reports · tests · benchmarks

Research

Built by an auditor, broken by one, until it held. The record — not a slogan — is the argument.

the security record

Adversarial from day one.

Every essential protection a sovereign ledger needs was implemented, then attacked relentlessly. Around a dozen real vulnerabilities were found and fixed in the reference implementation. The browser wallet then went through five rounds of independent adversarial audit — each finding closed and re-verified against the live network.

Wallet — 5 audit rounds, all closed

XSS surface eliminated; SHA-256 + network-domain signing; balance counted only from on-device membership proofs; two-node completeness & maturity cross-check; BigInt amounts; 600k-round PBKDF2; mandatory key backup; strict CSP.

Signing ↔ node parity — sealed

A cross-side test proves byte-for-byte agreement on the domain, serialization, SHA-256 digest, compact signature, low-S handling and transaction id — run against the real node code and the real in-browser crypto library.

tests

What we actually run.

suitecoversresult
accumulatorroot parity · inclusion · exclusion (randomized sizes)pass
wallet ↔ node paritydomain · serialization · digest · signature · txid9 / 9
light clientheader PoW chain · coin proof · non-membershippass
consensus & reorgmost-work fork choice · reorg mempool reclaim · MTPpass
double-spend / dup-inputwithin-block & cross-block spend attemptsrejected
fuzz / long-stressmalformed blocks & txs · sustained loadpass
guardian / vaultbounded recovery · limits · challenge resolutionpass

Suites live in the reference repository as test_*.py / attack_*.py. Names, not adjectives.

benchmarks

Measured, on the live network.

~2 min
block time (target)
0.67 s
balance proof (cached)
6.3 → 0.67 s
owner proofs: first vs cached
30 / 5 s
light-endpoint rate limit

The batch light endpoint rebuilds state once per tip and caches proofs per owner; the wallet verifies a full balance against two nodes in under a second on a warm cache.

whitepaper

A candid research note — including what didn't work.

Refutation-Matured Audit (RMA) explores letting off-chain agents point at a suspected invariant violation and having the chain resolve it deterministically. The note is deliberately honest: an internal red-team demolished an earlier draft's economic claims, and the paper retracts them in full — reporting what runs, what does not yet hold, and what stays open. Honesty about a negative result is the point.