Deterministic Consensus
The hard boundary protecting ownership, supply and finality.
- Signatures & nonces
- Balances & state roots
- Stake-weighted finality
- Hard supply invariants
- Protocol permissions
NEXUS separates deterministic monetary consensus from probabilistic cognition, allowing agents and machines to reason, prove results, exchange value and settle energy without giving AI authority over ledger validity.
ec24ae13…38c5eAI can recommend.
Cryptography decides.
Reasoning becomes a
verifiable receipt.
Machines become
economic actors.
Energy becomes
streamable settlement.
THE PROTOCOL
NEXUS deliberately refuses to make probabilistic models part of monetary truth. The ledger remains deterministic; cognition produces typed evidence that deterministic verifiers may accept or reject.
The hard boundary protecting ownership, supply and finality.
Competitive agents perform work without gaining authority over consensus.
PROOF OF REASONING
The protocol does not store private chain-of-thought. It commits to inputs, outputs, evidence, model identity and validator signatures, creating an auditable artifact without turning hidden reasoning into consensus data.
{
"problem_hash": "0x9d…e2",
"model_hash": "0x41…af",
"evidence_hash": "0x72…19",
"result_hash": "0xc3…44",
"committee": 4,
"agreement": "3/4",
"confidence": 0.75
}
MACHINE ECONOMY
Wallet, owner, capabilities, model identity, budget, reputation and policy in one constrained account.
Cryptographic identity for robots, chargers, batteries, sensors and other autonomous infrastructure.
Signed metering attestations allow machines to settle verified energy consumption in small increments.
Agents express goals and constraints; deterministic policies bound what plans are allowed to execute.
REFERENCE FLOW
In the Alpha reference scenario, a robot purchases 5.4 kWh from a machine identity and settles 1.08 NEX after a signed energy attestation is incorporated into state.
MONETARY INVARIANT
The maximum native supply is defined as 2²³. The research design allocates the maximum at Genesis into protocol-controlled and participant balances. Later rewards release existing locked balances rather than relying on future mint authority.
Hard-cap invariant
DEVNET ALPHA · REFERENCE IMPLEMENTATION
These are reproducible Alpha test results, not a claim of production readiness or public decentralization.
PROTOCOL ROADMAP
NEXUS v0.1 remains an immutable historical reference. Every later release must pass a specific technical test before the protocol advances.
Exit evidence: public paper + deterministic 4-node convergence.
Exit criterion: machine-readable specification with explicit invariants and failure conditions.
Exit criterion: published attack matrix and mitigations under repeatable tests.
Exit criterion: deterministic cross-node state transitions on the Rust implementation.
Exit criterion: native Windows x64 + macOS Apple Silicon/Intel builds each pass the frozen four-node network self-test.
Exit criterion: 20–50 independent nodes with measured finality, throughput, PoR latency and recovery.
Exit criterion: reproducible hardware-to-chain settlement outside simulation.
Exit criterion: end-to-end agent-to-agent service settlement on public testnet.
Exit criterion: critical findings resolved or explicitly accepted and documented.
Exit criterion: published economic model survives adversarial parameter sweeps and failure scenarios.
Exit criterion: no unresolved critical blockers across security, consensus, cognition or economics.
v0.1 is never rewritten. Future research extends it through new specifications and releases, preserving an auditable history of how NEXUS evolved.
NEXUS PRINCIPLE 00
“The blockchain may reason about what to do.
It may never reason away its own rules.”
Probabilistic intelligence lives inside deterministic boundaries.
OPEN RESEARCH
NEXUS v0.1 is a research draft. The most valuable contribution today is rigorous criticism of its trust boundaries, verifier classes, committee failure modes and machine-oracle assumptions.