The core
Canonical codecs, cryptographic primitives and proof validation live in urma-core, without network or filesystem I/O.
PROTOCOL / RECORDS & VALIDATION
A record is bytes in a block.
Not a row in a database.
URMA V0 defines how files and public records are written into blockchain transactions, how any reader verifies them, and how private content is recovered with a 32-byte root. Profiles give records meaning. Applications give people a workflow. The protocol depends on neither.
01 / ANATOMY OF A RECORD
Every record starts with the same eight bytes.Bytes 0–3URMA55 52 4d 41
Byte 400version
Byte 501…0Ckind
Bytes 6–700 00flags
| Kind | Record | Carrier | Bound |
|---|---|---|---|
| 01 | Private canonical record: encrypted bytes of any type. Content type is encrypted metadata. | Taproot reveal or offline container | Fragmented into canonical chunks under one root |
| 02 · 04 | Public post and reply. Signed by the key that authorizes the reveal. | Taproot reveal | 32,768 bytes, atomic |
| 05 | Identity profile: up to 128 UTF-8 bytes, preserved exactly. | Taproot reveal | 8–136 bytes, atomic |
| 06 | Avatar: 16×16 indexed pixels, fixed EGA16 palette, high nibble first and row-major. | Taproot reveal | Exactly 136 bytes: eight-byte header + 128 raw pixel bytes |
| 0A · 0B | Structured wires and hashtags. | Taproot reveal | 32,768 bytes, atomic |
| 0C | Profile record: eight-byte profile identifier plus opaque bytes. Names registries use it. | Taproot reveal | 32,768 bytes, atomic |
| 07 · 08 · 09 | Public multipart object: data parts, leaf manifests, one root manifest. Git snapshots and site packages travel this way. | Taproot reveal | 262,144 bytes per record; root → leaves → data |
| 03 | Private-object container for offline recovery. | Offline only | Same private format, no chain |
02 / DOCUMENTS
Stable address per revision. Checksums on the documents page.Specification
Revision 0.11 · 10 October 2026
The normative document, rendered from the exact Markdown.
Exact file
PROTOCOL.md
The Markdown of record, identified by its SHA-256.
Whitepaper
Authenticated Records for Independent Data Recovery
Non-normative scientific presentation. Cristian Zmole, ROSINT · 10 October 2026.
03 / WHAT CONFIRMATION MEANS
Confirmed once.
Carried by everyone.
A record is published as a Taproot commit and reveal. Once confirmed, it is inside a block that every full copy of the chain carries. The protocol has no delete operation and no central index, registry or relay.
- ErasureNo single party can remove a confirmed recordHolds
- AuthorshipAny reader checks the author’s key proofHolds
- PrivacyPrivate bytes stay unreadable without your keyHolds
- ReachabilityYou still need a reachable chain sourceYour side
Public & private
Public records can be read by anyone with a reader. Private objects open with your key: every object under one key is recoverable with that key alone. No wallet seed, journal, filename, database or company service is ever required.
Records on a chain
Chain observations, transaction decoding and proof-of-work validation cover Bitcoin and Litecoin. Transports belong to the runtime, not the record format.
Follow a record through the systemWhat a proof means
Verification proves the bytes are intact and which key authorized them.
Status & boundaries