URMA. GitHub

OPEN PROTOCOL / RECORDS ON BITCOIN-FAMILY CHAINS

URMA mark: a broken trace that reconnects

Published.
Confirmed.
Not erasable.

URMA writes encrypted files and signed public records into blockchain transactions. A confirmed record is part of chain history: no host, platform or seized device holds the only copy, and nobody can delete it on its own. Get it back with any compatible reader and your key.

What gets cut, what stays Read the protocol
One record, start to finish
How a record survives without its host Your file is encrypted, signed and written into confirmed blockchain blocks. The host, the device and the account are single points of control and are cut. Any reader fetches the records from the chain and restores the file with your key. SINGLE POINTS OF CONTROL HOST DEVICE ACCOUNT ROUTE CUT YOUR FILE ENCRYPT · SIGN … CONFIRMED BLOCKS ANY READER YOUR KEY RECOVERED FILE

What is published

Encrypted files of any type, signed public text, code snapshots and site packages.

Where it lives

Inside Taproot transactions on Bitcoin-family blockchains, Litecoin first.

How it comes back

Any chain source, any compatible reader, your key. No account, no central service.

01 / WHAT GETS CUT. WHAT STAYS.

Take the host.
Take the device.
The record stays.

After publication URMA depends on none of the layers that get cut. The record sits in blocks that thousands of nodes keep. Removing it would mean rewriting the chain from that block, for everyone.

  1. HostingThe provider pulls the plugCut
  2. DomainDNS stops resolvingCut
  3. AccountPosts removed, login closedCut
  4. DeviceCamera, phone or laptop seizedCut
  5. Chain historyConfirmed records remain in every full copyStays

02 / HOW IT COMES BACK

  1. Fetch

    Any chain source: your own node, a public explorer, an archived block set.

  2. Verify

    Proofs checked, parts reassembled. Altered or missing bytes are refused.

  3. Open

    Private content opens with your key. Public records open for anyone.

Follow a record through the system
Litecoin testnet · 2026-09-21Git snapshot
Object
URMA’s own source code, Git HEAD snapshot
Size
841,133 bytes · 6 commit/reveal pairs
Confirmed
heights 4,892,667 and 4,892,668
Root
89de5774619943c3e628c92430a0ba0c8695000d6706d45f7ea22a84a59c50a1
Publish
233.8 s
Verified clone
≈2.11 s, HEAD restored

Our own source, published and cloned back through the chain.

03 / ONE PROTOCOL. SIX SYSTEMS.

Photography is one use case. Any bytes take the same route.
01

Capture

Journalism: originals and context that survive a seizure.

 02

Git

Code snapshots that outlive the hosting account.

 03

Wire

Public text and identities you can verify.

 04

Files

Private archives with independent recovery.

 05

Web & Names

Site packages and a names registry, no central provider.

 06

Camera

URMA’s own device: capture, publish, recover from the field.

04 / WHEN THE ROUTE BROKE

Each one lost a layer
that URMA does not need.

Hosting, domains, accounts and devices taken from publishers and newsrooms.

December 2010

WikiLeaks

Hosting, DNS and payments withdrawn. Mirrors stayed reachable.

  • Hosting
  • DNS
  • Payments
  • Copies

August 2023

Marion County Record

Police seized the newsroom’s computers, phones and file server.

  • Devices
  • Files

June 2021

Apple Daily

Raids, arrests, frozen assets. The digital edition went offline with the publisher.

  • Publisher
  • Archive

HRW · 2020

Platform removals

619 of 5,396 posts cited as evidence in rights reports were gone.

  • Posts
  • Links
Read the case studies

05 / FUNDING PROGRESS

Stage 0 is funded.
The target is 1.0.

ROSINT.org invested USD 25,000 to reach V0. Five further stages take URMA to a robust 1.0 and its own device, integrated end to end.

USD 25,000invested by ROSINT.org to reach V0
1.0target: robust protocol and own device
Funding progress
  1. Stage 0V0 KickstartFunded · ROSINT.org
  2. Stage 1V0 refinementIn progress
  3. Stage 2External auditPlanned
  4. Stage 3Product validationPlanned
  5. Stage 4DistributionPlanned
  6. Stage 5Own device · 1.0Target

06 / OPEN SOURCE

Fourteen crates.
One command.

Public Rust under 0BSD. Specification under CC0. Read the boundaries before you rely on a workflow.

Status & boundaries Crates and CLI
Install · cargoCLI
$ cargo install urma-cli --locked
$ urma --help