Avatar
Matthew Kratter 1mo ago

Big Shipcoiners Love Big Op Returns

https://blossom.primal.net/bd041c156a2a89f66ca7043626a961e85e08c6fbf762a2ba269b4e1f40eebef4.mp4

Reply to this note

Please Login to reply.

Discussion

Avatar
BitcoinIsFuture 1mo ago

Here Jameson Slopp telling you your node doesn't matter.

Yet the OP_RETURN filters kep OP_RETURN data below 83 Bytes for 14 years.

Avatar
Pepe López 1mo ago

nostr:nprofile1qyv8wumn8ghj7mn0wd68ytnvdac8qtnnda3kjctv9uqzpaegm8nwwpyrtrnsjv84efjtp9mhpkvfenvxs487vx8d48y28qgxxgzsvk slopping right 😂🤣

Avatar
Christopher 1mo ago

What a cute couple. They just want to be recognized.

Avatar
Jameson Lopp 1mo ago

Hilarious to see you claim large OP_RETURN data is antithetical to individuals running a node given that more OP_RETURN data directly results in smaller block sizes, smaller UTXO set, and thus lower resource requirements to run a fully validating node.

🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡🤡

Avatar
Resonance Cascade The II 1mo ago

Hilarious that you want to see OP_RETURN increased to 100 kB to service your "extreme edge case" for Citrea

Here is a Bitcoin pleb quote for you;

"Bitcoin changes you, you don't change Bitcoin"

Avatar
GFY 1mo ago

YOU CONTINUE TO HAVE NO LEGIT POINTS... WHY DO YOU STAY ON NOSTR COLLECTING L'S 🤢🤣

Avatar
Pepe López 1mo ago

Maybe @Saylor, with his sw dev background, could push alternatives to core deviation.

Meanwhile, it seems MSTR run 10K+ nodes with strict mempool policy (labeled "/Satoshi:0.21.1(MSTR-SoundMoney)/" 👍

Avatar
Resonance Cascade The II 1mo ago

I don't think this is the solution