A feck! I made another meme after I said I was moving on for today... oh well.

Btw, mastering coin control doesn't just help with keeping tx fees low, it also allows you remove individual UTXOs from a specific address. For example, if that specific UTXO contains unwanted metadata.

Alright, last one before I move on to other things. 😉 #meme #nostrmemes

Out of interest. Do you know what coin control is and how to use it when you create Bitcoin transactions on the main-net? Do you know how to exclude several inputs from being included in your output before broadcasting a transaction hence reducing the transaction fee by not sending the entire balance to the network only to receive most of it back in change while paying more tx fee? You need to know this shit.

Just for fun... on-chain zaps Setup: You've recived 200 zaps generating 200 inputs to your wallet. 200 × 350 sats (random amount because of dust limits) = 70,000 sats total balance Each zap creates 1 UTXO → 200 UTXOs We assume: Native SegWit / Taproot-like efficiency Standard P2WPKH/P2TR inputs ≈ ~68–69 vbytes per input 1 output when consolidating Consolidation transaction: Inputs: 200 × 68 ≈ 13,600 vbytes Output: ~31 vbytes Overhead: ~20 vbytes Total ≈ 13,650 vbytes Next we calculate the consolidation cost Fee = size × fee rate We use realistic fee bands: Scenario A — very low fee market (1 sat/vB) 13,650 × 1 = 13,650 sats Scenario B — normal (5 sat/vB) 13,650 × 5 = 68,250 sats Scenario C — moderate congestion (10 sat/vB) 13,650 × 10 = 136,500 sats At 1 sat/vb the consolidation will cost almost 20% of the received funds. At 5 sat/vb the whole thing becomes unrealistic.

if you send me an on-chain zap you're burning your money. Send it to charity or Saylor instead. Thank you for your attention.

Nothing is more permanent than a temporary tax. View quoted note →