pull down to refresh
21 sats \ 0 replies \ @031ca302ff 31 Jan \ on: Dust consolidation bitcoin
No. Dust is not a function of tx fees. It’s a relay policy
What? No UTXO can increase circulation
So miners are not incentivized to act against their own interest, but maybe they will?
Even with empty blocks, no one was consolidating dust. And how do you expect miner to include txs they don’t have the keys/scripts to spend. If you want to get rid of dust in your wallet, you’re better off donating it to the miners as a OP_RETURN.
HTLC did not resolve in time, must go on chain via Force Close
Force Close outputs are time locked. Non initiator of the close has a time lock of 1 block. Since there's only one htlc in the close, it's probably not yours. The P2TR output is to your wallet.
0 sats \ 1 reply \ @031ca302ff 4 Jan \ parent \ on: Favorite Non-Default lnd.conf Settings lightning
Here’s 2 examples from FCs from a few hours ago.
This CPFP needed 2 utxo, where the 2nd was big enough to go solo had it used largest selection - https://mempool.space/tx/d46cedf4e5b85dfde09b4ee4cfb713214e0956a6d6c932caf39195f0faa9bb65
Here is a 6 utxo CPFP (maybe they didn’t have a utxo large enough) - https://mempool.space/tx/039ae9e76659454b59412fb6cc63e22dfe621f967d22e424a953d8984430f1da
10 sats \ 3 replies \ @031ca302ff 3 Jan \ parent \ on: Favorite Non-Default lnd.conf Settings lightning
Except when your node has to CPFP anchors or stage 1 sweep htlcs. Carrying an extra input utxo (or 5) at 200 s/vB because it didn’t select a utxo big enough is pretty painful.
IMO, if privacy is the goal, avoid using the hot wallet altogether.
GENESIS