Luke Dashjr's avatar
Luke Dashjr
luke_nostr@dashjr.org
npub1lh27...a9nk
Roman #Catholic, husband, father of 11 children, #Bitcoin Core developer, and CTO @npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze ; INTP; I condemn fake "Catholics", cryptobros & pedos; see full bio
Luke Dashjr's avatar
Luke Dashjr 0 years ago
Long-time Bitcoin Core developer (not one of the bad ones) and US citizen Jon Atack has been detained in El Salvador. His phone and passport have been taken from him.
Luke Dashjr's avatar
Luke Dashjr 1 year ago
image The sooner proposals like CTV are implemented, the sooner blocks can get smaller. Assuming of course we deal with spam too (so it doesn't just fill up the gained space) CTV/CSFS and spam filters go together
Luke Dashjr's avatar
Luke Dashjr 1 year ago
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's avatar
Luke Dashjr 1 year ago
Spam apologists trying to reintroduce the Bitcoin censorship FUD painted with jargon to confuse people. Sigh Spam filters cannot be abused for censorship. It only takes 1 block to bypass attempts to censor. But it takes 1 block to make spam filters effective. Opposites.
โ†‘