tldr; Luke Dashjr, maintainer of Bitcoin Knots, is reportedly considering a hardfork to introduce a trusted multisig committee capable of retroactively altering the Bitcoin blockchain to remove illicit content, such as CSAM. This proposal has sparked controversy as it challenges Bitcoin’s censorship resistance and permissionless nature. Critics argue it could lead to broader data censorship and legal risks for node operators. Dashjr has denied the claims, calling them unfounded, but the debate highlights ongoing tensions within the Bitcoin community over content moderation and blockchain integrity.
*This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.
Appropriate-Talk-735 on
This has been debunked but the spam war is alive and well.
East-Cricket6421 on
As someone who hasn’t been tracking BTC development closely, this sounds like a big fucking mess. Kind of funny to see the Bitcoin Core team on the side of increasing space this time around but not entirely surprising that there’s a more fundamentalist sounding group like Knots fighting against any changes.
The CSAM attack vector seems an annoying one, as it doesn’t really have anything to do with the networks utility and design but more so to do with people being pieces of shit (which you have to account for unfortunately).
Is the attack vector „someone loads CSAM onto the network and now anyone hosting an node can be liable for spreading CSAM around“?
Leave A Reply
Du musst angemeldet sein, um einen Kommentar abzugeben.
3 Kommentare
tldr; Luke Dashjr, maintainer of Bitcoin Knots, is reportedly considering a hardfork to introduce a trusted multisig committee capable of retroactively altering the Bitcoin blockchain to remove illicit content, such as CSAM. This proposal has sparked controversy as it challenges Bitcoin’s censorship resistance and permissionless nature. Critics argue it could lead to broader data censorship and legal risks for node operators. Dashjr has denied the claims, calling them unfounded, but the debate highlights ongoing tensions within the Bitcoin community over content moderation and blockchain integrity.
*This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.
This has been debunked but the spam war is alive and well.
As someone who hasn’t been tracking BTC development closely, this sounds like a big fucking mess. Kind of funny to see the Bitcoin Core team on the side of increasing space this time around but not entirely surprising that there’s a more fundamentalist sounding group like Knots fighting against any changes.
The CSAM attack vector seems an annoying one, as it doesn’t really have anything to do with the networks utility and design but more so to do with people being pieces of shit (which you have to account for unfortunately).
Is the attack vector „someone loads CSAM onto the network and now anyone hosting an node can be liable for spreading CSAM around“?