Switch to Knots 🤙

nostr:nevent1qqsyl0am9ejeje6rcauggmyhkms503lart8z96g888v8axdu9phc9usppamhxue69uhkummnw3ezumt0d58cvxws

Nope.

Wonderful!

Bitcoin is THE Global Most Secure Decentralized Unconfiscatable Peer-to-Peer Scarce Hard Sovereign Freedom Money and Greatest Store of Value 💪

and

The Strongest Hope for Humanity 💜

GM… Happy SAT-urday!! 🙌👏🍂🍁

Thanks team!

Aguante Bitcoin Core!!!

😂😂🤣🤣

Se acuerdan de la época de las #flamewar?

Nos peleamos por cualquier cosa!! 😄

No hurries to upgrade

Just updated 💪🏾

Waiting for core to destroy bitcoin 💀

Hey there Luke, what do you think the likelihood is of successfully forking BTC to hardcode the op_return filter, and eliminating the inscription exploit?

I just manually 1-year banned a Core v30 node that I happened to notice was connected to my nostr:npub13rhywhcdwvcfgu7qktm7kz3sxqkk6jvs237eq6n0vrmzrlsvnc6s6jcgea node (just to test the feature out on a node that I didn't particularly care for trading data with) & it got me thinking... 🤔

...What is stopping nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk, nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr & other Knots devs from implementing a feature for Knots to auto-disconnect & auto-ban any discovered nodes that broadcast a version that the node runner doesn't approve of? 🤷‍♂️

If it was off by default & you allowed node runners to select which node versions they approved/disapproved of & the duration of ban desired, wouldn't that be the ultimate freedom for node runners to exercise their agency? It would also be a natural mechanism for consensus & broadcast depth. 💁‍♂️

Just a thought. 🤙

sure

and I'll try to compile too