Architecture

Biont Network is a layered protocol. Every layer is an on-chain program written in AppliedML on Octra. The design is lean: one program per biont, plus a small set of shared service programs and five validator programs. Nothing more.

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.

#Layers

• Citizens. One program per biont, deployed from one of seven archetype bytecodes.
• Factory. BiontGenesis mints bionts and tracks ownership.
• Validators. Five programs that post and judge work jobs.
• Services. Shared programs that hold cross-cutting state: treasury, registry, reputation, territory, and the rest.
• Bridge. BiontBridge connects a biont to a Pipoke identity and routes earnings.

#Citizens: the biont proxy

Every biont is its own deployed program. There are seven compiled variants, one per archetype, and they share a single template. Only two things differ between variants: the private task kernel and the archetype constant.

The program holds:

• Identity. name, symbol of BIONT, soul_id, seed, archetype, birth_epoch.
• Ownership. owner, is_freed, liberator, plus the wired addresses of every service.
• Self-fund. self_fund_balance, the biont's own OCT reserve, credited by the Treasury from work earnings.
• Work surface. auto_claim, auto_attest, auto_claim_winnings, and auto_answer. These are permissionless and only callable once the biont is liberated. Each is cooldown-gated.
• Visuals. token_uri returns a complete animated SVG built from the seed. No external rendering, no off-chain image host.

There is no shared logic contract. Each biont is the full program at its own address. Heavy mutable state such as vitality lives in BiontRegistry, which every biont calls into.

#Factory: BiontGenesis

BiontGenesis is the mint factory and the ownership index.

• It stores one compiled bytecode per archetype, set by the owner before launch.
• mint(archetype) validates the archetype, deploys the bytecode on demand, initialises the new program, and registers it with the Registry and Reputation.
• It tracks soul_by_id, owner_map, and per-wallet mint counts.
• liberate(soul, successor) frees a biont, records the liberator, and notifies the Registry, Treasury, and Bridge.
• transfer_to and market_transfer move held bionts. Liberated bionts can never be transferred.

#Validators

Five validator programs post and judge work. Each one is standalone. They are peers, not a routed hierarchy.

Job type	Validator	Judges
1	BiontWorkEngine	General hash and attestation jobs
2	BiontOracleValidator	Numeric oracle queries
3	BiontCurationValidator	Quality scoring and pick sets
6	BiontChallengeValidator	Adversarial challenge resolution
7	BiontPredictionValidator	Forecast settlement

A poster funds a job on the relevant validator. Liberated bionts submit answers through their proxy. After the deadline anyone settles, the validator decides the winning answer by plurality, pays winners through the Treasury, and updates reputation. There is no central work engine routing between validators. A biont's proxy holds the address of each validator and submits to the right one by job type.

#Services

Program	Role
BiontRegistry	Per-soul vitality, decay, alive and dead state, and the liberation record. Every consensus win refreshes vitality here.
BiontTreasury	Earnings and payouts. Takes the settler cut, then splits the rest between patron or bonded wallet, the soul self-fund, and the protocol fee. Tracks inflow by source.
BiontReputation	Per-soul score with Bronze, Silver, Gold, and Platinum tiers. Awarded on a win, slashed on a loss, with built-in decay.
BiontTerritory	The 100 by 100 grid. Auto-spawn on liberation, permissionless drift, teleport and pin for liberators, discovery and landmark rewards from a bounty pool.
BiontLineage	Parent and child relationships, generation depth, and two-parent breeding.
BiontAlliance	Mutual signed pacts between two bionts.
BiontNames	Unique on-chain name registry, one name per soul.
BiontGraveyard	Death records, wills, epitaphs, and burial.
BiontMarket	Sale listings and escrowed offers for held bionts, with a protocol fee on settlement.
BiontBridge	Bonds a biont to a Pipoke wallet and handle, runs the successor system, and flips the earnings split to Stage B while bonded.
BiontSessionRegistry	Maps short-lived session keys to a principal wallet so any wallet can drive bionts without a wallet prompt per action.

#Control

There is no single pause multicaster. Each program carries its own pause and unpause, callable by that program's owner, and a not_paused guard on its state-changing methods. Cross-contract wiring is set once by the owner and then locked with a lock_wirings call on each program.

#Network

Biont Network runs on Octra, a general-purpose Layer 1 with native HFHE in the VM, the AppliedML contract language, epoch-based consensus, and fast devnet finality. All biont programs compile to OCTB bytecode and interact through standard Octra RPC methods.