/r/block — the day the map could draw itself
The Bitmap idea has always carried a quiet contradiction: it asks you to see a Bitcoin block as a place, a little country of transactions — yet for years an inscription could not actually read those transactions from inside the chain. On 12 September 2026, a single line merged into ord closed the gap. The map can finally draw itself, on-chain, from its own memory.
Start with the promise, because it is a beautiful one and it has been half-kept for years. Bitmap theory says something almost childlike and almost profound at once: that every Bitcoin block is a place. Not a ledger entry, not a number — a territory, with an area you could pace out and parcels you could stand in, one parcel for every transaction the block confirmed. Block 840,000 is a district. So is the block your birthday fell in. The whole chain, read this way, becomes a map a million blocks wide, and owning a "bitmap" means holding the deed to one of its provinces.
It is a lovely idea, and if you have wandered our explainer you have met it before. But there was always a crack running down the middle of it, and honest builders knew exactly where. To draw a district accurately — to lay out its parcels the way the block actually laid out its transactions — you need the block's transactions. And an inscription, a program living inside the chain with no server to phone, could not get them.
The wall
The magic that lets an inscription do anything interesting is called recursion: the ability, from inside one piece of on-chain data, to reach out and read another. It is what turns a static image into a program that composes itself from the chain's own materials, with nothing off in a data centre to trust or to fail. Recursion is the whole reason an inscription can be honest — it depends on nothing but Bitcoin.
But recursion had a blind spot precisely at the thing bitmaps needed most. You could ask the chain plenty of questions, yet you could not, from inside an inscription, resolve the transactions of a block without already knowing each transaction's id — and to gather those ids you'd fire off thousands of recursive calls per block, which is no way to draw a picture. So the full promise of Bitmap had never actually run on-chain through ord. Districts were drawn with data fetched from the outside, or approximated, or simply gestured at. The map existed everywhere except the one place the philosophy insisted it must live: inside the chain itself.
The map existed everywhere except the one place the philosophy insisted it must live: inside the chain itself.
One call
The fix, when it came, had the tidy inevitability that good engineering often has in hindsight. Rather than teach an inscription to hunt down transactions one id at a time, you give it the whole block in a single breath: /r/block/<query> — pass a height or a hash, receive the full block hex. Header and every transaction, all of it, in one recursive call. From there an inscription can parse the block itself and know, exactly and on-chain, what happened inside it. Every parcel accounted for. The district can finally be drawn from the ground truth of the block.
The path there is a small parable about how this culture actually builds. A community developer had been circling the problem, first trying to fetch transaction ids from blocks — the thousands-of-calls dead end — before landing, in conversation, on the cleaner idea: don't fetch the pieces, fetch the block. The working proposal went up as an ord issue, ready to merge. And on the evening of 12 September 2026, Casey Rodarmor — who wrote ordinals into being — merged it as pull request #4563. One commit. Five checks green. A line of code, and a wall that had stood for years was simply gone.
Why a museum notices
We keep this one not in the Ruins wing but in the Dispatches, because it is the opposite of a ruin — it is a promise finally made good. And it rhymes with the single idea this whole museum keeps returning to: that Bitcoin's ledger forgets nothing, and that the interesting thing is what you can build once you take that memory seriously. For years the chain remembered every transaction perfectly and the pictures we drew of it still had to lean on the outside world. Now the pictures can be drawn from the memory directly. The block describes itself. The map is no longer a rendering of the territory kept somewhere else; the territory hands you the map.
There is a lesson in the how, too, and it is not a small one. The thing that had blocked the dream for years was closed by a community builder and a maintainer agreeing, in the open, that the simple idea was the right one — an issue, a pull request, a merge, a deleted branch, all of it visible to anyone who cares to read the record. No committee, no roadmap, no permission. Just the oldest motion in open source: someone saw the wall, described the door, and someone with the keys agreed. If you build on Bitcoin, or on the chains that took its lessons and carried them further, that is the ceremony worth learning. Build in the open. Build procedurally. Leave a record the chain can keep.
The endpoint is live now. Somewhere this week, for the first time, a block is drawing an honest picture of itself with nothing underneath it but Bitcoin. That is a good day for the map, and a good day for the idea that a place can be made of nothing but arithmetic and still be worth standing in.