Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:
1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.
2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently, since "it's already deprecated").
3) Core never fixed the Inscription exploits (CVE-2023-50428 and CVE-2024-34149) which allow spammers to bypass the datacarriersize limit.
The only way forward now is a mass migration to Knots. Not the way I wanted things to go, but Core has given us no other choice. Once this is resolved, we should avoid putting all our eggs in one basket, and encourage the creation and use of multiple clients.
Luke Dashjr
npub1lh…aa9nk
2025-06-10 18:44:29
Author Public Key
npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nkPublished at
2025-06-10 18:44:29Event JSON
{
"id": "9d885d10697bad57996144fb8af753c604163074200e561cea3181a64e0a56c4",
"pubkey": "fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7",
"created_at": 1749581069,
"kind": 1,
"tags": [],
"content": "Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:\n\n1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.\n\n2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently, since \"it's already deprecated\").\n\n3) Core never fixed the Inscription exploits (CVE-2023-50428 and CVE-2024-34149) which allow spammers to bypass the datacarriersize limit.\n\nThe only way forward now is a mass migration to Knots. Not the way I wanted things to go, but Core has given us no other choice. Once this is resolved, we should avoid putting all our eggs in one basket, and encourage the creation and use of multiple clients.",
"sig": "394fd57a2f802b7a48c8a2485ccd23b089d5e4eae3585da4cc62eca5512d8963626b25ba212db396ed31cd2ece123b17f419ade8b57df5829f51aeab4ed91021"
}