Signed today.
Still yours
after quantum.

↓
whathappensonq-day
Record.Wait.Forge.

Bitcoin, Ethereum and Solana sign with elliptic curves. Shor's algorithm solves the elliptic-curve discrete log in polynomial time, so once a public key is on chain, a large enough quantum computer can derive the private key behind it and sign as the owner. Public keys are being collected now. Migration has to happen before that machine exists.

● record.2026
a wallet on an elliptic-curve chain
public key copied and kept
onyx · onx1 address
public key copied and kept
BitcoinECDSA · Schnorr · secp256k1
EthereumECDSA · secp256k1
SolanaEd25519
signaturessee the design →elliptic curveslattices
ONYX · blocksML-DSA-65 · NIST level 3
ONYX · transactionsML-DSA-44 · NIST level 2
ONYX · hashingSHA3-256

Putting post-quantum signatures onto a chain that already exists means a hard fork and every holder moving keys in time. ONYX starts with lattices at block one, so there is no elliptic-curve key anywhere in it to break.

thetestnetrightnow
Not a paper.A chain.

Validators rotate block production every 4 seconds. Each block is signed by its proposer and attested by the others, every signature ML-DSA-65, and each one is checked before the block is accepted. What you see below is the chain as it runs.

block height—
pq signatures verified—
transactions—
accounts—
slot time4.0s
insidethelatticechain

Every layer of ONYX is built on lattice signatures and SHA-3, with zero elliptic curves:

wallet

Lattice keys in your browser

Your wallet makes an ML-DSA-44 keypair on your device. The secret key never leaves it. Your address is a SHA3-256 hash of the public key.

addr = "onx1" ‖ SHA3-256(pk)[0..20]
transactions

Verified at the gate

Every transaction carries its 1,312-byte public key and 2,420-byte signature. The node checks it against FIPS 204 before it reaches the mempool.

replaces ECDSA and Ed25519
consensus

Quantum-safe finality

Proposers rotate. A block is final when the proposer and at least two attesters sign its SHA3-256 header hash with ML-DSA-65.

final ⇔ 1 + ≥2 valid ML-DSA-65 sigs
validators

Open validator set

Anyone can stake and attest: a 70-line node you can read, or a validator that runs in a browser tab. Rewards are paid per block and per attestation.

custody

Quantum Vaults

k-of-n multisig where every signer key is ML-DSA-44. Proposals and approvals are signed in the browser and land in blocks.

tokens

Launchpad

Launch a native token on a bonding curve. Tech tokens prove a public GitHub repository; every launch and trade is ML-DSA signed.

trading

QuantumDEX

A constant-product pool for tONYX and tUSD. Swaps and liquidity are signed with lattice keys and settle inside blocks.

migration

The Lifeboat

Bind a Solana wallet to an onx1 address: the same message signed by your Ed25519 key and your ML-DSA key, written into a block.

builders

Public RPC

JSON-RPC 2.0 with fifteen methods, open CORS and a small SDK. Send a signed transaction from a script in a dozen lines.

whatsafetyweighs

Lasting signatures have a size.

Post-quantum signatures are larger than the elliptic-curve ones they replace. ONYX is built around that from the first block: blocks, gossip and storage are sized for ML-DSA instead of having it bolted on later.

Ed25519 Solana
64 B
ECDSA Bitcoin, Ethereum
65 B
ML-DSA-44 ONYX transactions
2,420 B
ML-DSA-65 ONYX blocks
3,309 B

Signature sizes per FIPS 204 and RFC 8032. Ed25519 and ECDSA are broken by Shor's algorithm. ML-DSA-44 is NIST security level 2, ML-DSA-65 is level 3.

onequestionthreechains
Same ledger.Different math.

Once a quantum computer can run Shor's algorithm, one question decides what a chain is worth: can anyone but the owner sign?

onyx

Holds

signatures after q-day
transactionsML-DSA-44, lattices
blocks and votesML-DSA-65, lattices
hashingSHA3-256
migration neededNone, lattice keys from block one
bitcoin

At risk

signatures after q-day
transactionsECDSA and Schnorr, secp256k1
blocksProof of work, SHA-256
hashingSHA-256
migration neededA fork, and every exposed key moved
solana

At risk

signatures after q-day
transactionsEd25519
blocks and votesEd25519
hashingSHA-256
migration neededEvery address is a public key already
whosignstheblocks
Lattice keys.Open set.

The genesis validators are below, each holding a 1,952-byte ML-DSA-65 key. The one outlined is proposing the current block. Anyone can join them.

fromtestnettomainnet
Theroadmap.
phase 1live

Lattice testnet. ML-DSA blocks, attestations and transactions, explorer, browser wallet and faucet.

phase 2live

Open validators. Stake, attest and earn from a script or a browser tab. Offline proposers are skipped.

phase 3live

Apps. Launchpad, QuantumDEX, Vaults, the Lifeboat and a public RPC with an SDK.

phase 4now

$ONYX. The token launches and carries the project to mainnet.

phase 5next

Mainnet. Genesis of the main chain. $ONYX holders move 1:1 to native ONYX through a snapshot.

thingspeoplekeepasking
Questions.Answers.
Are the signatures on the testnet really post-quantum?

Yes. Blocks and attestations are signed with ML-DSA-65 and transactions with ML-DSA-44, the lattice signature standard NIST published as FIPS 204. The node verifies every one of them with its runtime's native ML-DSA before a transaction enters the mempool or a block is accepted. Open any block in the explorer to see the signatures and their sizes, or try the Forge, which pays a bounty to anyone who can produce a valid signature without the key.

Where are my keys?

In your browser. The wallet generates an ML-DSA-44 keypair on your device and keeps the secret there. Transactions are signed locally and only the signature and public key are sent. Export the seed from the wallet page to back it up or move it.

How do I get tONYX?

Open the wallet, generate a key, and claim from the faucet: 1,000 tONYX per hour per address. Transfers cost a fee of 0.001 tONYX.

What is the difference between tONYX and $ONYX?

tONYX is the coin of the test network: it pays fees, stakes validators and trades on the testnet apps. $ONYX is the token that funds the work and carries the project to mainnet, where holders move 1:1 to native ONYX through a snapshot.

How does a block become final?

Proposers take turns in a fixed rotation every 4 seconds. The proposer signs the SHA3-256 hash of the block header with ML-DSA-65, and the other validators attest to the same hash. The block is final once the proposer's signature and at least two attestations verify. A proposer that is offline is skipped.

Can I run a validator?

Yes. Stake 500 tONYX, then sign block headers either with the single-file node (about 70 lines, readable in a minute) or with the validator that runs in a browser tab at /node. Rewards are 2 tONYX plus fees per proposed block and 0.25 tONYX per attestation.

Why not add post-quantum signatures to an existing chain?

It can be done, but it takes a hard fork, bigger blocks than the chain was sized for, and every holder moving funds to new keys before a quantum computer arrives. Addresses that have already revealed a public key stay exposed until they move. A chain that starts with lattice keys has nothing to migrate.

Can I build on it today?

Yes. The public JSON-RPC has fifteen methods, open CORS and a rate limit of 40 requests a second, and the SDK is one file you can import from this site. The RPC page has a live playground.

follow

Quantum-resistant L1

● testnet live · block …

Move before Q-day

specification

ML-DSA (FIPS 204) · SHA3-256 (FIPS 202). Protocol and API in the docs.