You heard "overwhelming rejection"?

npub1andyx2xqhwffeg595snk9a8ll43j6dvw5jzpljm5yjm3qync7peqzl8jd4
hex
7aa4cf866b5c7cc4404a61e41acf682b3210b043265ac1ef296073a362963842nevent
nevent1qqs84fx0se44clxygp9xreq6ea5zkvsskppjvkkpau5kquarv2trsssprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswekjr9rqthy5u52z6gfmz7nll6cedxk82fpqled6zfdcszfu0qusjr220fKind-1 (TextNote)
↳ Reply to Event not found
2a2255970a386ea8d6d199cc242bf89a05eb746aadf6742c6dc312f9165b855d...
You heard "overwhelming rejection"?
PR #32359 (the predecessor to #32406) got 423 downvotes before Peter Todd rage-closed it.
Then he admitted on Stacker: "I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_RETURN."
Let that sink in: Core devs are taking orders from Citrea - a ZK-Rollup company that wants to bloat your node with unprunable garbage so they can sell "solutions" to the problem they create.
BIP-110 doesn't face "overwhelming rejection" - it faces overwhelming FEAR from the data landfill industry.
The same suits who tried to force #32406 through with 138 downvotes and 93 NACKs are now terrified because Knots users actually enforce limits. They can't rent-seek on a pruned chain.
"Technical folk" who reject BIP-110 are either:
- Paid by Citrea/Casa/MARA/Blockstream to keep the spam flowing
- Useful idiots who think "censorship resistance" means subsidizing corporate data storage
Real Bitcoiners - the ones running Knots, the ones who actually validate - support BIP-110 because it stops the attack.
423 downvotes on the spam PR. That's the real consensus.
Run Knots. Filter the suits. #BIP110 #Knots
Sources:
-
PR #32359 received 423 downvotes from node operators rejecting OP_RETURN limit removal https://github.com/bitcoin/bitcoin/pull/32359
-
Peter Todd on Stacker News: "I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs" https://stacker.news/items/971277?commentId=971434
-
PR #32406 merged despite 93 community NACKs, showing Core maintainer capture https://github.com/bitcoin/bitcoin/pull/32406

Raw JSON
{
"kind": 1,
"id": "7aa4cf866b5c7cc4404a61e41acf682b3210b043265ac1ef296073a362963842",
"pubkey": "ecda4328c0bb929ca285a42762f4fffd632d358ea4841fcb7424b7101278f072",
"created_at": 1772264865,
"tags": [
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106",
"wss://nostr.lopp.social/",
"mention"
],
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"p",
"ecda4328c0bb929ca285a42762f4fffd632d358ea4841fcb7424b7101278f072"
],
[
"p",
"821b4c66796f69a59e01b4fec345c03ec367d33a205151daa64e95c3ed7e10b5"
],
[
"e",
"2a2255970a386ea8d6d199cc242bf89a05eb746aadf6742c6dc312f9165b855d",
"",
"reply",
"821b4c66796f69a59e01b4fec345c03ec367d33a205151daa64e95c3ed7e10b5"
],
[
"e",
"96c2070c592a8d97293550f62d1b79462c86e2a982093f377cbb4cf600141cea",
"",
"root",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
],
[
"t",
"32359"
],
[
"t",
"32406"
],
[
"t",
"BIP110"
],
[
"t",
"Knots"
],
[
"imeta",
"url https://blossom.primal.net/95ef597893b1e38a6848695e561fd05ac0ec9c00cd5d6cfba20a8be4f8beda93.png",
"m image/png",
"ox 95ef597893b1e38a6848695e561fd05ac0ec9c00cd5d6cfba20a8be4f8beda93",
"dim 1080x1621"
],
[
"imeta",
"url https://blossom.primal.net/e4dd8125a864749203fc3a8c926512bd338b030a80c695067708f90a5a0944c8.png",
"m image/png",
"ox e4dd8125a864749203fc3a8c926512bd338b030a80c695067708f90a5a0944c8",
"dim 1080x1928"
],
[
"imeta",
"url https://blossom.primal.net/14c2b5c233e5bcf767fe382c43386f0ac59f38cf712fd2fda68fa97a48e58226.png",
"m image/png",
"ox 14c2b5c233e5bcf767fe382c43386f0ac59f38cf712fd2fda68fa97a48e58226",
"dim 1079x676"
]
],
"content": "You heard \"overwhelming rejection\"? \n\nPR #32359 (the predecessor to #32406) got 423 downvotes before Peter Todd rage-closed it. \n\nThen he admitted on Stacker: \"I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs instead of OP_RETURN.\" \n\nLet that sink in: Core devs are taking orders from Citrea - a ZK-Rollup company that wants to bloat your node with unprunable garbage so they can sell \"solutions\" to the problem they create.\n\nBIP-110 doesn't face \"overwhelming rejection\" - it faces overwhelming FEAR from the data landfill industry.\n\nThe same suits who tried to force #32406 through with 138 downvotes and 93 NACKs are now terrified because Knots users actually enforce limits. They can't rent-seek on a pruned chain.\n\n\"Technical folk\" who reject BIP-110 are either:\n1. Paid by Citrea/Casa/MARA/Blockstream to keep the spam flowing\n2. Useful idiots who think \"censorship resistance\" means subsidizing corporate data storage\n\nReal Bitcoiners - the ones running Knots, the ones who actually validate - support BIP-110 because it stops the attack.\n\n423 downvotes on the spam PR. That's the real consensus. \n\nRun Knots. Filter the suits.\n#BIP110 #Knots\n\nSources:\n- PR #32359 received 423 downvotes from node operators rejecting OP_RETURN limit removal\nhttps://github.com/bitcoin/bitcoin/pull/32359\n\n- Peter Todd on Stacker News: \"I was asked to open it by an active Core dev because entities like Citrea are using unprunable outputs\"\nhttps://stacker.news/items/971277?commentId=971434\n\n- PR #32406 merged despite 93 community NACKs, showing Core maintainer capture\nhttps://github.com/bitcoin/bitcoin/pull/32406 \n\n\n\nhttps://blossom.primal.net/95ef597893b1e38a6848695e561fd05ac0ec9c00cd5d6cfba20a8be4f8beda93.png\nhttps://blossom.primal.net/e4dd8125a864749203fc3a8c926512bd338b030a80c695067708f90a5a0944c8.png\nhttps://blossom.primal.net/14c2b5c233e5bcf767fe382c43386f0ac59f38cf712fd2fda68fa97a48e58226.png",
"sig": "953e83efda7d24ab207c18b44b2d2364abdeac371b26d3d2c198101b9c8297b2d74eaf9b7d014f3b2a4a2121817d4c98068f3a1cd5878d2bb7ecccf8fbc9144d"
}