Continuity Transfer

A non-custodial Bitcoin recovery and inheritance plan

Continuity Transfer lets you define a Bitcoin-enforced recovery and inheritance plan without giving up custody. You keep full control today, while specifying exactly who can recover or receive funds in the future. No accounts, no custody, no counterparty risk. Bitcoin enforces the rules.

How Continuity works

Continuity creates a Bitcoin-enforced plan first, then lets you fund it from your own wallet.

▸Example: See a real-world Continuity flow

Walk through a complete example before creating a plan.

This example is illustrative. No Bitcoin moves in Steps 1–2.

This example shows exactly what happens — and what does NOT happen — when you use Continuity.

Step 1 — Create the plan (no Bitcoin moves)

Alice enters:

  • Recipient public key: Bob
  • Recovery public key: Alice
  • Unlock date: January 1, 2030
  • After unlock: Recovery key + Recipient key

She clicks Create Continuity Package.

Result:

  • A Bitcoin script is created
  • A funding address is derived
  • A Continuity Package (JSON + instructions) is generated

No Bitcoin has moved yet. At this stage, Alice has only created rules and instructions.

Step 2 — Review the Continuity Package

The Continuity Package clearly states:

Before January 1, 2030:
Alice (recovery key) can spend

After January 1, 2030:
Bob (recipient key) can spend
Alice can still recover (by choice)

It also includes the exact Bitcoin funding address, the rules enforced by Bitcoin, and instructions for independent verification.

The Continuity Package defines what will be allowed, not when Bitcoin moves.

Step 3 — Fund the address (this is when Bitcoin moves)

Alice opens her own Bitcoin wallet and sends funds to the address shown in the Continuity Package:

bc1q...

This is the moment Bitcoin actually moves.

From this point forward:

  • The funds are locked by the script
  • The rules cannot be changed
  • EverCert is no longer involved

From this point forward, EverCert is no longer involved.

Step 4 — Verify anytime (with or without EverCert)

Anyone can verify the plan by loading the Continuity Package into Verify Plan.

They can independently confirm:

  • The spending rules
  • The unlock date
  • The funding transaction
  • Who can spend, and when

Verification works even if EverCert is offline or no longer exists.

Step 5 — Spending later (future event)

Before January 1, 2030:
Alice can recover the Bitcoin if needed

After January 1, 2030:
Bob can spend the Bitcoin using his key
Alice may still recover if that option was chosen

Bitcoin enforces these rules automatically.

Key takeaway

The Continuity Package defines the rules.
Funding the address activates them.

EverCert never moves your Bitcoin and never holds your keys.

Create a Continuity Package

This step creates Bitcoin-enforced rules and a funding address. No Bitcoin moves yet.

⚠

Example keys prefilled — DO NOT USE WITH REAL FUNDS

These keys are for testing the UI only. Replace them with your own keys before funding. Never send Bitcoin to a plan created with example keys.

Example only. Replace with your own key before funding.

Example only. Replace with your own key before funding.

The moment when recipient access becomes valid.

After unlock, both keys may spend. Funds remain recoverable.

For your own notes only. Not enforced by Bitcoin. Included in the Continuity Package.

EverCert never holds keys or funds. These public keys define spending rules enforced by Bitcoin.

This creates Bitcoin-enforced recovery rules and a funding address. No Bitcoin moves yet.

Non-custodial. No keys shared. Verifiable forever.

▸

Continuity Guarantees

  • •EverCert cannot move or access your Bitcoin
  • •No service dependency after creation
  • •Rules are enforced by Bitcoin, not by EverCert
  • •Proofs remain independently verifiable forever

This approach is commonly used for Bitcoin inheritance planning, long-term recovery, and emergency access. Because the rules are enforced by Bitcoin itself, verification remains possible decades into the future.