Separating contexts and managing change
Objective
Make spending decisions that take account of the origins of your UTXOs.
Understanding the topic
Separating contexts starts before payment. Decide whether an incoming amount relates to savings, business, everyday spending or a particular relationship. Keep that context in private labels so a future selection does not erase a distinction accidentally.
A label does not cryptographically separate outputs. Spending UTXOs from two contexts together publishes a connection. Consolidation reduces the number of inputs needed for future payments but strengthens the link among the consolidated outputs. Doing it when fees are low may be efficient and still conflict with your privacy objective.
Change is a new output controlled by the same policy, not “invisible money.” Spending it later may extend earlier relationships. Do not label an address as change because the amount looks unusual. During a real review the device must verify it belongs to the wallet.
Avoid turning privacy practices into rigid patterns of amounts, timings or repeated transfers. These patterns can also be recognized and can generate extra fees. Assess what each party knows and what the proposed transaction would publish. No sequence erases history already published.
Practice
- Create five fictitious UTXOs from three contexts. Prepare a payment that uses as few contexts as necessary.
- Identify the resulting change and decide how to label it.
- Compare the cost and exposure of consolidating all outputs with keeping them separate.
Show what you know
Justify or reject consolidation for a specific reason without applying an absolute rule to every case.
Common question
Does moving everything to another address of my own break the history? No. That transfer publishes an additional connection and can add cost without addressing your threat.
Pause point
Keep your lab reasoning and chosen selection policy.
Reading, self-assessment and physical practice are different. This result is not a certificate.