FxTwitter / FixupX
jamesob (@jamesob)
BITCOIN CORE'S LOSS OF FOCUS
The legacy technical leadership in bitcoin is becoming increasingly less effective.
--
Almost universally, Core and "graybeard" devs are not focusing on _the_ fundamental problem in bitcoin: preserving trustless UTXO ownership.…
The legacy technical leadership in bitcoin is becoming increasingly less effective.
--
Almost universally, Core and "graybeard" devs are not focusing on _the_ fundamental problem in bitcoin: preserving trustless UTXO ownership.…
https://fixupx.com/jamesob/status/1860340932706730261
Lightning has not solved our problems, and given the on-chain footprint that existing channel constructions require, it categorically cannot. Lightning certainly helps reduce on-chain payment volume once someone has opened a channel - but to do that for most people will require a layer 1 innovation.
Forwarded from Down Fall
I have this annoying issue in my node: it does not forget some channels due to: "ONCHAIN:1 outputs unresolved: waiting confirmation that we spent DELAYED_OUTPUT_TO_US (cbxx....cf1:0) using OUR_DELAYED_RETURN_TO_WALLET". ( this one is like a year old , and it's still there ). I have like 20 of them
However, cbxx....cf1:0 has already returned to my wallet . The tx shows up in mempool.space . Does it mean cln couldn't find it on my btc node (it's a full node, not pruned) ? Should I try to use the dev rescan wallet to resolve the issue ? How did it happen in the first place. I think it's been like this since a few release ago. (I'm still on 24.05, not sure if it's fixed on 24.08 and nobody seems to complain about it, maybe it only happens on my node)
However, cbxx....cf1:0 has already returned to my wallet . The tx shows up in mempool.space . Does it mean cln couldn't find it on my btc node (it's a full node, not pruned) ? Should I try to use the dev rescan wallet to resolve the issue ? How did it happen in the first place. I think it's been like this since a few release ago. (I'm still on 24.05, not sure if it's fixed on 24.08 and nobody seems to complain about it, maybe it only happens on my node)