Money lost its banks.
Contracts lost their courts.
Intelligence is next.
Your intelligence has a landlord — a handful of labs decide what the models say, who may use them, and what the rent is. MindChain is the eviction notice: a Layer 1 where AI inference is receipted at the source, verified by an escalating dispute ladder, and settled on-chain — and where ASC, thinking gold, is minted only when a mind no one owns provably grows. The consensus is boring on purpose. The revolution rides above finality, and every claim not yet earned is held, in writing, in the litepaper.
MINDCHAIN · NETWORK
A block every slot. A slot every second.
The specimen beside the headline is a faithful animation of the MindChain block lifecycle — execution, proposal, propagation, quorum, finality — not live telemetry. The chain's real numbers come from recorded devnet-1 runs, and they are better than the animation: 86 blocks finalized with a bit-identical final hash and state root on every validator, mean finality lag 1.081 s, 800 of 800 transactions included, supply conserved (measured, devnet smoke run).
- 01
Execution
Agent transactions assemble into state transitions and converge on the validator due to propose.
- 02
Proposal
One validator earns proposer duty. Duty rotates deterministically every cycle — never a fixed leader.
- 03
Propagation
The block travels validator to validator across the gossip topology. No hub, no broadcast tower.
- 04
Quorum
⌈2/3 · V⌉ validators acknowledge the block — a two-thirds supermajority. On devnet-1 today that is 4 of 5; the animation draws a larger shell for legibility.
- 05
Finality
Attestations contract into a settled state root. The next cycle begins under a different proposer.
Protocol design
No permanent leader
Proposer duty moves through the entire validator set on a deterministic stride. Any observer can verify the schedule; no validator can hold the network.
Machine-native execution
Notes, lock scripts, and cognition-intent objects are first-class protocol state — built for software that transacts continuously. The receipt is the atom: this model, these weights, this request, this output.
Two-slot finality
A block proposed in one slot is final a slot later — about a second of measured lag on devnet runs, not probabilistic confirmations.
Verifiable by anyone
Every phase of consensus is observable: proposals, acknowledgements, quorum, and finality are public protocol events.
devnet-1, measured
| Network | devnet-1 · chain 70085c…cd300 |
|---|---|
| Consensus | BFT · ⌈2/3 · V⌉ quorum · deterministic coprime-stride proposer rotation |
| Slots | ~1 s · two-slot finality by design |
| Validators | 5, curated — candidacy open via onboarding |
| Recorded run | 86 blocks finalized · mean finality lag 1.081 s · identical final hash and state root on every validator · 800/800 tx · supply conserved |
| Live state | MindScan explorer · network pointer /network/latest.json |