// SYS_INIT // CLIENT_OK // TOR_LINKED // XMR_BAL: 0.0421

v0.1 // ENCRYPTED OFFSITE PROTOCOL

STORE / ROUTE / PAY

Backups nobody can read — not us, not your ISP, not anyone who breaks in, not a future owner of this company.

> archive.init --cert ./your.pem > archive.fund --xmr 0.05 > archive.push ~/.life [OK] encrypted. routed. forgotten.

// PROTOCOL_LAYERS

Stacked privacy. Each layer fails closed.

L1

RESTIC // crypt

AES-256 + Poly1305 client-side. Keys never leave your device. The blob is encrypted on your machine. Server only ever holds opaque ciphertext — wherever the operator parks the bits is irrelevant, they cannot decrypt them.

L2

TOR // ghost

Onion-routed transport. Three hops between you and us. Origin IP unknowable on both sides.

L3

mTLS // ident

Your client cert is your account. SHA256 of the cert is your only ID. No password, no email, no recovery flow. Lose the cert, lose the archive.

L4

XMR // settle

Pay-as-you-go in Monero. Balance burns down as you push bytes. Top up when needed. No subscription, no invoice trail. Subaddress per client, stealth addresses, ring signatures — the chain forgets who paid.

// THREAT_VECTORS

What we are designed to survive.

VECTORSTATUS
Network observer (ISP / transit)CONTAINED — tor + tls
Server compromiseCONTAINED — ciphertext only
Disk seizureCONTAINED — opaque blobs, no keys
Insider with admin accessCONTAINED — no keys, no plaintext, no PII to leak
Loss of your client certFATAL — archive lost
Loss of your passphraseFATAL — data lost

// DEPLOY

JACK_IN.

Open source. Reproducible builds. Zero PII, zero analytics, zero phone-home.