Here is why i love ordinals. First go to oodinals.com and if like me you get a 404 error, most likely because i didn't pay the bill or similer but then you realise that it was only ever a pointer. The content will live for ever on bitcoin. ordinals.com/content/bf93203…

It's time to get excited about ORD and BITMAP again. Why? Because /r/block just got merged!! What does this mean? We now have full block data through recursion!! What problem does this solve? TL;DR: we can now accurately draw Bitcoin Maps! Up until this merge, it has been impossible to resolve transaction data within an inscription without knowing the txid. That means, the full promise of Bitmap has been impossible on-chain via ord, because we cannot represent accurate transaction data. THE SOLUTION /r/block/<query> : full block hex for <hash or height> One week ago, I submitted a PR issue to Ord that would allow you to fetch full block hex with one call. It was after working with Astra to close the gap. Originally I was going to build fetching txid from blocks, but it became clear that this would lead to thousands of recursive calls per block. Astra suggested using /r/block instead to get the full block hex. With one call, you get all transaction data from the block. I wholeheartedly agreed. It just made sense. I put Astra to work and it was done within 20 minutes. I tested it on my node and it worked a charm, then I submitted my PR as an issue to ord. Last night, Casey merged /r/block/<query>. So now we have full block and transaction data! This is a game-changer for bitmap. So this morning, I'm working on something to show what is now possible. See image for a clue. But more importantly, the endpoint is available now for you all! This is truly an exciting moment, and will open a dam of development on Ord and Bitmap. Use it wisely, and build procedurally. Please show Casey some Bitmap love on this historic merge. Happy building!

It's time to get excited about ORD and BITMAP again. Why? Because /r/block just got merged!! What does this mean? We now have full block data through recursion!! What problem does this solve? TL;DR: we can now accurately draw Bitcoin Maps! Up until this merge, it has been impossible to resolve transaction data within an inscription without knowing the txid. That means, the full promise of Bitmap has been impossible on-chain via ord, because we cannot represent accurate transaction data. THE SOLUTION /r/block/<query> : full block hex for <hash or height> One week ago, I submitted a PR issue to Ord that would allow you to fetch full block hex with one call. It was after working with Astra to close the gap. Originally I was going to build fetching txid from blocks, but it became clear that this would lead to thousands of recursive calls per block. Astra suggested using /r/block instead to get the full block hex. With one call, you get all transaction data from the block. I wholeheartedly agreed. It just made sense. I put Astra to work and it was done within 20 minutes. I tested it on my node and it worked a charm, then I submitted my PR as an issue to ord. Last night, Casey merged /r/block/<query>. So now we have full block and transaction data! This is a game-changer for bitmap. So this morning, I'm working on something to show what is now possible. See image for a clue. But more importantly, the endpoint is available now for you all! This is truly an exciting moment, and will open a dam of development on Ord and Bitmap. Use it wisely, and build procedurally. Please show Casey some Bitmap love on this historic merge. Happy building!