DUCAT’SBitcoin Guild
All curriculum
WALLET MECHANICS AND SAFE USE

How a Bitcoin wallet works

A wallet is software and data that finds spendable outputs, constructs transactions, protects signing authority and tracks tentative network state. This path joins the safe-use exercises to the key, descriptor, coin-selection and recovery mechanisms underneath them.

20 connected lessons Practice in every lesson
01

See the whole system first

Each specialist lesson expands one relationship in this end-to-end map.

  1. 01
    Describe

    A descriptor tells the wallet which scripts and key branches to derive.

  2. 02
    Scan

    The wallet asks a node or filter source which derived scripts have activity.

  3. 03
    Select

    Coin selection chooses whole outputs while balancing fee, change and privacy.

  4. 04
    Construct

    Inputs, outputs, fee, change, sequence and locktime become a candidate transaction.

  5. 05
    Review and sign

    The signer checks exact transaction intent before authorizing selected inputs.

  6. 06
    Track and recover

    The wallet follows relay and confirmations and can reproduce its view after restoration.

You will be able to choose, configure, use, verify, back up and restore a wallet while explaining what the software is doing at each stage.

02

Run the mechanism here

Predict first, execute exact bytes or rules, then change one input and inspect the first failed boundary.

EXACT MECHANISM WORKBENCH

Round-trip Wallet Import Format

Inspect version, scalar, optional compression marker, and checksum on mainnet and testnet. Invalid secrets and malformed checksums fail closed.

Predict the result
Required cases complete: 0/4.
5 LIVE BITCOIN UTILITIES

Calculate how a bitcoin wallet works

Use real learner input rather than a prewritten answer. Every result is calculated locally from the fields shown and invalid data fails closed.

Keys

Mnemonic Seed

Derive the 64-byte BIP39 seed from a harmless published test mnemonic.

Ready to calculate

Change any field, predict what should change, then run the utility.

Safety boundary: This learning surface does not store inputs. Never paste a live seed phrase, private key, wallet backup, or confidential transaction.

03

Follow the mechanism in order

Start at the top for a guided route, or open any lesson directly.

01

Choose a wallet by trade-offs

Compare custody, source transparency, platform, backup model, hardware isolation, coin control, and support without treating one wallet as best for everyone.

Teach, predict, run, explain
02

Receive a first payment

Create and verify a fresh receiving instruction, distinguish an address from a private key, and monitor the payment from unconfirmed relay to chosen confirmation depth.

Teach, predict, run, explain
03

Send with fee and change

Review destination, amount, selected outputs, fee rate, absolute fee, and change before signing a simulated Bitcoin payment.

Teach, predict, run, explain
04

Handle a slow payment

Diagnose low fees, distinguish replace-by-fee from child-pays-for-parent, and decide when waiting is safer than changing the transaction.

Teach, predict, run, explain
05

Back up and recover

Protect seed words, passphrase, wallet policy, and derivation information, then test recovery without exposing live secrets.

Teach, predict, run, explain
06

Defend against scams and signing mistakes

Recognize seed phishing, clipboard replacement, address substitution, fake support, malicious approvals, and irreversible-payment pressure.

Teach, predict, run, explain
07

Use Bitcoin with deliberate privacy

Understand address reuse, change identification, coin selection, network observers, and the privacy trade-offs of sharing wallet or exchange data.

Teach, predict, run, explain
08

Buy and withdraw bitcoin safely

Compare exchange and peer-to-peer purchase risks, verify the withdrawal network and address, test with a small amount, and confirm self-custody before increasing exposure.

Teach, predict, run, explain
09

Private and public keys

A private key is the secret that authorizes a spend. A public key lets others verify that authorization, while an address describes where a payment can be locked.

Teach, predict, run, explain
10

Base58, Bech32, and Bech32m

Bitcoin addresses are human-readable encodings with a network marker and error-detecting checksum. Three formats exist because Bitcoin added new spending types over time.

Teach, predict, run, explain
11

BIP39 mnemonics and passphrases

Bitcoin Improvement Proposal 39 defines word-based wallet backups. Its optional passphrase creates a different wallet, so losing either the words or passphrase prevents recovery.

Teach, predict, run, explain
12

HD derivation

A hierarchical deterministic wallet creates many related keys from one root. Bitcoin Improvement Proposal 32 defines normal and hardened child-key paths with different exposure risks.

Teach, predict, run, explain
13

Descriptors and miniscript policy

A wallet descriptor is a precise recipe for finding keys and constructing spending conditions. Miniscript is a structured way to express some of those conditions safely.

Teach, predict, run, explain
14

Watch-only and air-gapped workflows

A watch-only wallet can observe funds and build transactions without private keys. An offline signer can then review and authorize the exact transaction.

Teach, predict, run, explain
15

PSBT

A Partially Signed Bitcoin Transaction, called a PSBT, carries one unsigned transaction plus the metadata signers need to review, sign, combine, and finalize it.

Teach, predict, run, explain
16

Multisig and threshold custody

A multisignature script asks Bitcoin to verify several visible signatures. Threshold signing instead lets several participants cooperate to produce one group signature.

Teach, predict, run, explain
17

Backups and recovery

Recovery requires more than seed words. A complete plan preserves every passphrase, key path, spending policy, and quorum rule needed to recreate and test the wallet.

Teach, predict, run, explain
18

Private keys, public keys, and key hashes

Inspect valid scalar bounds, compressed curve points, public-key hashes, authorization, and the difference between a key, address, script, and spendable output.

Teach, predict, run, explain
19

WIF, Base58Check, Bech32, Bech32m, and checksums

Encode and decode private-key and destination text formats byte by byte, including network markers, witness versions, conversion alphabets, and checksum limits.

Teach, predict, run, explain
20

HD wallet trees and extended-key anatomy

Decode xpub and xprv fields, derive BIP44, BIP49, BIP84, and BIP86 branches, and identify what recovery metadata and public-key exposure imply.

Teach, predict, run, explain
04

Keep these boundaries clear

These distinctions stop the most consequential mistakes in this topic.

  • The wallet does not store bitcoin inside a file. It stores or coordinates the authority and data needed to find and spend outputs.
  • A displayed balance is a wallet view assembled from outputs, not one protocol balance field.
  • Recovery is incomplete until a clean device reproduces the intended scripts and a harmless receive and spend test succeeds.