QUACDocs

Reference

Roadmap

Stages are listed in order. Dates are given only once a stage is ready.

Done

Devnet

  • Cosmos SDK v0.55.1 chain with ML-DSA-65 as the only accepted signature, for accounts and validators.
  • Capped block-reward minting with an inflation band.
  • Classical keys rejected before execution, verified end to end.
  • Unit tests and an in-process ML-DSA validator network test.

Public testnet: quac-testnet-1 (live since 2026-11-18)

  • Four ML-DSA-65 validators with equal stake, peering over firewalled P2P; the chain tolerates any one validator going down.
  • A fourth validator added on a running chain with MsgCreateValidator (deploy/testnet/add-validator.sh).
  • Public REST API and faucet through a Cloudflare Tunnel; validator IPs never published.
  • Block explorer and faucet.
  • These docs.

Next

QUAC 100 validator signing

Validator consensus keys generated and held inside Dyber QUAC 100 post-quantum hardware, signing votes without the key ever leaving the module. CometBFT supports remote signers over a socket (priv_validator_laddr), so this ships as a signer process backed by the QUAC 100 SDK, with no change to the chain.

A separate server for quac-val-3, then external validators

quac-val-3 currently shares a server with quac-val-1; moving it to its own machine makes the network tolerate the loss of any one server, not just any one validator. After that, the testnet opens to outside validators: a public seed or sentry node arrangement that keeps Dyber's validator IPs private.

QUAC wallet

Mainstream Cosmos wallets don't support ML-DSA-65 keys yet. A QUAC wallet will create, back up and sign with them, and broadcast over the REST API. Contributing ML-DSA support to existing wallets is also on the table.

Later

Post-quantum P2P

Replace CometBFT's Ed25519/X25519 node handshake with a post-quantum one (for example ML-KEM for key exchange and ML-DSA for node identity), ideally upstream in CometBFT.

Mainnet

Mainnet launches after:

  1. the final supply, genesis allocation and vesting are published,
  2. an independent security review of QUAC's code and configuration,
  3. legal review of the coin's distribution,
  4. each mainnet validator has generated its own keys on its own hardware.

IBC

Inter-Blockchain Communication with other Cosmos chains. Counterparty chains must run a CometBFT/SDK version that can verify ML-DSA-65 commit signatures before an IBC light client of QUAC can work.

Edit this page on GitHub