pull down to refresh

246 sats \ 5 replies \ @gregtonoski 28 Aug \ on: Luke is wrong: datacarriersize was about OP_Return, since Bitcoin Core v0.10.0 bitcoin
Cry harder scammer, @petertodd. We resist your psyop. More information at https://wtfhappenedinfeb2023.com/
TL;DR datacarriersize has always been about any non-Bitcoin data as the name suggest. OP_RETURN is the security hole introduced (and exploited) by spamming attackers long after Bitcoin inception and CIA "invited" the maintainer Gavin Andersen. TapRoot is the much younger change than OP_RETURN and Bitcoin Core maintainers failed/refused to extend datacarriersize limit to TapRoot. Fortunately, the patch (bugfix) has been implemented in Bitcoin Knots.
write
preview
71 sats \ 4 replies \ @ZezzebbulTheMysterious 28 Aug
But why the fuck would you run knots?
reply
21 sats \ 3 replies \ @gregtonoski 28 Aug
I run Bitcoin Knots: "https://bitcoinknots.org/".
reply
101 sats \ 2 replies \ @ZezzebbulTheMysterious 28 Aug
Of course you are free to run it, Infact any software you like.
But knots is not Bitcoin. It’s a Bitcoin LARP client developed by a fool.
reply
0 sats \ 0 replies \ @Bell_curve 1 Sep
This whole ordinals/filters/core thing has really brought out the egos in the space. At least with the blocksize wars we knew who the enemy was...big businesses (Coinbase, etc.) and crooks (Craig Wright etc.). Now with filters, etc. there's a whole new split.
reply
21 sats \ 0 replies \ @gregtonoski 29 Aug outlawed
stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.