Thanks for the correction. I've seen both sides misrepresent this now in arguing over what does/doesn't get stored. Think this gives me an idea to hit AI with.

It definitely seems like it was an overreaction to the announcement of the out-of-band offerings like Mara's SlipStream. Was it really encouraging it though? Or was it hoping that those misusing other, non-pruneable fields like witness data would take the olive branch and move their data use there so at least it could be pruned by those not running full archival nodes? Again, probably another overreaction that came out of the temporary Ordinal craze.

This is something we both can agree on. I do wish we would see more Bitcoin node implementations and I've held that belief for quite awhile.

Some disgusting tweets by Luke Dash were unearthed that I had never seen before last night. While there is very little probability this BIP-110 effort is going to be successful, if he ever gets in control of Bitcoin like Knots/110 supporters want, I think I may have to move on. I also never want to hear the CSAM talking point again.

You are correct. I blew away my old install, slapped 0.4b9 on it and now v31 is synching.

Thanks to the knowledge from @BTCMcBoatface on X — new 4TB SSD in, 0.4 installed, and sync has started on v31. Still think showing something never installed on the Updates tab is dirty work but they claim it was a bug.

Start9 is saying it should work fine and my OS isn’t current. I checked that first and it said current so I may have bigger issues with my node. May need to completely blow it away and reinstall from scratch.

https://primal.net/e/

I assume all of the miner support is just hiding until the last minute, right? https://wickedsmartbitcoin.com/bip110_signaling

https://primal.net/e/

I haven't seen this mentioned on any Space or tweets, but if you generated your seed on an impacted ColdCard but later moved to a different vendor and imported that seed vs generating new, you're still at risk and should act accordingly.