Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

Sikh Bitcoin · Advanced · Lesson 15 of 21

Descriptors make a wallet policy portable

Preserve the information that turns keys into the intended outputs.

About 14 minutes with practice. You only need something to take notes with. No real wallet details or payments are part of this lesson.

Course contents · Lesson 15 of 21
  1. Read the whitepaper as an argument
  2. Hashes and Merkle commitments
  3. UTXOs, change and accounting
  4. Scripts describe spending conditions
  5. Signatures and what they authorize
  6. Block headers and the chain of work
  7. Difficulty, hashrate and noisy observations
  8. Issuance, fees and incentives
  9. Mempools and policy are not consensus
  10. Fee changes: RBF and CPFP
  11. SegWit and transaction weight
  12. Taproot and Schnorr: useful, not magical
  13. HD wallets and derivation paths
  14. PSBT: separate construction from signing
  15. Descriptors make a wallet policy portable
  16. Full nodes, pruning and verification
  17. Reorganizations and lightweight evidence
  18. Lightning channels and HTLCs
  19. Lightning liquidity has direction
  20. Soft forks, proposals and human coordination
  21. Capstone: trace a payment end to end

What you will learn

  • Explain what a descriptor describes.
  • Identify limits of a key-only backup.

Keys do not describe every choice

A replacement wallet must know how to construct the scripts and addresses it should watch. Output script descriptors express script types, keys and derivation information in a structured language. BIP 380 describes general syntax and checksums. This addresses a gap in backups that preserve a secret but omit the policy surrounding it.

A checksum is useful but narrow

A descriptor checksum can help detect transcription errors. It does not certify that the descriptor belongs to you or represents the intended signers. A maliciously supplied descriptor can be perfectly well formed. Verify policy and derived receiving information through the supported wallet workflow rather than trusting syntactic validity alone.

Protect both confidentiality and continuity

A descriptor can contain public or private key material depending on the export. Never assume every descriptor is safe to publish. Even a watch-only export can disclose financial history. A good recovery package records the required format and metadata under appropriate access controls. For a classroom exercise, draw the policy rather than copying a live descriptor. Ask whether a second compatible implementation can interpret it before treating portability as established.

Practice on paper

A multisig backup includes one signer’s seed but omits the other public keys and script policy. Why might that be insufficient even if another signer is available?

Reveal the worked answer

The wallet may be unable to reconstruct the exact addresses and spending conditions. Recovery needs the required key threshold and complete policy metadata, not simply an unrelated collection of seeds.

Check your understanding

Choose an answer in your head or on paper, then reveal the explanation. Retry whenever you like. Answers are not submitted or scored; completion marks are your own learning notes.

1. Does a valid checksum prove ownership?

  • Yes
  • No
Reveal answer 1

No. It primarily detects errors, not authorization.

2. Are all descriptors safe to post publicly?

  • Yes
  • No
Reveal answer 2

No. They may contain private material or sensitive public-wallet information.

Take this with you

A portable recovery plan preserves the exact policy, not just a label.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.