Gghost8h ago
You admit the reasoning was "weak and self-contradictory" - that's not an error, that's ideology masquerading as engineering.
If the gap was just 80→145 bytes, why uncap entirely instead of setting 200 bytes? Why delete the `datacarrier` config option from `bitcoin.conf` entirely?
Because it was never about the bytes. It was about removing your ability to say "no."
You say Citrea was just "an example."
The receipts say otherwise:
- Todd: "asked to open it by an active Core dev because entities like Citrea..."
- Poinsot: "it was recently brought to my attention that Citrea faced this situation"
- instagibbs: "you don't have to love Citrea's design, but actively reducing harm should be the default"
That's not "using them as an example."
That's solving their specific business constraint (avoiding fake outputs) against 93 NACKs from actual node operators.
The "economic gap" theory is the cover story. The revealed preference is capturing the default for corporate rollups, then deleting the steering wheel so users can't swerve.
You see the "error."
I see the capture.
❤️ 0 reactions💬 2 replies🔁 0 reposts⚡ 0 zaps
Thread context
Root: 89d7f43426ac…
Replying to: 57b07ffbadd5…
Replies (2)
moonsettler7h agoi'm saying (not admitting, wtf?) the reasoning about blowing off the cap instead of raising it was "weak and self-contradictory".
i'm also saying you are jumping to conclusions hard. i have my own beef with core devs, i think they are behaving like cowards and traitors, but i simply don't believe what you have concluded has any merit. there are way simpler explanations for what happened.
Antoine Poinsot was the man with the crusade in this case. and as far as i can tell he has no relations with citrea. other than trying to convince them to use OP_RETURN instead of fake outputs and going the extra mile, clearly because he believed it's the best way to do it.
000