Oooops, my contiguous image file got misinterpreted as a transaction WITHOUT OP_RETURN by the Bitcoin network and now it's forever contiguously stored in the chain! https://t.co/R2QOUqxABo (BTW, I only logged in to post this don't expect me to use X again anytime soon.)

@hodlonaut You are a clown, a hack, and a deceptive person. A Grok summary (that I fully read and verified) on why this whole thread is misleading bullshit distorting context: In summary, by fixating on Citrea as the linchpin and portraying the change as arbitrary or corrupt, hodlonaut

@kwsantiago You are conflating relay policy changes with criminal possession. The datacarrier size increase does not make the images viewable to the node operator. The CSAM statutes require knowing possession of a visual depiction of a minor engaged in sexually explicit conduct, with actual

@sashahodler @kixunil

Illative made a cool Bitcoin map in VR Chat called "Live Bitcoin Blockchain"

I guess it's time to get off twitter again.

Crap, this needs to be reposted more, how come it has only 6 retweets? Come on guys, we need to expose the Knots bullshit!

Here it is, a new demo! The BIP-110 supporters haven't provided the numbers on how the BIP affects spam yet, so I made a calculator that does: https://t.co/eLojPDpFyB The numbers don't look good for BIP-110.

Questions for BIP-110 supporters: Did you read the BIP? Did you realize it rugs large multisigs such as Liquid? Did you agree to rug them? If not why didn't you complain? Did you know the reference implementation fails to enforce it? Is it possible you are not technical enough?

So turns out the code doesn't enforce it and the hypocrites are now changing the BIP.

Holy shit, I just realized BIP-110 effectively limits the size of multisig in P2WSH and P2TR scripts to 7 keys. That's even more insane than I previously considered.

Mechanic is now crying that "permissionless" is just a bad word used by scammers. 😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂

The state of the BIP110 debate, March 1, 2026

LOL, @CaminaDrummer4 blocked me and talks shit about me behind my back. So much for honest discussion about BIP-110. To the honest BIP-110 supporters: such people are damaging your reputation, you need to kick them out.

There's a bunch of misinformation about this floating around, especially from LLMs. I'm thinking of putting more information about the technique into the document but that will also help any spammers to replicate it. Thoughts?

Some people were wondering why I didn't do it from the beginning. To be completely honest part of it was that I wanted to be done with it already and the other part was that verifying that proof is not nearly as easy and cool as the mainnet one.

It's live now!

Update that you've been all waiting for: I made a contiguous image file that can be misinterpreted by the BIP-110 Bitcoin fork as an entire transaction and contiguously stored in the BIP-110-compliant chain! Read the details and verify at: https://t.co/MhgWucTohS

Important update: I just fixed the bug in my code that made it crash when trying to make the BIP-110-compliant version. It just produced a BIP-110-compliant regtest transaction. I will test it against the reference BIP-110 implementation today and post instructions to verify.

I think it's worth adding something: The way I wrote the code it should be possible to produce BIP-110-compliant transaction already and I tried but got weird crashes which I didn't care to fix. I have since improved some parts which may have resolved them. Maybe I'll try later.