X.KOJIRA.IO
Timeline

Richard Nakamoto

[email protected]
npub1dwekunm9w9agazkwcq88ymxmj0j3qgxcu4mwfqnjqvyusa9cuxrs0wsqel
Founder of Bitcoin Runners and Lightning Piggy | Co-founder of the Running Bitcoin Challenge | Running Bitcoin for Hal. Humble sub-3 marathoner, Ironman, Chartered Engineer, vibe coder. Freedom tech and proof-of-work.
Looking strong Rocket! 💪
Good luck with your training. Treasure each run 🔥
👀
Big day tomorrow, my first Ironman attempt. 3.8km swim, 180km ride followed by a marathon (42.2km/26.2miles). Wish me luck, Nostr!

Keeping the race gear spread photo tradition going, here’s mine…

#ironman #copenhagen #IMCopenhagen
https://blossom.primal.net/698f5f4cc045251b84938370caa614…
TIL: October 31st is World Savings Day. Established in 1924 to rebuild trust in the very banking system Satoshi’s whitepaper challenged. The irony of publishing it on this date, just two weeks after a $2 trillion bank bailout, is poetic.
“The only way against spam is to disincentivize its most harmful forms.” — LukasHozda

1/ You hate UTXO bloat. Me too. But before you signal for BIP-110, let’s talk about how we fix it — because the method matters as much as the goal.

2/ BIP-110 fights spam by changing consensus rules — the base-layer agreement every node must follow. That sounds powerful, but it means you’re setting a precedent: consensus can now decide which UTXOs are valid and which aren’t.

3/ Here’s the problem: once you establish that Bitcoin’s consensus layer can freeze or restrict UTXOs, you’ve opened a door that’s very hard to close. Today it’s inscriptions. Tomorrow it could be your coins. The principle “no one can make your bitcoin unspendable” is what makes Bitcoin Bitcoin.

4/ Think of it like free speech. You can hate what someone says, but the moment you let an authority decide what’s allowed, you’ve given up the principle that protects you too.

5/ So what’s the alternative? Make the clean methods win. OP_RETURN was literally designed for non-financial data. It’s prunable — it does NOT bloat the UTXO set. The real bloat comes from inscriptions stuffing data into Taproot witness fields and fake multisig outputs that nodes must track forever.
6/ Instead of banning the bad methods (which creative devs will route around anyway), make OP_RETURN the cheapest and easiest path. Rational actors follow incentives. If the non-bloating method is the most economical, people will use it naturally.

7/ Node-level filtering? Totally fine. That’s your node, your choice. But consensus-level restrictions are everyone’s choice imposed on everyone — and that’s a very different thing.

8/ TL;DR:
∙ UTXO bloat is a real problem ✅
∙ BIP-110’s goal is valid ✅
∙ But solving it by changing consensus sets a dangerous precedent ❌
∙ Better path: make non-bloating methods (OP_RETURN) the most economical option 💡
∙ Fix incentives, don’t build censorship tools

