Block space is precious, act accordingly. #Bitcoin 🍿 https://open.substack.com/pub/everstonebtc/p/the-digital-antique-why-a-bitcoin?r=7vy765&utm_medium=ios

Blocks are empty. Fees are pennies. I'm building a use case I know will eventually get priced out by higher-value transactions. That's literally the design. The people screaming about it are the same ones who told me the market decides. Make it make sense. #Bitcoin 🍿 Good morning you sons of bitches

Birthstones are live, soon to add Milestones. https://everstonebtc.com/birth/birth-sophia-grace-zhang

Each Everstone memorial produces one Bitcoin transaction containing one OP_RETURN output. Inside that output: a SHA-256 hash. That’s it. Around 80 bytes of data in a provably unspendable output that no node has to carry in its UTXO set. Ever. No images. No files. No base64-encoded obituaries. No 4MB witness blocks full of pixel art. We’re not Inscriptions. We’re not BRC-20. We are closer to what OpenTimestamps does than anything the “blockchain bloat” discourse is usually about. OP_RETURN exists specifically for this. It was added to give people a clean way to embed small data commitments without polluting the UTXO set with fake outputs that nodes would have to track forever. When we use OP_RETURN, we are doing precisely the thing it was designed to do. If that’s spam, then the feature itself is spam, and we should take it up with the developers who merged it.

We are not spamming anything, we are using the time chain for a purpose. https://substack.com/@everstonebtc/note/p-191011245?r=7vy765&utm_medium=ios&utm_source=notes-share-action

Birthstones went live Block 940,873 #Bitcoin 🍿 https://open.substack.com/pub/everstonebtc/p/birthstone-anchoring-new-life-on?r=7vy765&utm_medium=ios

Not debating nor asking permission.😊#Bitcoin 🍿 https://substack.com/@everstonebtc/note/p-191011245?r=7vy765&utm_medium=ios&utm_source=notes-share-action

Same idea

No data on chain. Just a fingerprint in the OP_return

Great motto