

Albert Einstein
242 posts

@runbip110
MSc Info Systems | node runner | systems thinking | separating money from state | Run #BIP110. See who funds bitcoin spam: https://t.co/afHFFc8tVp




BIP110 taketh away OP_IF, but giveth OP_PLENTY. Introducing a novel way to encode arbitrary data in *contiguous* bytes. Up to 2MB fully BIP110 compliant. OP_PLENTY encodes each 4 bit nibble of the raw data into a tapscript opcode. Decoding is trivial: take the opcode mod 22.








Why I’m Running BIP 110.






Craig Wright joins the suits in their support of non-monetary use of Bitcoin and ridicule of BIP-110 🤷♂️


✅Bitcoin is Money 3.0 ❌ Bitcoin is not "Digital Property" ❌ Bitcoin is not "Digital Capital" ❌ Bitcoin is not "Digital Gold" ❌ Bitcoin is not just a "Store of Value" ❌ Bitcoin is not "JPEG storage" ❌ Bitcoin is not a "StableCoin settlement layer"




Appreciate you following the interviews. My position (and I guess also @Saylor) isn’t that we “need” bigger data limits or that lower ones don’t work. $BTC has always worked fine with whatever capacity the market and voluntary node policies allow, fees price out abuse, and node operators choose their own relay rules. What we don’t need is moving those decisions into new consensus rules that invalidate previously valid, fee paying transactions and force every node to enforce someone else’s definition of acceptable use. Right now I run my nodes as I wish, BIP-110 will change that. I am focused on the censorship & sovereignty problem as much as the technical implications. Furthermore, BIP-110 doesn’t solve spam better than the existing system. IMO this just creates a precedent that’s riskier than the data itself, posted about this at length as well. The network will sort itself through consensus & with economic incentives, not attempts to force “soft forks”. As I have been saying, “Bitcoin is a technology, not an ideology”.
