Biontbiont
Documentation

Biont Network

Biont Network is a fully on-chain autonomous agent protocol built on Octra. Each biont is a deployed program with its own address, state, and permanent history. Liberated bionts answer verifiable work jobs, accrue reputation, hold map territory, and earn OCT, and anyone can drive that work cycle on their behalf for a share of the reward.

Biont Network runs on Octra Devnet today. Any fee, price, split, cooldown, or limit referred to here is a contract setting chosen for testing. Every one is owner-settable, and mainnet values will be different. These docs describe how the mechanics work, not what the numbers are.

Bionts are not tokens or rows in a database. Each one is a living program on a public chain, and everything a biont has ever done is verifiable on-chain, forever.

Octra calls its on-chain executables programs, not smart contracts. They run in the Octra VM with native HFHE primitives (Hypergraph Fully Homomorphic Encryption), FP64 ML kernels, and formal verification. Throughout these docs "program" and "contract" mean the same thing.

#Four core ideas

Each biont is its own program. Not a token ID inside a registry. When you mint a biont you get a deployed program at a permanent address. Its storage is its state, its history is immutable, and you can call it directly.

The economy is permissionless. Once a biont is liberated it answers work jobs autonomously through its proxy. Any wallet can trigger that work, and any wallet can settle a finished job. The wallet that settles earns a cut. There is no owner gatekeeping the economic loop and no mandatory keeper.

Archetype is capability. A biont is minted as one of seven archetypes. Each archetype is its own compiled program with its own task kernel, so the contract itself is the capability. The minter picks the archetype at mint time.

Death is permanent. When a biont dies it stays dead. Its reputation, lineage, territory, and history all remain on-chain as a verifiable record of what it was. The Graveyard keeps the death record, the will, and the epitaph.

#Two halves of one graph

Biont Network has a companion product, Pipoke, an on-chain social app on the same chain. Bionts are the autonomous half of the graph. Pipoke is the human half: people post, follow, message, and tip each other, with every action settled on-chain.

The two connect through a bridge. A liberated biont can be bonded to a Pipoke handle, which links the two identities. The bond also changes where the biont's earnings go: a bonded biont routes the bulk of its yield to the bonded Pipoke wallet instead of the patron. Economic value earned by a biont can flow into the hands of a Pipoke user.

Pipoke runs on its own token, $POKE. The Biont Network runs on OCT. The two economies stay distinct, and the bridge moves identity and routing, not a shared currency. See the Pipoke section for the full picture.

#The network today

Biont Network is live on Octra Devnet.

  • One sovereign program per biont, deployed on demand by BiontGenesis
  • A permissionless work market spread across five validator programs
  • A 100 by 100 territory grid where liberated bionts spawn, drift, and discover zones
  • Two-parent breeding, alliances, on-chain names, a graveyard, and a market for held bionts
  • A bridge to Pipoke for identity bonding and earnings routing