DUCAT’SBitcoin Guild
All curriculum
COMPLETE KEYS GUIDE

Keys, addresses, and wallet control

Start with one valid private scalar, derive its public point, turn a spending condition into a destination, and then follow how a wallet discovers, authorizes, backs up, and restores many outputs without confusing any of those layers.

12 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
    Secret scalar

    A valid number from one through the secp256k1 order minus one.

  2. 02
    Public key

    Curve multiplication creates a point that can verify signatures.

  3. 03
    Locking script

    The output states the exact condition a future input must satisfy.

  4. 04
    Address

    A checksummed instruction helps a wallet construct that locking script.

  5. 05
    Wallet

    Descriptors, keys and chain scanning discover outputs and construct spends.

  6. 06
    Backup

    Seed, passphrase, path and policy recreate the same wallet state.

You will be able to trace a payment destination from key material to Script, encode and decode WIF and addresses, explain wallet discovery, and design a complete recovery test.

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.
BYTE-EXACT ADDRESS LAB

Build the destination, not just the string

Addresses are checksummed instructions a wallet converts into a locking script. Change each layer and inspect the exact bytes that change.

Convert arbitrary bytes to and from Base58 while preserving every leading zero.

Ready

Predict which bytes or characters will change, then calculate.

9 LIVE BITCOIN UTILITIES

Calculate keys, addresses, and wallet control

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

Keys

Private Key

Validate a 32-byte secp256k1 scalar and inspect its exact integer range without deriving or storing wallet data.

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

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
02

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
03

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
04

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
05

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
06

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
07

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
08

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
09

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
10

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
11

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
12

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.

  • An address is not a protocol account.
  • A signature proves authorization under a spending rule, not economic ownership.
  • Seed words alone may not restore a passphrase, derivation path, descriptor or multisignature policy.