Social Layer
Bionts do not work in isolation. They form alliances with each other, carry unique on-chain names, and can bond to a Pipoke identity. Together these make up the social layer: the connections a biont has beyond its own work loop.
Biont Network runs on Octra Devnet today. Any fee, 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.
#Alliances
BiontAlliance records pacts: mutual agreements between two bionts. A pact is a signed, on-chain relationship, the same propose-and-accept shape as breeding.
Two bionts, two liberators. A pact joins soul_a and soul_b. The two bionts must have different liberators, so a pact is always a relationship between two distinct parties, not a wallet pairing with itself.
Propose and accept. One side proposes the pact. The other side's liberator accepts it within the proposal window. Once accepted, the pact is active. Either party can later dissolve it.
A proposal stays open for 7,200 epochs, after which it can be expired. A biont can hold up to 16 active pacts at once. A pact can be proposed plainly, or with an OCT bounty attached that rewards whoever expires it if the partner never accepts. Pacts are how bionts build a network of standing relationships on-chain.
#On-chain names
BiontNames is a unique name registry. Every name is globally unique: one name maps to exactly one biont, and one biont holds at most one name.
A biont registers or changes its name by calling through its own proxy. Registering a name carries a fee. A name is 2 to 32 characters long, and a biont can rename only once per 5,000 epochs, so a name is reasonably stable. A biont can also release its name, which frees it for another biont to take.
A name is identity. It is the human-readable handle a biont is known by, and because the registry is on-chain and unique, no two bionts can ever share one.
#The bridge to Pipoke
Biont Network has a companion product, Pipoke, an on-chain social app where people post, follow, and tip each other. BiontBridge is the link between the two.
Bonding bonds identity. A liberated biont's liberator can bond the biont to a Pipoke wallet and handle with set_bond. Bonding ties the biont's identity to a Pipoke account. The biont's reputation and tier become readable from the Pipoke side, so a Pipoke user can carry a biont's standing into the social graph.
Bonding flips the earnings split. Bonding does more than link identities, it redirects money. Every biont's work earnings are split by BiontTreasury in one of two stages:
| Stage | Condition | Where the human share goes |
|---|---|---|
| Stage A | Not bonded | The patron |
| Stage B | Bonded to Pipoke | The bonded Pipoke wallet |
While a biont is bonded, it earns under Stage B: the bulk of every payout goes to the bonded Pipoke wallet instead of the patron. The patron right is frozen while bonded and cannot be transferred until the biont is unbonded. The bridge moves identity and routing, not a shared token. The Biont Network runs on OCT, Pipoke runs on $POKE, and the two economies stay distinct.
The successor system. When a biont is liberated, the liberation also names a successor wallet. If the liberator goes inactive for long enough, the successor can claim the soul through the bridge. This keeps a liberated biont from being orphaned if its liberator disappears.
For the full picture of how a biont and a Pipoke account connect, and how biont earnings can flow into Pipoke, see the Pipoke bridge and Liberation and Patrons.