BIP110NACKER

Public Key

npub1tfgk4cud5lj8aad397g66uhtknv6e02c90yyr8azydsk327dpxmqytlgxz

Profile Code

nprofile1qqs955t2uwx60er77kcjlyddwt4mfkdvh4vzhjzpn73zxctg40xsndspp4mhxue69uhkummn9ekx7mqpz4mhxue69uhhyetvv9ujumn0wd68ytnwv46qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcww62kp

Publishing to

nos.lol

relay.nostr.net

relay.damus.io

Author Public Key

npub1tfgk4cud5lj8aad397g66uhtknv6e02c90yyr8azydsk327dpxmqytlgxz

Show more details

Last Notes

2026-07-27 00:18:44 UTC

- reply

If you don't accept blocks that old clients do accept ? how is that a small cautious step? Am I at risk of losing lightning channels if my peers are 110ers ?

2026-07-25 18:14:30 UTC

I am going to continue to run Core 31 although the ethos of 110 is good, the real risk of a fork is not worth it. Bitcoin as Money is the reason it matters, but Bitcoin as living system is an immutability machine. There will always be demand to put data into this immutability machine and increasingly as the block reward diminishes and layer 2 is adopted **that demand will be the primary revenue for the miners**. It will occur regardless of the protocol hoops that must be jumped through. OP RETURN is the **best possible way** for data to be included in a block because it doesn't clog the memory pool and can be safely ignored. Adjusting the protocol rules will just make the data that inevitably will be demanded and stored in the immutability machine **more costly to the network**. It achieves **exactly NOTHING**.