✦

Pearl Legacy

A dead-man's-switch PRL inheritance vault — your heir inherits on silence, never on trust.

Plan the vault

Two leaves under a NUMS internal key (no keypath bypass possible): the heartbeat leaf the owner can always spend, and the heir leaf that unlocks only after n blocks of inactivity.

Owner key

Stays in this page's memory only. Never sent anywhere. Never written to disk by this page.

Heir identity

The heir's key, not yours. Owner and heir must differ — that is refused, loudly, if they match.

Inactivity threshold

≈ 100.1 days at 194 s/block (estimate only — the chain enforces blocks, never time).
OP_CHECKSEQUENCEVERIFY is 16-bit: a "one year" setting is impossible and is refused, not silently truncated.

The vault

Load a vault spec to see the address, the descriptor, and what each key can do. The spec re-derives everything and refuses tampering loudly.

This page can keep the spec (never private keys) in this browser's localStorage for convenience. It survives even if localStorage is hostile or disabled — it just won't persist.

Watch

Read-only. Blockbook is only ever fetched with GET — never trusted blindly: every returned UTXO's script is checked against the vault contract before it is believed.

Only GET requests are ever made. Default: the network's public endpoint.

Claim & refresh

Both transactions are built and signed locally. Nothing is broadcast until you explicitly confirm — twice.

Heir claim

One claim transaction spends one vault UTXO via the heir leaf (nSequence = n, hard-coded). Repeat per UTXO.

The claim input's nSequence is set to n exactly; the UTXO must be at least n blocks old at the current height.

Standalone verifier

Paste a legacy:v1:… descriptor and the address it claims to describe. The page recomputes the contract from the keys + n and refuses loudly on any mismatch — the descriptor itself is not signed, so the claimed address must come from a source you trust. No keys needed — verification is trustless.

Honest limits