pull down to refresh

225 sats \ 4 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
0 sats \ 3 replies \ @ZezzebbulTheMysterious 28 Aug
But why the fuck would you run knots?
reply
0 sats \ 2 replies \ @gregtonoski 20h
I run Bitcoin Knots: "https://bitcoinknots.org/".
reply
90 sats \ 1 reply \ @ZezzebbulTheMysterious 18h
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 \ @gregtonoski 5h
I recommend running Bitcoin Knots instead of Core. I have upgraded with the single line: sudo rsync --ignore-times rsync://peer.dedyn.io:1873/knots/* /usr/local/bin Bitcoin Knots uses the same files format so blockchain re-download is not needed. Bitcoin Knots is more powerful and higher quality node implementation. There are more instances of the Bitcoin Knots v. 20250305 than any Core version older than 28.0 (according to clarkmoody.com).
reply