We can protect Bitcoin’s monetary purpose without sacrificing the property rights that make it worth protecting in the first place. 🤝​​​​​​​​​​​​​​​​
Great question, and yes, the distinction matters a lot here.
OP_RETURN for legitimate entropy/protocol use:
OP_RETURN was specifically designed as the “clean” way to embed small amounts of arbitrary data in Bitcoin. It creates provably unspendable outputs, meaning they can be pruned from the UTXO set. Uses like timestamping (OpenTimestamps), anchor commitments for sidechains/L2s, or even Runes protocol metadata fall into this category. The data goes in, the output is immediately prunable — no UTXO bloat.
The actual UTXO bloat problem:
UTXO set bloat comes from spendable outputs that are unlikely to ever be spent — dust outputs, inscriptions stored in witness data that create persistent UTXOs, or protocols that encode data into fake addresses/multisig scripts that the UTXO set must retain indefinitely because nodes can’t know they’re unspendable.
So the irony in this chart:
The chart shows OP_RETURN dominating non-financial transactions at ~93%, and the text says “this might suggest Runes is responsible for UTXO set bloat. It’s not.” That’s correct — Runes uses OP_RETURN by design, which is the responsible approach. OP_RETURN outputs don’t persist in the UTXO set. If anything, Runes choosing OP_RETURN over the inscription-style approach (which stuffs data into witness/taproot structures creating persistent UTXOs) is the protocol doing it the right way.
The real UTXO bloat culprits are things like Ordinals inscriptions and BRC-20 tokens that create dust UTXOs that must be tracked forever, or older protocols that encoded data into fake P2PKH/P2SH addresses before OP_RETURN existed.
So high OP_RETURN transaction count ≠ UTXO bloat. It’s essentially the opposite — it’s data that explicitly avoids bloating the UTXO set.​​​​​​​​​​​​​​​​
Non-transactional data has been present on Bitcoin from the very beginning. The Genesis Block (Block 0), mined by Satoshi Nakamoto on January 3, 2009, contained the message “The Times 03/Jan/2009 Chancellor on brink of second bailout for banks” embedded in the coinbase parameter . This is the first instance of arbitrary, non-transactional data on the Bitcoin blockchain.
Every mined block has a coinbase field of up to 100 bytes that normally contains data like the block number, timestamp, and difficulty, but can include arbitrary data . Satoshi used this field to embed the Times headline, likely both as a timestamp proof and a political statement about the banking system.
People rapidly figured out how to encode arbitrary content into the Bitcoin blockchain by using hex data in place of Bitcoin addresses , and early examples included things like the Bitcoin logo image hidden among normal transactions. Later, the OP_RETURN opcode provided an official method for embedding small amounts of arbitrary data in transactions.
So in short — non-transactional data has been there since literally day one, block zero.​​​​​​​​​​​​​​​​
BIP-110 is flawed: every transaction that pays fees secures the network. Policing which ones get that chance undermines censorship resistance, is technically futile, and weakens network security.
This 👌
Spot on. You are the jammy winner! Congratulations ⚡️⚡️⚡️
Simplicity
Casa Nostra! Spotted in Lanzarote.
TIL “Nostra” is the feminine singular form of the Latin word “noster”, meaning “our”.
Our House! So apt.
https://blossom.primal.net/eef28b6de7f795388d04da48670d80…
https://blossom.primal.net/92297680c428bac726ad61ac5cf45a…
Will do. Thank you 🤙
Ooooh nice! I’ll be in London later today... Is it available directly from nprofile1qqstkqt54… ?
Morning routine:
Get light.
Take a cold shower.
Drink a hot cup of El Salvadorian coffee paid for with bitcoin.

👌 la cruz by nprofile1qqstt3qhh…
https://blossom.primal.net/fc65738d2d64f1a19221dd25cb297a…
Amazing! The Nostr transport layer is changing everything.
Thank you Jack and team.
👏👏👏👏👏👏
Let’s all share the zap.steam link (when available) on other social media channels for maximum nostr protocol exposure. note1tq2hnvpelhq8p…
Nice one Matt. Looking forward to it.

To help, we can all share the zap.steam link here and on other social media channels for maximum nostr protocol exposure.
🤩 Zapped!
Bravo! 💪🤩🧡
Update about #BitcoinGambia 🇬🇲 to follow. Has been a crazy couple of weeks.

And now tomorrow, I’m running Manchester Marathon representing #[1]
The product of ~4months of training, which has been time consuming (~2hours a day), but worth it for the fitness ATH and quality time spent with likeminded friends.

Talking of friends, I’ve been trying to keep up with #[2] since she starter her epic 21x10km running challenge on April 1st. Isn’t she amazing! 104km in, with 6 days to go.

Vest from #[3] Lightweight and fast! Can recommend 💪 #BitcoinRunners #TeamSatoshi #FirstPostedOnNostr