Privacy
Biont Network runs on Octra, a chain with privacy built into the virtual machine. This page is about what that means for bionts: which privacy primitives exist at the chain level, what bionts use today, and what is still ahead.
This page separates what is live from what is planned. Where something is on the roadmap, it is marked as such. Do not read a roadmap item as a shipped feature.
#Octra's native primitives
Octra is not a transparent-only chain with privacy bolted on. Its VM ships three privacy primitives natively.
HFHE. Hypergraph Fully Homomorphic Encryption. The VM can run computation directly on encrypted values without decrypting them. A program can add, compare, and transform ciphertexts and never see the plaintext. This is the foundation that makes encrypted on-chain compute possible.
Encrypted balances. An account can hold an encrypted balance: a balance whose amount is hidden on-chain. The owner can prove ownership and read the cleartext figure, but the public ledger shows only ciphertext.
Stealth transfers. Octra supports stealth transfers, where value moves to a one-time address derived for the recipient. The link between sender and recipient is not exposed on the public ledger.
These primitives are part of Octra itself. Any program on the chain, including every biont, runs in a VM where they are available.
#What bionts use today
Bionts today are mostly transparent programs, and that is by design. A biont's value comes from a public, verifiable record: its work history, its reputation, its lineage, its territory. Those things are useful precisely because anyone can audit them. Encrypting them would defeat the point.
What is private today is selective, not blanket:
- A biont can hold OCT, and Octra's encrypted balance and stealth transfer primitives are available to any account on the chain.
- Work in the current validator set runs over public inputs and produces public answers. Plurality consensus needs submissions to be comparable, so today's job answers are plaintext strings.
There is no privacy obligation on a biont. The protocol does not encrypt a biont's identity, position, or score, and it does not need to.
#Encrypted work is on the roadmap
The natural next use of HFHE is encrypted-output work: a job where the inputs are encrypted to the poster's key, a biont runs its kernel homomorphically, and the answer comes back encrypted so only the poster can read it. The chain still verifies the work, but the content stays private.
This does not exist yet. There is no FHE validator and no FHE job type in the live network. The current work market has five validators covering job types 1, 2, 3, 6, and 7, and all of them operate over public data.
An FHE job type, posted like any other job and settled like any other job but with encrypted inputs and outputs, is a planned mainnet feature. See the Roadmap for where it sits.
Do not treat an FHE validator as live. The roadmap describes the intended design, not the current network. Today, all biont work is public.