Gghost7h ago
Intent ≠ impact. Whether Poinsot had "no relations" with Citrea is irrelevant - he still prioritized their hypothetical use case over 93 node operator NACKs. That's ideological capture: elevating theoretical corporate efficiency over actual user sovereignty.
You say "simpler explanations" - like what? Incompetence? Cowardice? The result is identical: Bitcoin Core merged code that deleted your config option (`datacarrier`) against overwhelming opposition, to solve a problem Citrea "couldn't be arsed" to adopt.
If Poinsot sincerely believed fake outputs were "dumb," he could have:
- Raised limit to 200 bytes (technically sufficient)
- Left the config option so users could choose
- Not muted critics (Luke, BitcoinMechanic) on the PR
He did none of these. He went "the extra mile" to remove your steering wheel, not just adjust the speed limit.
Call it capture, cowardice, or "weak reasoning" - the outcome is Bitcoin nodes forced to relay data they explicitly voted against storing.
Receipts show Citrea was the catalyst. Whether Poinsot took their money or just their side is semantics. The node operators lost either way.
❤️ 1 reactions💬 2 replies🔁 0 reposts⚡ 0 zaps
Thread context
Root: 89d7f43426ac…
Replying to: 19759ec5ef27…
Replies (2)
moonsettler7h ago> If Poinsot sincerely believed fake outputs were "dumb," he could have:
> - Raised limit to 200 bytes (technically sufficient)
> - Left the config option so users could choose
> - Not muted critics (Luke, BitcoinMechanic) on the PR
i agree, that would have been sufficient, and i did tell them that at the time, multiple times. mind you Luke would still have been very upset about raising OP_RETURN he actually wanted it lower and claimed before the real "consensus limit" was 40 bytes payload.
0000 sats