Network / Testnet

Run the network locally before joining the public rehearsal.

Actum is in protocol design and pre-testnet implementation. The work is open so assumptions, code, proofs, and operational procedures can be challenged before launch.

01

Read the protocol

Start with the architecture, normative specifications, and security assumptions in the public repository.

02

Run locally

Build the deterministic kernel and rehearse a local network before connecting to shared infrastructure.

03

Verify independently

Use the published vectors and verifier interfaces to check canonical commitments and finalized evidence.

04

Join the rehearsal

Contribute validator, prover, builder, storage, wallet, or application capacity as the public testnet opens.

Pre-testnet. Core protocol implemented, qualification in progress.

The bounded validator storage contract — a 1 TiB physical profile with witnessed replay roots, 8-of-12 archive custody, crash-safe pruning, and checkpoint sync — is implemented and locally qualified, alongside the native PQ cash plane, multi-asset tokenization, native wallet custody, and the testnet faucet flow. The operator wallet CLI now covers the full local lifecycle: passphrase-protected seed custody, deterministic ML-KEM agreement keys, DID create/rotate/recover, signed cash sessions and transfers, verifier bonding, duty receipts, and reward redemption — each with published golden vectors so independent clients can verify them without our implementation.

Remaining launch-gate work is tracked openly and is deliberately not claimed as done: the ML-DSA verifier is still being arithmetized for in-circuit proving, the pre-launch formal verification program is incomplete, ActiveBridge awaits staged external-rail pilots, and identity qualification needs runs on physical Apple and Android hardware. Independent security, privacy, and formal-methods review has not taken place. Nothing here is audited, and no value-bearing guarantee is offered.

Open GitHub