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

Sikh Bitcoin · Advanced · Lesson 16 of 21

Full nodes, pruning and verification

Understand the difference between validating history and retaining every byte.

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 16 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 full validation and pruned storage.
  • Recognize operational limits of a node.

Validation is the core responsibility

A full node independently checks blocks and transactions against its rules. Running one can reduce dependence on a third-party service for payment verification. It does not automatically make every connected wallet use that node; the wallet’s actual connection and configuration still matter. A node also does not create ownership of funds merely by observing them.

Storage choices affect capabilities

Pruning removes older block data after validation to reduce retained storage. It is different from skipping validation. However, historical rescans and serving old blocks can be constrained by what remains available locally. A recovery plan must account for those operational limits rather than assuming that a small disk footprint comes without consequences.

Independence still needs maintenance

A node depends on hardware, storage integrity, power, network access and software maintenance. Protect administrative interfaces and understand synchronization status before treating its view as current. Do not publish a node’s management credentials to make remote help convenient. For this course, plan the architecture on paper: data source, wallet connection, backup, update process and who responds when the machine is offline. No software installation or ports need to be opened.

Practice on paper

A wallet uses a public server while a full node runs unused on the same home network. Has the wallet automatically gained independent validation?

Reveal the worked answer

No. The wallet must actually use an appropriate connection to the validating node. Proximity is not configuration, and a node that is out of sync may also provide an incomplete current view.

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 pruning necessarily mean skipping historical validation?

  • Yes
  • No
Reveal answer 1

No. Pruning concerns retained data after validation.

2. Does operating a node remove hardware and maintenance responsibilities?

  • Yes
  • No
Reveal answer 2

No. It changes dependencies rather than eliminating operations.

Take this with you

Verify the connection and operational state, not just the presence of a node.

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.