Chain in development  ·  Public testnet 2027  ·  No token has been issued
Peer-to-peer commerce Register
08  ·  Security

Nothing to trust. Everything to verify.

Who could stop it, and how would you know?

Sovereign is secured by SovereignBFT, a proof-of-stake consensus with deterministic finality. Ten disclosed operators anchor the set at genesis, open from block one; the set is capped at fifty and widens by governance toward a hundred, wherever validators are. No admin keys. No mint function. No pause.

3
Bootstrap nodes, open set
—
Nakamoto coefficient
0
Founder allocation
0
Admin keys
01

Who decides which block is real?

Two-thirds of staked validators, every block. Once committed, it is final.

How it works
01Blocks are proposed in turn and committed when validators holding two-thirds of stake sign them. No reorganisations, no confirmations to wait for.
02A validator that signs two conflicting blocks loses its stake. One that goes quiet is jailed and replaced by the next by stake.
03Ten disclosed operators anchor the set at genesis; it is capped at fifty and widens by governance toward a hundred. Stake, run the node, join.
04Block time ~3 s at mainnet, 1 s on the dev net. A payment that lands is settled.
02

Who could switch it off?

Nobody with a key. There is no admin key, no pause and no mint function to hold.

How it works
01No upgrade key, no blacklist, no account that can move funds it does not own.
02There is no mint function. Every SOV is mined out of a pool filled once at genesis, so circulating supply only rises toward one billion and never past it. Nothing is burned; fees are recycled back into the same pool.
03Rule changes go through holder vote with a long delay, and validators can refuse to run them.
04The founder’s key does nothing any holder’s key cannot.
03

What if a country, a grid or a hosting company goes down?

The chain does not notice. The validators are placed so that none of them can take it with them.

How it works
01No more than a fifth of stake on any one power grid or hosting company; no more than a quarter under any one government.
02The Nakamoto coefficient, the smallest number of validators that could halt the chain together, is published live, with a target of rising every year.
03Site, wallet and docs are pinned on IPFS and served over Tor; seeds and RPC are published as onion services as well as clearnet. Six points of failure →
04

How do you know any of this is true?

Read the chain, or watch the kill-test.

Kill-test, illustrative
Project-run nodesOff, 72 hours
Blocks producedUninterrupted
Trades settledNormal
Site and docsServed from IPFS and Tor
ResultPublished, with heights
How it works
01Every quarter, every node the project runs is switched off, announced in advance. Blocks continue, trades settle, offline payments finalise. The result is published with block heights.
02Independent audits precede mainnet and are published.
03Keys never leave the holder’s device. Non-custodial throughout.
04The code is open. Every claim on this site is a function you can read.
05

What is built today?

The chain runs. Every module below is live on the dev net and exercised end to end.

How it works
01Mining: mine-from-zero on-ramp — a cold wallet with no account proves a short proof-of-work over its own address and is created and funded at the next epoch, no fee, no sign-up.
02Reservoir: the whole supply starts in one mining pool; each epoch emits a slice, halving about every two years, split 50/25/25 to miners, validators and the mesh. Fees recycle in; nothing is burned.
03Market: posts, escrow lock and release, auto-refund at deadline; the dispute panel is built but dormant at genesis until governance enables it.
04Staking: delegate to a validator, earn a share of emission (yield capped ~7%/yr), redelegate, unbond over 21 days. Downtime jails; double-sign slashes.
05Mesh: proof-of-coverage — bonded witnesses attest who is on the air each round against an unpredictable beacon; nodes are paid for proven uptime, with region-diversity shaping and an inactive-node slash.
06Governance: holder voting — enable disputes, widen the validator cap, approve coin issues. Struck: strike, transfer, melt, sealed totals. Offline: caps, signed hops, onward hops, out-of-order settlement, replay rejection.
07Privacy: sealed amounts (commitments with range proofs, no trusted setup) and one-time addresses, with the supply audit. Not yet: viewing keys, sealed-send sender privacy, native Bluetooth, public testnet.

One billion SOV, fixed. Each epoch the mining pool emits a slice — halving about every two years — split fifty percent to miners, twenty-five to validators, twenty-five to the mesh. Fees recycle back into the pool; nothing is burned.

50% miners
25% validators
25% mesh

Rules without rulers. If you can read the chain, you can verify every claim on this page.

Next: Questions
Sovereign