The next Ord release will have a new recursive endpoint, `/r/block/`, which returns the entire 4 MB block data. That means: 🟧 Every Bitmap visualization can be built entirely inside inscriptions up to the current block, including transaction value anatomy (standard Bitmap/BitMon) and vBytes anatomy. 🟧 Indexing of the latest Bitmaps recursively. 🟧 Finally, accurate Bitmap indexing. You can search the entire block for Ord envelopes/potential Bitmaps, then call `/r/content` to pull the actual inscription content while indexing. No more arbitrary parsing rules, broken Bitmaps, or indexing issues caused by weird data formatting, OP_PUSH, etc. 🟧 Find every inscription in a block more efficiently than simply returning a list of inscription IDs. You can parse the entire block and analyze potential inscriptions to determine which ones to actually pull. For example, you could pull the block, easily filter out all BRC-20 inscriptions, and fetch only images/models based on MIME type. Congrats @rodarmor and Bitmappers 👏 The Bitcoin multiverse just got one step closer. 🌐🟧🦒

🚨 BITMAP PARCELS ARE NOW LIVE The BitmapCore Parcel Marketplace is officially LIVE. Anyone, anywhere in the world can now list, discover, buy, and sell verified Bitmap parcels directly through BitmapCore. But there is one important difference: a parcel cannot simply be listed because someone claims it belongs to a Bitmap. It must pass our on-chain verification process. 🧩 How does BitmapCore verify a parcel? A valid Bitmap parcel must satisfy the required confirmations that establish its relationship with its parent Bitmap. ✅ Confirmation 1 — The inscription The parcel must exist as a real inscription on Bitcoin. We verify its genesis transaction, inscription number, genesis block, inscriber address, and transaction data directly from the chain. ✅ Confirmation 2 — The parent Bitmap The parent M.bitmap must have been transferred to the same wallet involved in the parcel inscription. This establishes the on-chain relationship between the parcel and its parent Bitmap. ✅ Confirmation 3 — Maximum 10 blocks The transfer of the parent Bitmap cannot be arbitrarily far from the parcel inscription. The two relevant transactions must occur within a maximum difference of 10 Bitcoin blocks. They can happen in the same block, which is the ideal case, or in different blocks, provided the difference does not exceed 10 blocks. This prevents an unrelated transfer occurring hundreds or thousands of blocks later from being treated as evidence of the same parcel relationship. 🔎 Confirmation 4 — The complete verification state BitmapCore combines these blockchain conditions into a deterministic verification process before allowing a parcel to become tradable on the marketplace. If the required conditions are not satisfied, the parcel cannot be listed as a verified Bitmap parcel. This verification layer was one of the most important pieces we had to solve before opening the marketplace. Building the marketplace itself was only part of the challenge; establishing a reliable way to determine whether a parcel is genuinely connected to its parent Bitmap was the critical part. Now it is ready. 🌍 The Bitmap Parcel Marketplace is live. If you own a Bitmap parcel, you can now list it. If you're looking to acquire one, you can now explore the available parcels. BitmapCore is building infrastructure around Bitmap — from blocks and their characteristics to marketplaces, classification, and now parcels. The next chapter starts today. 🧩⚡ bitmapcore.net #Bitcoin #Bitmap #Ordinals #BitcoinOrdinals #Bitmapcore