Security & audits

What does not exist yet

No external audit has been performed. The first one is a gate on going public, not an afterthought. There is no bug bounty yet. The security contact publishes here before any public network does — until then, the repository is the surface and the test suite is the referee.

What exists

The protocol's correctness posture is differential and adversarial, in code that runs on every commit:

A reference model. Production settlement behavior must match an independent reference implementation on differential tests; any divergence is adjudicated against the frozen spec text — whichever side disagrees with the spec is the bug.

Byte-identical consensus. Multi-node tests pin that every validator computes identical state, byte for byte, through fork and halt scenarios — and the SDK's signing vectors are generated from the consensus types and checked cross-language.

Adversarial suites. Forgery batteries at the admission boundary (signature and authority checks on every transaction kind, default-deny), replay protection, and negative tests through the running node.

The claims audit behind this site. The home page's one sentence — rules nobody can rewrite — was verified against the emergency-controls surface before it shipped; the controls and their limits are public on Emergency controls.

Key handling

The SDK signs locally and never transmits a secret. The upcoming browser console's keystore is devnet-only by policy and undergoes formal security review before it can ever touch a surface where keys hold value — that review is a standing gate, recorded now so it is in place before the console is built.