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

Sikh Bitcoin · Expert · Lesson 7 of 21

Coin control and privacy tradeoffs

Understand how transaction construction can connect histories.

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 7 of 21
  1. Threat model before tools
  2. Design a custody architecture
  3. Entropy, mnemonics and passphrase tradeoffs
  4. Hardware signing and trusted displays
  5. Multisig and independent control
  6. Recovery and continuity across people
  7. Coin control and privacy tradeoffs
  8. Lightning operations and recovery
  9. Payment operations and reconciliation
  10. Native bitcoin and wrapped claims
  11. USDC, reserves and redemption
  12. Identify a Morpho market precisely
  13. Oracles, prices and measurement risk
  14. LTV, liquidation and nonlinear losses
  15. Variable rates and growing debt
  16. Vaults, allocation and exit liquidity
  17. Arc, Base and cross-chain dependencies
  18. Allowances, signing and simulation
  19. Treasury accounting and restricted funds
  20. Incident response with clear human authority
  21. Capstone: a defensible treasury design

What you will learn

  • Explain a privacy cost of combining inputs.
  • Compare fee efficiency with data minimization.

Inputs tell a story

When a wallet combines outputs from different sources in one transaction, observers may infer relationships among them. Such heuristics are not perfect, but they can reveal more than a user intended. Address reuse, published receipts and third-party balance queries can add further links. Privacy is a system property involving both chain data and surrounding information.

Coin control exposes a choice

Some wallets let an operator choose which outputs to spend. That can support accounting separation or privacy goals, but introduces decisions about fees, change and operational complexity. Avoid universal rules such as always consolidate or never combine. The right analysis begins with the purpose, threat model and constraints of a specific situation.

Keep accounting separate from unnecessary publication

A community can preserve internal source-of-funds records without publishing every donor-to-expense relationship. A researcher should receive the minimum data needed for reconciliation. Exporting an xpub to a convenient service can expose a much wider history than one address lookup. This lesson does not provide a privacy guarantee or ask you to reorganize real funds; use labeled fictional outputs to reason about what a transaction reveals.

Practice on paper

A mock wallet has one output publicly tied to a fundraiser and one from a private artist sale. What new inference might arise if they are spent together?

Reveal the worked answer

An observer may associate the sources with a common spending controller. The inference is not absolute proof of identity, but the transaction can reduce separation between previously distinct contexts.

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 new receiving address alone guarantee privacy?

  • Yes
  • No
Reveal answer 1

No. Later transactions and external disclosures can connect activity.

2. Can a watch-only export expose broad history?

  • Yes
  • No
Reveal answer 2

Yes. Its scope may include many derived addresses.

Take this with you

Evaluate what construction and disclosure reveal together.

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.