SATOSHI ° NOSTR ° AI LLM ML ° LINUX ° MESH ° BUSINESS ° OFFGRID

Open letter to Bitcoin Core: ‘Bitcoin is and must remain censorship resistant’
#Culture #bitcoin #bitcoin_core #Core_vs_Knots #Peter_Todd #Shinobi

Lema Máxima:

My Node. My Rules.

Meu Node. Minhas Regras.

Quer protestar?
Rode o #node que Você defende.

PS.
- Esse artigo está com viés para #BitcoinCore.
- Não apresenta os argumentos do #Knots.
- #DYOR Faça sua própria pesquisa.
- #DTV Não Confie. Verifique.

via Bitcoin (BTC) News | CryptoSlate

25 viewsedited 00:06

SATOSHI ° NOSTR ° AI LLM ML ° LINUX ° MESH ° BUSINESS ° OFFGRID | HODLER TUTORIAL

The Bitcoin And . . . Podcast:
Knaughty Core #Newsletter

#BitcoinCore #Knots
#Saylor #SP500

11 viewsedited 19:06

SATOSHI ° NOSTR ° AI LLM ML ° LINUX ° MESH ° BUSINESS ° OFFGRID | HODLER TUTORIAL

I see way too many people on Nostr that are still confused about the #BitcoinCore vs #Knots debate. This is a tl;dr for them. If a longer explanation is needed, they should go over the website below.

tl;dr:
SegWit introduced the witness discount, that ended up making junk data up to 75% cheaper, which opened the door for arbitrary data-carrying transactions to directly compete with monetary transactions for blockspace. In practice, that ended up being an unintended de facto subsidy for spam.

Taproot then provided a way for inscriptions to sidestep the old datacarriersize filter, which is why the UTXO set exploded from around 4 GB in 2023 to nearly 12 GB by 2025, putting real strain on low-end node hardware.

Meanwhile, the Core devs’ reaction has been pathetic — hand-waving it away for two whole years as “free market dynamics” or saying that fixing the exploit is considered “controversial”. At the same time they did a stealth documentation change to pretend the broken filter is “working as intended”. Unhosted Marcellus caught them red handed, but instead of apologising for hiding it, they claimed that changing the documentation is a valid way for fixing bugs.

Now they’re doubling down their efforts “to fight spam” they willingly allowed by gutting another spam filter (OP_RETURN) that has worked for 11 years, and helped keep 99.9% of all OP_RETURNs at or under 80 bytes. Larger payloads were possible, but never at the absurd size of 100 KB in a single output.

Core v30, due in early October, will raise the default limit to 100 KB (an 1200x increase), which makes it trivial to upload entire malware files or worse straight into the chain. This isn’t hypothetical — when BSV made the same change in 2019, it was immediately hit with child p[]rn.

The legal and practical fallout for Bitcoin node operators, especially those on cloud infrastructure, hasn’t even begun to be fully grasped.

All these absurd and rushed decisions raise the obvious questions: why push this change through despite massive pushback; who stands to profit from it; and why are the real risks of this happening being ignored or swept under the rug?

https://wtfhappenedinfeb2023.com

https://primal.net/e/nevent1qqszgqshk9nqjfc3vxpg32m92pnyykt00smlh3a02kyqfnu5qygxmlg3cdhmx

Wtfhappenedinfeb2023

WTF Happened in Feb 2023?

A website dedicated to mitigating spam on Bitcoin.

9 viewsedited 04:13

About

Blog

Apps

Platform