Quantum-safe
accounts.
Every account is signed with ML-DSA-44, the NIST post-quantum standard. Validator blocks add a classical Ed25519 signature on top, so the chain is protected against both today’s and tomorrow’s attackers.
NOXY is a post-quantum Layer 1 blockchain: every account signature uses ML-DSA (NIST FIPS 204) — not as a patch or a roadmap promise, but from genesis. The quantum-resistant testnet is public: query the RPC, run a validator, and verify every claim on this page. Native staking, on-chain account names, and BFT finality are live today.
Accounts, consensus, deterministic state, and a native staking economy — coordinated by a single Rust node and secured end to end with post-quantum cryptography.
Every account is signed with ML-DSA-44, the NIST post-quantum standard. Validator blocks add a classical Ed25519 signature on top, so the chain is protected against both today’s and tomorrow’s attackers.
BFT consensus commits blocks that are final the moment they land — no waiting for confirmations, no probabilistic settlement.
A Jellyfish Merkle Tree commits every state change, so any account or balance can be proven against a block with a compact proof.
Fees, treasury, bonding, delegation, rewards, and slashing live in the protocol itself — not in a separate contract you have to trust.
Real validators, real genesis parameters, real staking economics. The testnet runs the same code and the same money path that mainnet will — nothing is stubbed out for show.
A Rust node and CLI, a TypeScript SDK with cross-checked encoding, account-name resolution, transaction submission, and read access to blocks, events, proofs, and economics — all through one clean RPC surface.
1 2 3 4 5 6 7 8 9
# resolve a native account name $ noxy-cli --profile test account-name resolve pavel@veylith # response shape { handle_ref: "pavel@veylith", account: "tnxy1q9k3xv7n2...", verifier: "pillar · mango · cliff · 47" }
1 2 3 4 5 6 7 8 9 10
GET https://rpc.veylith.test/v0/node/identity GET https://rpc.veylith.test/v0/state/root GET https://rpc.veylith.test/v0/economics/summary # all values are committed state or node build metadata { chain_id: "veylith", release_version: "0.1.x", protocol_version: 1 }
1 2 3 4 5 6 7 8 9
# operator profile chain_id = "veylith" rpc_bind = "0.0.0.0:8080" db_path = "/var/lib/noxy" # node startup refuses mismatched genesis identity genesis = "/etc/noxy/genesis.json" validator_key_dir = "/etc/noxy/keys"
The protocol core, native economics, account-name registry, and service-chain framework are all working code — with a CLI, RPC, Docker images, and full documentation.
One Rust node produces and verifies blocks, commits state, emits events, and replays the chain from genesis to prove it.
A native token with fees, an on-chain treasury, validator bonds, delegation, rewards, and slashing — all in protocol.
Send to a name instead of a 64-character address. Names are on-chain, checksummed addresses prevent typos, and three words let you verify a recipient out loud.
Register a service chain, post a refundable bond, and anchor its checkpoints to NOXY — with usage metered per epoch.
The testnet runs real genesis parameters, real validator keys, and the real staking economy. Mainnet follows once the network is proven in the open — with audits, benchmarks, and signed releases.
Not yet. The testnet runs on tNOXY — a test asset with no monetary value, dripped freely from the faucet. The mainnet token launches with mainnet, and its supply and distribution principles will be published before any listing.
Real enough that NIST has standardized replacement algorithms (FIPS 204) and set a 2030–2035 timeline for retiring classical cryptography. Blockchains are especially exposed: public keys and signatures live on-chain forever, so anything signed today can be attacked retroactively — “harvest now, decrypt later”.
Retrofitting means migrating every account, wallet, and signer without breaking consensus — and ML-DSA signatures are roughly 35× larger than ECDSA, straining formats designed around small signatures. NOXY skips the migration entirely: every account signs with ML-DSA from genesis.

Spin up a validator, resolve your first account name, or send a transaction with the SDK. Everything you need is documented and running today.