if this is the best drama we have u know we are struggling this cycle

NOTE OF THE YEAR🫡

There is no technical basis to oppose lifting the OP_RETURN limit in mempool policy. The amount of emotional thinking in this space is wild.

Bitcoin is just another victim of the old EMBRACE, EXTEND, EXTINGUISH corporate playbook, a documented strategy used by tech giants. "Maxis" were maybe the first (unwillingly?) actors of this playbook

Good luck. I'll be upgrading to v30.

Door number three is the status quo.

Best...🌐🌐🌐🌐🌐🫶

Libbitcoin enters the chat

3rd option would be cool roll back Taproot and fix OP_RETURN at 21 bytes.

https://blossom.primal.net/09dc8da924642aaf68e88a29a328e4169f498d16a64049c58dd8d5d75e63382c.gif

fence straddling? 😂

Get Eric Voskuil on citadel or listen to his Bitcoin takeover interviews. The project is solid but, from his words, hasn't taken any third-party funding. As a dev, libbitcoin is ok to get running and hack on, but it's missing the type of project management that core has. It's not really possible t...

Libbitcoin is the way.

Why? Core solution is just accepting that Ordinals are inevitable in the chain and minimize damage, allowing people to use OP_RETURN as preferred option to upload this data. Instead of storing in Witness or another solutions that increase UTXO set, that will be an increase in RAM requirement for n...

Satoshi was not the best coder, but he was an amazing "Bitcoin architect," applying knowledge from other disciplines. I think in the future, Bitcoin development needs a formal process to get input from non-coders who understand economics, law, etc. nostr:nevent1qqs8nzhyc388qgnv6mqrdr28e3sd5knqyqnfyy...

Do it nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgewaehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd94lnue ! The more implementation options we have, the more decentralized bitcoin becomes. This is the way.

Do we have any third implementation that would simply be conservative? Just a v28 with only patches in case of network-threatening bugs? I'd like to support that kind of third implementation. Might as well use those sats while they still hold some value...