The implementation
Fourteen public Rust crates and the urma command line: core validation, identities, wallets, publication and recovery, Wire, Git, files, Names and Web. Source under 0BSD, specification under CC0.
STATUS / SCOPE & BOUNDARIES
Working code.
Explicit boundaries.
URMA is in active development. Every claim on this site is scoped to a revision, a network and an observation.
01 / ON THE RECORD
Public-network observations, dated and scoped.| Date | What happened | Network | Scope |
|---|---|---|---|
| 2026-09-21 | Git HEAD snapshot of URMA’s own source, 841,133 bytes in 6 commit/reveal pairs, confirmed at heights 4,892,667 and 4,892,668. Two verified clones restored HEAD in ≈2.11 s each. | Litecoin testnet | One source revision, single leaf. Not a block-inclusion deadline or mainnet claim. |
| 2026-09-24 | Administered names registry exercised and a Web site package published and recovered. | Litecoin testnet | Selected registry only. Not general availability. |
| 2026-09-25 | Portal gateway served name-bound Web packages with verified stored objects and proof endpoints. | Litecoin testnet deployment | Historical observation of one deployment, not a resolver service. |
Not erasable, precisely
A confirmed record is part of the chain. No host, platform, author or operator can delete it on its own; removing it from canonical history means reorganizing the chain from its containing block. URMA has no delete operation and no mandatory central provider.
Two things stay on your side: keeping your key, and reaching a chain source from where you are.
Per revision
Every claim is tied to a source revision and a network. Conformance and interoperability are proven per revision; the specification lists its own completion conditions.
Review the trust
No external security audit has been performed yet. A valid record proves intact bytes and an authorizing key, not the truth of its content.
External audit is Stage 2Remaining scope
Full conformance and rejection review, fuzzing and hostile-source stress; measured recovery at the full multipart ceiling; broader independently verified interoperability and platform coverage; multi-leaf public-network acceptance; live Wire publication acceptance; Capture and Archive application and device acceptance; Names/Web profile publication and Bitcoin mainnet adapters.