2²⁵⁶
addresses on the chain
Around 10⁷⁷ of them — comfortably more than the atoms that make up the Earth. You will never collide with anyone, by construction.
Address = [u8; 32]
maya-testnet-1 · connecting… · block — · — s ago
The ledger for the post-quantum century.
Every transaction carries two NIST post-quantum signatures. Every claim links to the test that proves it.
Drag to orbit. Tap the core, a validator or a block for its numbers.
- Height
- —
- Block time
- —
- Signature
- ML-DSA-65
- Validators
- —project-run
In plain words
A shared notebook that is hard to forge
Maya2C is a notebook that everyone copies. Each page lists payments. A payment is written only if it carries two signatures that check out, and the number on it is the next one for that account.
The signatures use two kinds of lock, because one kind might one day be picked by a quantum computer. A thief would have to pick both.
Validators take turns proposing pages and sign each other’s pages. When enough of them agree, the page is sealed and never changes.
Each page below goes deeper, in three layers: plain words first, then the engineering, then the mathematics.
- How a transaction works
- Post-quantum signatures
- Consensus and finality
- Run a validator
- Wallets
- Join the testnet
Why it is built this way
Security you can check
Two signaturesML-DSA-65 and SLH-DSA on every transactionLearn more →Final in secondsDAG-BFT: a block never reorganisesLearn more →Post-quantum linksML-KEM-768 on every peer connectionLearn more →Proven claimsA claim without a test fails CILearn more →
Hard to believe, easy to check
The numbers behind a post-quantum chain
2signatures
on every transaction
ML-DSA-65 and SLH-DSA-SHA2-128s both sign and both must verify. A quantum computer has to break a lattice problem and a hash problem — breaking just one buys it nothing.
FIPS 204 + FIPS 205, hybrid suite
11,165bytes
of post-quantum proof per transfer
That is the price of not betting the whole chain on a single cryptographic assumption. A classical chain spends 64–96 bytes, and none of it survives a quantum computer.
3,309 B ML-DSA + 7,856 B SLH-DSA
32MiB
of memory per mining guess
Every proof-of-work attempt has to fill 32 mebibytes with Argon2id before it counts. That is the knob that keeps the network out of reach of cheap throwaway ASIC farms.
Argon2id over 32 MiB + BLAKE3
Architecture
Post-quantum at every layer
ApplicationsMaya Chat · desktop wallet · SDKs (TypeScript, Python, Go)
GatewayREST and GraphQL, default-deny allowlist, rate limits
ExecutionWASM contract VM, metered · fee market with a burned base fee
ConsensusDAG-BFT (Narwhal + Bullshark) · staking and slashing
Networklibp2p · Noise with an ML-KEM-768 layer
CryptographyML-DSA · ML-KEM · SLH-DSA (FIPS 204/203/205) · X-Wing hybrid
Ecosystem
Many apps, one identity
Try it
Testnet paused: 7 days, zero halts
ExperienceBack with the next genesisLearn more →Test coinsBack with the next genesisLearn more →Uptime7 d 15 h, zero haltsLearn more →Wallet, chat, minerWindows, macOS, LinuxLearn more →MineGPU mining from mainnet launchLearn more →Build on itSDKs and a public APILearn more →Break itAttack it, earn creditLearn more →
Proof, not promises
The whole system, by what a test can prove
—tests passing
—verified subsystemsbacked by a named test
—workingbuilt, test pending verify
—planneddesigned, no code yet
—launch gates passedof —, before mainnet
Mainnet gates
Ten checks before mainnet
Gate 1 · met
Replay protection
A signature commits to its chain: a testnet transfer cannot replay on mainnet
Evidence: ADR-036 →Gate 2 · met
Shielded pool off
Mainnet starts without shielded transfers; the guard refuses a genesis that enables them
Evidence: ADR-037 →Gate 3 · met
7 days, no halt
Passed: 7 days 15 h with zero halts, blocks 0 to 393,812, stopped on purpose 2026-10-28
Evidence: soak report →Gate 4 · in progress
Separate validators
A project-run foundation set at launch, stated publicly; separate machines and operators join after
Evidence: ADR-047 →Gate 5 · waiting
Genesis ceremony
Rehearsed and reproduced byte-identical; the real one needs gate 4
Evidence: ceremony runbook →Gate 6 · in progress
Economics
GPU-mined block rewards, no premine (ADR-044). Approved 2026-10-28, being built: a reward that never ends and part of every fee burned
Evidence: ADR-044 →Gate 7 · in progress
CI and release
Every check green, gate 1 and 2 reviews clean, binaries built from a tag
Evidence: CI →Gate 8 · met
Validator rejoins
A validator down for any length of time comes back on its own
Evidence: attacknet, all 8 attacks →Gate 9 · met
Logs stay bounded
Consensus logs pruned each epoch: 286 MB per validator, was 3.1 GB
Evidence: measured on the testnet →Gate 10 · in progress
Halt recovery
No cheap committee capture, and a tested way back from a halt (the way back is still being built)
Evidence: attacknet + runbook →
metin progresswaitingas of 2026-10-28 · source: docs/mainnet-v1-plan.md
Progress
Live from the repository
5 of 10 gatesMainnet checks passedLearn more →86 done29 steps still openLearn more →CI greenmaster, 2026-10-30 02:37 UTCLearn more →95 mergedchanges in the last 7 daysLearn more →1 in reviewopen pull requestsLearn more →node-v0.1.0-testnet.4newest build, 2026-10-19 15:56 UTCLearn more →
- test: attacknet PASS on the freeze commit 8987a6be 2026-10-30
- feat(genesis): mainnet inputs, 10^6 fee floor, DAG-BFT-aware genesis-check 2026-10-30
- docs(state): consensus frozen at 8987a6be 2026-10-30
- feat(rpc): get_node_version for operator update notices 2026-10-30
- feat(hub): signed in-app updates 2026-10-30
- fix(bft): rescue followers that no checkpoint can move (attack 7) 2026-10-30
- fix(staking): no repeated punishment for fallback-seated jailed validators (S-030) 2026-10-29
- docs(audit): round-2 pre-audit findings S-012..S-034 2026-10-29
Counted automatically at 2026-10-30 02:46 UTC; rebuilt every 6 hours and on every merge.
Launch ladder
Where it stands, gate by gate
- Localnetpassed
4 validators over real libp2p: agree, survive a kill, catch up
- Devnet softwarepassed
DAG-BFT finality, staking, slashing, fee market, SLO metrics
- Operations rehearsedpassed
state sync, crash restore, coordinated restart
- Public testnetpassed
maya-testnet-1 ran 7 days 15 h with zero halts to block 393,812, then was paused on purpose 2026-10-28 for the next genesis
- Foundation validator setnext
four project-run validators, all on one PC and said so: any one validator can stop without halting the chain, the PC failing halts it until it returns; other machines join after launch (ADR-047)
- Attacknet, 4 weeksnot yet
self-run attacknet daily (crashes, stolen key, floods, outages) plus a public break-it programme for credit; paid incentives after funding (ADR-042)
- Pre-audit + audit applied fornot yet
pre-audit package complete and free audit programmes applied to; mainnet carries an "external audit pending" label until a report lands (ADR-042)
- Mainnetnot yet
blocked until every gate above passes
Launch vector · maya-mainnet
4 / 8 GATES PASSED
No token is for sale, and nothing here is an offer of one.
Every download is built from this source by CI and carries verifiable provenance: Code signing policy.