Damus
Luke Dashjr · 1w
No, because a counter-fork to reject RDTS would be explicitly protecting the ability to force others to distribute child porn.
Luke Dashjr profile picture
Core30 intentionally enabled attackers to force every Bitcoin user to distribute CSAM.
This is a fatal wound because nobody is going to be willing to use Bitcoin if it requires them to do that.
(Remember, Bitcoin only works if _most people_ are using full nodes.)

RDTS rejects/undos the changes Core30 made. It prevents the CSAM attack.

Rejecting RDTS requires creating a counter-fork like Bcash.
To oppose or reject RDTS is therefore an explicit action to enable people to force CSAM on Bitcoin.
Therefore, if someone actually tries to reject RDTS, the name of their fork is Bpedo.
610โค๏ธ33โค๏ธ3๐Ÿค™3๐Ÿš€2๐Ÿ‘€1๐Ÿ’œ1
AU9913 · 1w
The more you talk about CSAM the more I think you're going to be the one who actually puts it on the blockchain after your fork.
Marcus Satbard · 1w
shitfork liar nostr:nevent1qqsvwxur99dpn7euhuq0vrspkr3j7q3fpanlmemcfr7eguzavrs64qqpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygxwm2uphepw737mmejn7ja84vj6cw4r9n7zkeewurufcra03qh38cpsgqqqqqqsjctmpw
Tony Acid · 1w
CSAM is already on Bitcoin. Is the fork going to remove it?
Gregor · 1w
How will RDTS deploy, by UASF?
kubernetes · 1w
Rejecting RDTS can be accomplished very simply by ignoring it. There's no chance that it gets adopted beyond fringe Knots fan communities.
sister_sam · 1w
How is not equivalent to saying anything that supports arbitrary data "forces CSAM" including any data or miscellaneous data field of any kind? Clearly massively overblown claim.