ProofOfLife — Your keys outlive you.

The problem

Crypto can survive its owner.
Private keys often do not.

Fortunes, sealed forever

Every year, holders die with their keys and the assets behind them become permanently unreachable. No court order, no support ticket, no recovery phrase can reopen them.

Inheritance asks for trust

Traditional solutions all share one flaw: someone else must hold the secret. A lawyer, a company, a safe-deposit box. Every custodian is a point of failure — and a temptation.

ProofOfLife is designed around the opposite principle: the operator is technically unable to read your secret. Not unwilling. Unable.

How it works

Five quiet steps.

Seal

You write down what matters — a seed phrase, a private key, instructions. It never leaves your device unencrypted.

Encrypt

Your browser encrypts the secret and wraps the key for a hardware-attested enclave. The backend receives ciphertext only.

Stay alive

Prove you're here with one tap, or let routine wallet activity speak for you. The clock resets.

Grace period

If silence stretches past your threshold, a grace window opens. Your heirs are nudged to reach you first.

Release

Only when every condition is verified does the enclave release the secret to your heir — with a signed receipt.

Security

“We can't read it.”

Not a promise — an architecture. Your secret is encrypted before leaving your device. The backend stores ciphertext. The watcher operates inside confidential computing. Release requires the configured conditions, and every release produces a verifiable receipt.

Client-side encryption

XChaCha20-Poly1305 with a fresh key per vault, sealed to the enclave's public key. Plaintext exists only in your browser's memory, briefly.

Ciphertext-only backend

The database holds encrypted blobs and wrapped keys. A compromised server yields nothing readable — demonstrated by test, not claimed.

Attested release

Decryption happens only inside hardware-attested confidential compute, only when the event chain proves the conditions were met.

Trust model

Where your secret can exist.

Plaintext exists in exactly two places. Everywhere else, it is ciphertext.

Your devicesecret entered & encrypted here
plaintext · briefly

↓

EncryptedXChaCha20-Poly1305 · sealed to the enclave key

↓

ProofOfLifeciphertext storage · timers · event log
ciphertext only

↓

Confidential computehardware-attested enclave
plaintext · inside enclave only

↓

Verified conditionsilence + grace windows proven from the event chain

↓

Heirreceives the secret re-encrypted to their key

Token

$POL

Proof Of Life — on Robinhood Chain.

0x3c1eb1f28562c8dcf59c823350de4998817db715

Begin

Leave instructions.
Not a vulnerability.

Seal your first vault in minutes. Your secret never leaves your device unencrypted.

Create your vault

PROOFOFLIFE · TEST BUILD — NO REAL SECRETS · SIMULATED ATTESTATION

Crypto can survive its owner.Private keys often do not.