Prepare & publish
Private bytes are encrypted under your key; public bytes are signed. The runtime plans the publication, quotes the fees, and broadcasts the commit and reveal transactions.
ARCHITECTURE / FOLLOW A RECORD
Write. Confirm.
Recover anywhere.
The application can change, the host can vanish, the device can be taken. The record format stays the same and the recovery inputs stay small.
Retrieve & check
A reader asks any chain source for the transactions: your own node, a public source, an archived block set. Decoding and core validation turn what it receives into evidence.
Reconstruct & use
The file, Git snapshot or site package is reassembled; anything incomplete or altered is refused. Private content opens with your key. The result is ordinary files on disk.
02 / WHO HOLDS WHAT
| Role | Holds | Needed to recover |
|---|---|---|
| Your key | 32 random bytes. Opens every private object under it. | Yes, for private content. |
| Author key | Signs public records. A pseudonym on the chain, not a registered name. | No. Readers verify it. |
| Wallet | Pays publication fees. | No. |
| Chain source | Any node or service that returns the confirmed transactions. | Yes. Any one will do. |
| Publisher journal, app database, company service | Convenience during publication. | Never. |
BUILD ON IT
Keep the key.
Publish before the loss.
Everything else is replaceable.
Explore the implementation