QUACDocs

Operating

Public testnet

quac-testnet-1 is the shared QUAC network. Use it to try ML-DSA-65 wallets, build against the API, or watch a post-quantum chain run.

Chain ID quac-testnet-1
REST API https://testnet-api.quantcoin.world
Faucet quantcoin.world/faucet, or https://testnet-faucet.quantcoin.world/claim
Explorer quantcoin.world/explorer
Validators 4, run by Dyber, equal stake (30M QUAC each)
Block time about 5.3 seconds
Minimum gas price 0.0025uquac
Genesis supply 400,000,000 test QUAC

Testnet QUAC has no value, and the network may be reset with a new genesis. Don't build anything that depends on testnet state lasting.

Get test QUAC

  1. Create a key: quacd keys add mywallet. It's ML-DSA-65 by default.
  2. Copy its address: quacd keys show mywallet -a.
  3. Paste the address into the faucet. You get 100 QUAC, once a day per address and per IP address.

From a script:

curl -X POST https://testnet-faucet.quantcoin.world/claim \
  -H 'Content-Type: application/json' \
  -d '{"address":"quac1…"}'
# {"address":"quac1…","amount":"100 QUAC","txhash":"3C73CA…"}

Send a transaction

The public testnet exposes the REST API only. Build and sign offline with quacd, then broadcast over REST:

# 1. Build an unsigned transfer. --offline needs the account number and sequence.
quacd tx bank send mywallet quac1… 1000000uquac \
  --chain-id quac-testnet-1 --fees 1000uquac --gas 400000 \
  --generate-only --offline --account-number <n> --sequence <s> > unsigned.json

# 2. Sign it with your ML-DSA-65 key
quacd tx sign unsigned.json --from mywallet --chain-id quac-testnet-1 \
  --offline --account-number <n> --sequence <s> > signed.json

# 3. Encode and broadcast through the REST API
TX=$(quacd tx encode signed.json)
curl -X POST https://testnet-api.quantcoin.world/cosmos/tx/v1beta1/txs \
  -H 'Content-Type: application/json' \
  -d "{\"tx_bytes\":\"$TX\",\"mode\":\"BROADCAST_MODE_SYNC\"}"

Get the account number and sequence from GET /cosmos/auth/v1beta1/accounts/{address}. A new account has none until it has received coins. See the REST API page.

How the testnet is deployed

The validators run on three servers. Their design goals are availability and not publishing server IP addresses.

            Cloudflare (quantcoin.world)
 testnet-api.quantcoin.world    ──┐
 testnet-faucet.quantcoin.world ──┴── Cloudflare Tunnel (outbound connection from server 1)

 server 1  quac-val-0 + REST API (localhost:1317) + faucet (localhost:8000) + cloudflared
 server 2  quac-val-1, quac-val-3 (second node; peers with quac-val-1 over localhost)
 server 3  quac-val-2
           └─ servers peer on 26656/tcp, each server's firewall open only to the other two
  • No inbound internet ports. The public endpoints arrive through a Cloudflare Tunnel, an outbound connection from server 1. DNS records point at Cloudflare, never at a server.
  • The P2P port is allowlisted. Each server's firewall opens 26656/tcp only to the other two servers.
  • IPs are kept out of public data.
    • Genesis transactions normally record each validator's node-id@ip:port in their memo, and the genesis file is public. QUAC's genesis uses placeholder addresses (10.0.0.x) there, and the real addresses live only in each node's local persistent_peers.
    • external_address is empty, so nodes never advertise an IP.
    • CometBFT RPC is not published. Its net_info method lists connected peers' IPs, and JSON-RPC can be called through several URL forms, so a path filter can't reliably block it. The REST API covers queries and broadcasting, and the node info it returns shows only tcp://0.0.0.0:26656.
  • One hostname level. The endpoints are testnet-api.… rather than api.testnet.…, because Cloudflare's universal certificate covers one subdomain level (*.quantcoin.world).

Fault tolerance

Consensus needs more than two thirds of the voting power. The testnet has four validators with equal stake (30M QUAC each), so any three of them, 90M of 120M, can finalize blocks. The chain keeps running with any one validator down.

One caveat: quac-val-1 and quac-val-3 share server 2, so losing that whole server takes out half the voting power and pauses the chain until it returns, with no lost state. Moving quac-val-3 to its own machine removes that single point of failure; deploy/testnet/add-validator.sh sets one up anywhere. Tested on 2026-11-18: with quac-val-2 stopped, blocks kept coming, signed by 3 of 4 validators.

The genesis ceremony

The testnet's genesis was built with deploy/testnet/make-genesis.sh. Steps:

  1. quacd init three validator homes. Each gets an ML-DSA-65 consensus key.
  2. Create an ML-DSA-65 operator key per validator, plus a faucet key.
  3. Add genesis accounts: 100M QUAC per validator, 100M for the faucet.
  4. Set block limits: max_gas 100,000,000 and max_bytes 4 MiB. Assert that pub_key_types is ["ml_dsa_65"].
  5. Each validator signs a gentx staking 30M QUAC. The memo carries a placeholder IP.
  6. collect-gentxs merges them, validate checks the result, and the final genesis goes to all three homes.
  7. Per-node config: persistent peers (real IPs, local only), empty external_address, pex = false, timeout_commit = 5s, minimum gas price, gRPC on 9190. The gateway node also gets the REST API with CORS.
  8. Each home is packaged as nodeN.tar.gz for its server. Mnemonics go to out/secrets/ for escrow.

deploy/testnet/install-node.sh then installs a node on a server:

  • creates an unprivileged quac user,
  • installs the binaries and unpacks the node home,
  • adds the firewall rules for the two peers,
  • installs quacd.service, plus quacfaucet.service and cloudflared on the gateway.

The full runbook is in deploy/testnet/README.md.

Testnet keys only. The ceremony generates every key on one machine, which is fine for a testnet. For mainnet, each validator generates its own consensus key on its own hardware, ideally inside a Dyber QUAC 100 module, and submits only its gentx.

Status

Live since 2026-11-18. Four ML-DSA-65 validators (the fourth, quac-val-3, joined at block 403 through a normal MsgCreateValidator), blocks about every 5.3 seconds.

Adding a validator

deploy/testnet/add-validator.sh adds a validator to the running chain without touching genesis:

  1. node phase, on the host: creates a node home with a fresh ML-DSA-65 consensus key and operator key, shifts its ports (PORT_OFFSET) so it can share a server, installs a quacd-<name> systemd service, and waits for it to sync.
  2. Fund the printed operator address with the stake plus a little for fees.
  3. create phase: submits MsgCreateValidator with the node's ML-DSA-65 consensus key, signed by the ML-DSA-65 operator key. x/staking rejects any other key type. The new validator joins the active set two blocks later.
sudo NAME=val3 MONIKER=quac-val-3 PORT_OFFSET=10 \
  PEERS="<node-id>@127.0.0.1:26656" GENESIS=/var/lib/quac/.quacd/config/genesis.json \
  ./add-validator.sh node
# fund the operator address, then:
sudo NAME=val3 MONIKER=quac-val-3 STAKE=30000000000000uquac ./add-validator.sh create

quac-val-3 was funded with 30,010,000 test QUAC from quac-val-1's unstaked balance and staked 30,000,000, matching the other three.

Edit this page on GitHub