LAZARUS PROTOCOL

🔐 LAZARUS VAULT TERMINAL NO VAULT DETECTED

No active vault found on this device. Create a new LAZARUS vault to begin your annual heartbeat protocol, or import an existing vault configuration from another device.

🔐

CREATE NEW VAULT

Initialize a new annual heartbeat contract. Designate your beneficiary and lock amount.

📥

IMPORT VAULT

Restore a vault from an exported JSON config file from another device.

HOW IT WORKS: You create a vault, designate a CAPS address to receive the funds if something happens to you, and check in once a year. Miss the check-in? After a 30-day grace period, the beneficiary can claim the vault. Simple. Trustless. Permanent.

🔐 VAULT INITIALIZATION WIZARD SETUP

OWNER

──

BENEFICIARY

──

CONFIRM

YOUR CAPS ADDRESS (OWNER / CONTROLLER)

This is your wallet address — the controller of the vault. This field is for identity purposes only; funds are not moved automatically on-chain. Use your Cap-Boy wallet address (starts with cap1).

⚠️ SECURITY NOTICE: Never enter your seed phrase or private key here. Only enter a public CAPS wallet address.

ACTIVE VAULT IDENTIFIER

LAZ-——————

❤️ HEARTBEAT STATUS ALIVE

—

DAYS

—h —m

DAYS UNTIL PULSE REQUIRED

Send your annual heartbeat to confirm you're still operational. This resets the 365-day countdown. Do this once a year — no more, no less.

📋 VAULT DETAILS CLASSIFIED

OWNER ADDRESS

—

BENEFICIARY

—

DECLARED AMOUNT

—

VAULT CREATED

—

LAST PULSE

—

NEXT DEADLINE

—

PULSE LOG — LAST 8 ENTRIES

◆No pulse entries yet.

☠️ LAZARUS TRIGGER DETECTED TRIGGERED

☠️

VAULT TRIGGERED — ANNUAL DEADLINE MISSED

The vault owner did not send a heartbeat pulse before the annual deadline. The LAZARUS contingency has been activated. The designated beneficiary may now claim this vault.

GRACE PERIOD REMAINING 30 DAYS LEFT

VAULT ID

—

BENEFICIARY

—

VAULT AMOUNT

—

OWNER — STILL ALIVE? If this trigger was a mistake (you simply missed the check-in), click OVERRIDE — I AM ALIVE to restore the vault and restart the annual countdown. This is only available during the 30-day grace period.

BENEFICIARY: If you are the designated recipient, click CLAIM VAULT to register the claim. You will then need to manually broadcast a CapStash transaction to receive the declared CAPS from the owner's wallet to yours.

📦 VAULT RELEASED COMPLETE

🏛️

CONTRACT EXECUTED

The LAZARUS clause has been fulfilled. This vault is now marked as released. Ensure the declared CAPS have been manually broadcast to the beneficiary's wallet.

VAULT ID

—

BENEFICIARY

—

AMOUNT DECLARED

—

RELEASED AT

—

NEXT STEPS: The vault record is archived. To set up a new LAZARUS vault, return to the home screen and create a new vault.

← RETURN TO WEN

📤 VAULT BACKUP — EXPORT / IMPORT SECURE TRANSFER

CRITICAL: Your vault data lives in this browser's localStorage. If you clear your browser data, switch devices, or use a different browser, you MUST import your vault config to maintain your heartbeat countdown. Export your vault and store the JSON file somewhere safe — an encrypted drive, an external disk, or a trusted cloud service.

📤 EXPORT VAULT CONFIG

Download your vault configuration as an encrypted JSON file. Store it alongside your wallet backup phrase. Active vault: —

📥 IMPORT VAULT CONFIG

Restore a vault from a previously exported JSON file. This will set the imported vault as your active vault on this device.

📂 SELECT VAULT.JSON

🔐 SHAMIR SHARD PROTECTION — KEY SPLIT WIZARD OWNER ONLY

⚠️ MAXIMUM SECURITY NOTICE: You are about to enter your wallet seed phrase. This data is never transmitted or stored. It is processed entirely in RAM using WebCrypto (AES-256-GCM + PBKDF2/200k). The seed phrase is wiped from memory immediately after splitting.

HOW IT WORKS: Your seed is split into 3 cryptographic shards using Shamir's Secret Sharing (GF-256). Any 2 shards can reconstruct it — 1 shard alone reveals zero information. Shard 1 is encrypted and stored on-chain (OP_RETURN). Shard 2 stays with you. Shard 3 goes to your beneficiary.

ENTER YOUR SEED PHRASE (12 OR 24 WORDS)

Separate words with single spaces. The field will be wiped immediately after processing. Do not screenshot this page.

🔑 STEP 1 — CLAIM PASSWORD

CRITICAL: This password encrypts Shard 1 before it goes on-chain. You MUST share it with your beneficiary through a separate, secure channel (in person, handwritten note, encrypted message). Anyone with this password + Shard 3 can recover the wallet.

— 16-BYTE RANDOM KEY — WRITE THIS DOWN

📂 STEP 2 — SHARD 2 (YOUR COPY — KEEP PRIVATE)

This is your shard. Save it in your vault export JSON, an encrypted file, or a hardware wallet backup. Do NOT give this to your beneficiary. This is your "proof of life" shard.

🔒 SHARD 2 — OWNER

🎯 STEP 3 — SHARD 3 (GIVE TO BENEFICIARY)

Give this shard to your designated beneficiary. They cannot use it alone. They need: this shard + Shard 1 (from the CapStash blockchain) + the Claim Password. Tell them to keep it somewhere safe.

🎯 SHARD 3 — BENEFICIARY

⛓️ STEP 4 — BROADCAST SHARD 1 ON-CHAIN (OP_RETURN)

This hex payload contains Shard 1, encrypted with your Claim Password (AES-256-GCM, PBKDF2/200k iterations). Include it as an OP_RETURN output in any CapStash transaction. Once broadcast, it is permanently anchored on the blockchain. The raw hex is safe to share publicly — it is encrypted.

🔴 SHARD 1 — ON-CHAIN (ENCRYPTED)

— / 80 bytes

HOW TO BROADCAST: Open your CapStash wallet (Cap-Boy or CLI), create any transaction (e.g., send 0.001 CAPS to yourself), and add this hex string as an OP_RETURN/memo field. Save the resulting TX ID — you'll need it for recovery.

RECOMMENDED: Download the full shard package as a JSON file. Store it on an encrypted drive. Keep Shard 2 and Shard 3 in different physical locations. Memorize or securely store the Claim Password separately from both shards.

🧩 SHARD RECOVERY TERMINAL — BENEFICIARY SECURE RECOVER

FETCH SHARD 1

──

DECRYPT

──

RECOVERED

BENEFICIARY INSTRUCTIONS: You need 3 things to recover the wallet:

Shard 1 — from the CapStash blockchain (TX ID) or pasted hex
Claim Password — shared by the vault owner out-of-band
Shard 3 — your designated shard given to you by the owner

HOW TO OBTAIN SHARD 1

The vault owner broadcast an OP_RETURN transaction anchoring Shard 1 on-chain. They should have saved the TX ID. If you have it, enter it here to fetch the shard automatically from the CapStash mempool.

OWNER ADDRESS	—
BENEFICIARY	—
LOCKED AMOUNT	—
CHECK-IN INTERVAL	365 days
GRACE PERIOD	30 days
VAULT NOTE	—

⚠️ REVIEW — VAULT CONFIGURATION

CONTRACT EXECUTED

LAZARUS
PROTOCOL