Rand Protocol
Progress

Progress

Each version of the Rand full node, from the first tag to human-readable addresses. Released versions show the date they were tagged. Later versions show an estimate, at one version a week. Estimates move when the work does.

Released
18
In progress
0
Planned
1
  1. v0.1
    Released v0.1 · 16 Sept 2026

    Security review fixes and the RAND coin

    • The first tagged full node: HotStuff BFT, the shielded pool, staking, confidential programs on the zkVM.
    • Fixes for the findings of the pre-release security review.
    • The native coin is RAND, and fees are paid in RAND.
  2. v0.2
    Released v0.2 · 17 Sept 2026

    Research on human-readable addresses

    • Research on addresses that people can read.
    • The findings led to v0.5.10's address sharing: the address stays about 1,667 characters, and gains a fingerprint, payment links and QR codes.
  3. v0.3
    Released v0.3 · 18 Sept 2026

    The RPC release

    • Eleven new JSON-RPC methods and two WebSocket topics, lined up against Ethereum's and Solana's RPC.
    • The wallet commands rand viewing-key and rand tx-key.
    • The program cap as a genesis parameter, inert until a chain sets it.
  4. v0.4
    Released v0.4 · 19 Sept 2026

    The RISC-V toolchain and the Solana and Ethereum transpilers

    • rand-guest: build, check, pack, run and inspect RV32IM programs from Rust or C.
    • sbpf2rv and evm2rv: Solana and EVM programs translated to RISC-V, with outputs equal to the interpreters word for word.
    • Chain 13, whose genesis raises the program cap and the call limits; the translated ERC-20 and SPL Token were deployed on it.
  5. v0.5
    Released v0.5 · 20 Sept 2026

    RPL tokens, zUSD and the hardened bridge

    • Chain 14, cut and tagged the same day. One USDT made the full round trip on each of Ethereum, Binance Smart Chain, Tron and Solana: locked, minted as zUSD, burned, released. A second round left 36 zUSD minted against 36 USDT in custody.
    • RPL, the token standard: a token is an entry in the ledger's registry, created by anyone for a fee in RAND, and moves in the same proof as RAND, which hides which asset moved.
    • zUSD is registered on chain 14 as one bridged token with seven backings: USDT and USDC on Ethereum, Binance Smart Chain and Solana, and USDT on Tron.
    • Bridge hardening: a daily mint cap per backing, a pause key, a post-quantum co-signature on every mint, and bounded block timestamps.
    • Every proof is bound to its whole transaction. From the security audit: the eighteen validator keys were rotated, and a faucet mint now opens its commitment.
  6. v0.5.9
    Released v0.5.9 · 27 Sept 2026

    Chain 15 and the audit fixes

    • Chain 15, cut on 26 September from chain 14's bridge position: the 10 zUSD still outstanding were carried over at genesis, backed by 9 USDT on Tron and 1 USDT on Solana, so supply equals custody from block 0. The fleet was then rolled to v0.5.9.
    • The v0.5.x patch releases up to v0.5.9 fixed the findings of three internal audit rounds led by a co-founder and three internal scans (no independent audit has been performed yet): a consensus lock that survives restarts, one quorum certificate stored per block, call proofs capped at tier 14, and validators that keep one day of blocks beside a full archive.
    • Chain 15's genesis turns on the gated fixes: a faucet limited to 16 named wallets and a budget per epoch, a two-epoch bond delay, every consensus signature bound to the genesis, and the bridge's rules v2 with a global mint cap and rotatable post-quantum keys. 26 validators now sign it.
  7. v0.5.10 · v0.5.11
    Released v0.5.10 · v0.5.11 · 28 Sept 2026

    Address sharing, the encrypted memo, and the vesting register

    • v0.5.10: a 16-character address fingerprint, randpay: payment links and QR codes, and an encrypted memo sealed inside the note envelope.
    • v0.5.11: a public vesting register for locked allocations (team, investors, partners), outside the shielded pool and genesis-gated; each entry's amount, schedule, claims and bonded validator are public under the holder's key. Active on no chain yet.
  8. v0.6
    Released v0.6 · 28 Sept 2026

    The zkVM, recursion-VM and aggregation fixes

    • Most findings of the 27–28 September zkVM, ISA and recursion-VM reviews fixed in code: four recursion-VM soundness breaks (dormant, since aggregation is off everywhere), the small-table call-input leak closed for new proofs, aggregator slashing retired, and the bundle verifier key kept warm off the consensus loop.
    • The branch-free bundle guest and the hardening_v6 genesis switch (program-table floor, call binding, uncallable deploys refused) built for the next chain cut. Rolled to all 26 validators on 28 September.
    • Still open after v0.6: the CON-4 consensus lock-release counterexample (fix designed, not shipped), bridge key custody, the GUI wallets' witness requests to the public RPC, and the forged-aggregate test (#45) before aggregation can be enabled.
  9. v0.6.1 · chain 16
    Released v0.6.1 · chain 16 · 28 Sept 2026

    Constraint set 7 and a new genesis

    • Constraint set 7, a hard fork: every LogUp terminal blinded and every table floored at 128 rows, so a proof reveals its 34 public values and nothing more; 32-bit range checks on input words; salted verifier keys; the recursion VM's in-circuit verifier.
    • Chain 16, live 28 September 16:39 UTC with the branch-free bundle guest and hardening_v6: 26 validators at 1,000 RAND each, all operated by the founding team, a quorum of 18; the 10 zUSD carried over, backed by 9 USDT on Tron and 1 on Solana; no aggregation section.
    • On chains 14 and 15 a transfer proof revealed whether RAND or a token moved and a fingerprint of the notes spent, and a call proof let low-entropy inputs be guessed; chain 16 closes both.
  10. v0.6.2
    Released v0.6.2 · 29 Sept 2026

    Delegated proving, Phase 1

    • rand-prover, and rand-node run --prover: a sealed proving service a wallet's owner runs, so a browser extension or a phone without 8 GB of memory can send. Jobs are sealed with ML-KEM-768 and ChaCha20-Poly1305, the witness is zeroised, and the wallet verifies the returned proof itself.
    • Phase 1 hands the prover the spend key, so delegating a proof is handing over custody: pair only a machine you run. Rolled to all 26 nodes on 29 September; superseded on chain 17 by split authorisation (v0.6.3).
    • The clients' v0.6.5 release pairs a prover from Settings, and the desktop app can be one.
  11. v0.6.3 · v0.6.4 · chain 17
    Released v0.6.3 · v0.6.4 · chain 17 · 29 Sept 2026

    Delegated proving, Phase 2: split authorisation, and a new genesis

    • The bundle proof no longer takes the spend key. The wallet makes a small authorisation proof itself (tier 10, about 7 s, 1.36 MB) and any paired prover may make the heavy bundle proof from the viewing key: it can read that wallet's history, and it cannot spend. A prover may quote a fee in RAND, paid as one shielded output inside the same transaction; the wallet caps it (1 RAND by default).
    • A hard fork, so a new genesis: chain 17 live 2026-09-29 03:03 UTC, cut from a snapshot of chain 16 with the same 26 validators, the 10 zUSD and their backing carried over; the proof cap is 4 MiB so a block has room for three proofs. A transfer now carries about 2.85 MB of proofs, seven to a 20 MiB block. v0.6.4 is the launch record.
    • Measured on 29 September: a v3 bundle proof 102 s locally, 108–111 s through a paired prover; a non-own prover proved a 5 RAND send end to end.
  12. v0.6.6
    Released v0.6.6 · 29 Sept 2026

    Gas: pay per instruction in RAND (constraint set 8), built for chain 18

    • The zkVM meters every run in circuit (one gas column, one public value); a call declares a gas limit and pays it at the chain's gas and byte prices, and under the dynamic section the prices move once a block with fullness. Every bundle declares the pinned limit 20,479.
    • Constraint set 8 changes every verifier key, so it could only run on a new chain. v0.6.6 was tagged and never cut as tagged: its content reached a chain the same day as v0.6.7-rc1, rebased onto split authorisation.
  13. v0.6.7 · chain 18
    Released v0.6.7 · chain 18 · 29 Sept 2026

    Chain 18: gas metering and the encrypted memo, live

    • Chain 18, cut on 29 September at 04:56 UTC on v0.6.7-rc1 and rolled node by node to v0.6.7: the first gas-metered chain (constraint set 8), with split authorisation from chain 17 and the 1,860-byte note envelope that carries an encrypted memo. 26 validators at 1,000 RAND each, a quorum of 18, proofs up to 4 MiB. RAND balances and the 10 zUSD outstanding were carried over at genesis.
    • A confidential call now declares a gas limit the circuit enforces and pays for it and for its bytes at prices that move with each block. Four calls measured on 30 September cost between 0.0057 and 0.0075 RAND.
    • Four example programs were deployed and called on chain 18 on 30 September: an anonymous vote over a Keccak allowlist, a proof of liabilities over a SHA-256 sum tree, an off-chain ledger carried between calls, and a private credit decision from a published model.
  14. v0.6.7 · chain 19
    Released v0.6.7 · chain 19 · 1 Oct 2026

    Chain 19: chain 18 again, with the redeployed bridge endpoints

    • Chain 19 went live on 1 October at 03:43 UTC, cut from chain 18 at a snapshot of height 141,935 and run on the same v0.6.7 build by the same 26 validators. Every rule and limit is chain 18's; the genesis names the Ethereum, BNB Chain and Tron bridge endpoints redeployed on 30 September.
    • Operator wallets and the bridged zUSD carried over. Programs do not carry over a cut, so the four example programs were deployed again on chain 19. The validators' prover pool at prover.randprotocol.org proves for chain 19.
    • Rand Wallet v0.6.7 was released the same day for chain 19: every client's core vendors fullnode v0.6.7 and refuses any other chain, and the wallet's version now matches the node's.
  15. v0.6.8 · chain 20
    Released v0.6.8 · chain 20 · 1 Oct 2026

    Chain 20: program state, bridge fees and the last audit-v6 fixes

    • Chain 20 went live on 1 October at 06:17 UTC on v0.6.8, a hard fork from chain 19's state at height 7,258, rolled all-stop by the same 26 validators. Every proof and signed message is now bound to the chain's genesis, so nothing made for one chain verifies on another, and a wallet needs v0.6.8 to send.
    • RPL-2: a program can keep state in cells and hold a vault, and an Invoke reads and writes them in one proved step, at 0.01 RAND a new cell. zUSD pays a 0.1% bridge fee each way, in zUSD, to a treasury note, and custody still equals supply.
    • The rest of audit v6: the consensus lock is no longer released automatically (CON-4) and views advance on timeout certificates (CH-1); a public RPC listener with a fixed method set; gas price ceilings; validators admitted by vote; guardian rotations that need possession and a day's delay.
  16. Wallet v0.6.8 · chain 20
    Released Wallet v0.6.8 · chain 20 · 1 Oct 2026

    Rand Wallet v0.6.8: the apps send on chain 20

    • Every app's core now vendors fullnode v0.6.8 and binds what it proves and signs to chain 20's genesis, so the phone, desktop and browser wallets send on chain 20 again. A wallet uses the RandProtocol prover by default for the bundle proof, and a prover of your own stays the private choice.
  17. v0.8.0 · chain 21
    Released v0.8.0 · chain 21 · 12 Oct 2026

    Chain 21: constraint set 9, burned fees, perps and multisig

    • Chain 21 went live on 12 October at 10:31 UTC on fullnode v0.8.0, a hard fork of chain 20 (its bridge state from the snapshot at height 814,702, the operator wallets' balances) rolled all-stop by the same 26 validators. The zkVM is on constraint set 9, Merkle spans in the recursion verifier and a chip for Dilithium2 arithmetic, so every verifier key and the proof encoding changed: v0.8.0 refuses chains 18 to 20, and a wallet needs v0.8.0 to send.
    • Every transaction's fee floor is now burned rather than paid to the proposer, who keeps only the tip. RPL-3 perpetual futures: one market, BTC-PERP settled in zUSD at 20× leverage, with a prover off chain. Multisig accounts: M-of-N Dilithium2 keys over a public balance, 1 RAND to create; the foundation treasury, 100,000 RAND behind 2 of 3 keys, is the genesis account. Private multisig: an M-of-N policy proved as a bundle's authorisation at tier 18, so the chain learns only that a multisig signed. Proofs may be 6 MiB.
    • Node-only changes since v0.6.8: signed, CI-built releases from v0.7.0; proving on every core, or the GPU, from v0.7.1; compact blocks, a startup checkpoint, a verify cache and off-loop block apply in v0.8.0; scan heads cut a wallet's sync bytes by 2.26×. The rand command line from the v0.8.0 release sends on chain 21, and so does Rand Wallet v0.8.0, below.
  18. Wallet v0.8.0 · chain 21
    Released Wallet v0.8.0 · chain 21 · 12 Oct 2026

    Rand Wallet v0.8.0: the apps send on chain 21, and sign for a private multisig

    • Every app's core now vendors fullnode v0.8.0, so the phone, desktop, extension and web wallets send on chain 21; the 0.7.x apps refuse it, and v0.8.0 refuses chain 20. Keys, addresses and viewing keys carry over, and a wallet that scanned chain 20 rescans from chain 21's genesis after one banner. Every app can sign a private multisig proposal with its own Dilithium2 key, checking the payee before it signs.
  19. next Estimate
    Planned next · 19 Oct 2026 (estimate)

    The example programs on chain 21 and aggregation's last test

    • Estimate. The four example programs redeployed on chain 21; the forged-aggregate test that block aggregation still waits on.

Dates marked “estimate” are plans, not commitments. The documentation describes what runs on the testnet today.