bitoshi blockamoto 🧱 BITMAP 🟧

Creator of Bitmap Theory and | Take advantage of data's unique ability to be parsed from different angels.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

Gateway: The Sats Update (v0.7.7)

Ship fast, fix later. Now we have Sat compatibility in Gateway. It's messy but we'll tidy up when we're done.

https://t.co/qahg2Exkb5

So, what have we got here?

Now you can enter any sat number and see details.
You can also use @rodarmor style sat names.
You can build a sat ranges index to unlock Ordinals.
Choose live or retained ranges (full Sat history).
Sats tracks inscription ownership.
Powered by Bitcoin Positional System.
Browser extension registers <number>.sat.

I'm purposefully keeping this version very blunt in my announcement delivery because I've been shipping daily feature updates, and it's important I give you the disclaimer that these 0.7 versions are for early public testing. I'm already noticing things that could be better. What I see so far though, it works. And we're almost finished with 0.7 versions now... just one more major feature to go before I tidy up around here.

The v0.7.8 update following this v0.7.7 is what you've all been waiting for... Bitmap! The most exciting and neccesary update for our community, including Bitmap Standard indexing, and Bitmap Chain validation and comparison against alternate rulesets. I will ship the /Blockamoto/bitmap repo with it to include full details on Bitmap Standard, and Bitmap Chain. Gateway will be it's first implementation.

If you're worried that I'm changing core ruleset, that's not the case. The ruleset stays. The Bitmap Standard ruleset keeps core ruleset and makes specific certain points that were assumed to be obvious.

Anyway, this update is supposed to be about Sats...

So go have fun and frollock in the field of Satoshi's!

https://t.co/qahg2Exkb5

Enjoy 🫡

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

Gateway: The Addresses Update (v0.7.6)

You can now index current OR historical Bitcoin addresses, show balances, UTXO's, and inscriptions.

https://t.co/qahg2Exkb5

The current addresses index gives you all the addresses that currently have sats in them, their balances, and UTXO's.

The historic index allows for complete historic data for each and every Bitcoin address ever used, and each UTXO that ever touched it.

There's a lot that can be done with this data!

But I won't pretend to know all the possibilities.

The Bitcoin Positional System is extremely helpful here, because instead of using a hash:outpoint, we can use BPS and point to the exact position of the prevout. This is at the core of our deeper indexes. It's extremely lightweight and human readable.

Now we have everything we need for the Sats index, and for it to be useful. That will be the next update, and following that, Bitmap! And once that's done, I'd like to do a stabilization and user friendliness and quality of life pass to really just tighten everything up, it's currently quite messy and all over the place, and to give you more timeline control and parrallel indexing, and maybe one more surprise feature, before we lock-in and version up to v0.8.0.

For now, here's v0.7.6:

🔗 https://t.co/qahg2Exkb5
👉 Existing users can update directly inside Gateway.

Enjoy! 🫡

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@singularety Yeah hashes remain the stable address.

Blocators for human readable addresses. Including block height or hash in the blocator allows for on-demand data requests.

Hashes and index numbers are interchangeable in blocators. But it assumes/requires a reorg resistant implementation.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

Gateway uses something called blocators, which stands for Bitcoin Locators (previously BPS).

I've published the specs here: https://t.co/PD8UmuP3Gm

It's looks like:
offset.output.tx.block

First satpoint of first output of first tx of second block:
0.0.0.1

I'm drafting a BIP.

WHY USE BLOCATORS?
When working with Bitcoin peers, you can only ask them for blocks. Not specific data inside.

That means, to use transaction ID's, you must have that block already, or know what block to ask for. In practical terms, this usually requires you to have a full node, since you don't know which block it is.

Since blocators point to the exact location, you can skip running a full node entirely and fetch data on-demand.

This means you don't need to have almost a terrabyte of storage available to work directly with Bitcoin.

I'm building Gateway indexes almost entirely on blocators. You can run transaction locators which indexes txid's against tx locators.

That means a translation from existing transaction hashes to blocators. This enables the use of traditional inscription ID's within Gateway.

This way you can also export indexes that use traditional ID's instead of blocators.

However, I'm so confident in blocators that I'm making it the default way to index with Gateway.

It's going slightly against the grain, but with a bridge between methods. But put it this way...

If ord used blocators for references like recursion, for example, there would be almost no need to use traditional inscription ID's.

This is a system I wrote independently of @rodarmor for Gateway (and has been perculating for a long time), but later came to find that Casey proposed literally the mirror image of blocators in an early draft of the ord protocol.

Personally, I think Casey's biggest mistake is not using a system like this to begin with. It means that for on-demand systems like Gateway, we have to have a translation index from transaction ID's to blocators (or have the raw blocks themselves) to be able to resolve an inscriptions directly from Bitcoin peers.

So that's why Gateway uses inscription locators instead of inscription ID's, because we can resolve them on-demand from Bitcoin peers.

But the limitation is simply that recursion and any reference to inscription ID won't work without having the txid locator index or raw block index.

So I'm going all in on blocators. I'm writing a BIP for Bitcoin itself, and at some point I'll propose it for ordinals itself as an alternative to ID's.

For now, we just prove its usefulness in Gateway.

Any questions, please ask!

---

THE GATEWAY BITMAP UPDATE IS ON ITS WAY

Full Bitmap District and Parcel Indexing and exporting. It will ship with a much smoother user experience for the timeline, arming of tracks for indexing, control buttons, and general usability improvements.

You can index tracks in parrallel now, with prompts when that is the best thing to do, such as when you index Bitmap or inscriptions, it will now prompt you to also arm the transaction locator track.

Bitmap Chain will be held off until a 0.8.x update. The design is final, but there are some serious considerations I want to put to the community before I roll it out. You can view the current design on the "chain" branch of the bitmap github: https://t.co/cw1lceI6bG

I'm not sweating it right this second, my focus is finishing up 0.7.x versions. After the Bitmap v0.7.8 update, the v0.7.9 will be most likely be the last 0.7.x update for deeper Ordinals indexing and usability features, which will land us nicely on v0.8.x, where my intent is validation features, a full index building engine, and tightening the ship, testing it compulsively until we are ready for the 0.9.x versions, where I will begin implementing Gateway p2p features for on-demand index sharing. Where a bitcoin node will not get you the answer, in 0.9.x versions onwards, Gateway peers shall bridge the gap. And I intend to bridge Gateway and Bitcoin peers to web hopefully in 0.9.x. One day, even mobile.

When that's done, I think we'll be ready for primetime, which is v1! At that point, I may change the name to Bitcoin Gateway just so I can appeal to plebs. If we ever add wallet features, it will be after v1, but I'm not rushing to do anything like that as it's not the main goal, and there are huge risks there. I may even keep this client focused solely on serving data.

---

Anyway, that's my word for now!

Stay notified for the Bitmap update 🔔

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

Gateway: The Sats Update (v0.7.7)

Ship fast, fix later. Now we have Sat compatibility in Gateway. It's messy but we'll tidy up when we're done.

https://t.co/qahg2Exkb5

So, what have we got here?

Now you can enter any sat number and see details.
You can also use @rodarmor style sat names.
You can build a sat ranges index to unlock Ordinals.
Choose live or retained ranges (full Sat history).
Sats tracks inscription ownership.
Powered by Bitcoin Positional System.
Browser extension registers <number>.sat.

I'm purposefully keeping this version very blunt in my announcement delivery because I've been shipping daily feature updates, and it's important I give you the disclaimer that these 0.7 versions are for early public testing. I'm already noticing things that could be better. What I see so far though, it works. And we're almost finished with 0.7 versions now... just one more major feature to go before I tidy up around here.

The v0.7.8 update following this v0.7.7 is what you've all been waiting for... Bitmap! The most exciting and neccesary update for our community, including Bitmap Standard indexing, and Bitmap Chain validation and comparison against alternate rulesets. I will ship the /Blockamoto/bitmap repo with it to include full details on Bitmap Standard, and Bitmap Chain. Gateway will be it's first implementation.

If you're worried that I'm changing core ruleset, that's not the case. The ruleset stays. The Bitmap Standard ruleset keeps core ruleset and makes specific certain points that were assumed to be obvious.

Anyway, this update is supposed to be about Sats...

So go have fun and frollock in the field of Satoshi's!

https://t.co/qahg2Exkb5

Enjoy 🫡

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@boppleton And parent/child is tied to inscription ID, not sat.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@boppleton Sat ownership changes constantly, so must be tracked.
But inscription ID's (or positions in blocator case) are constant.

[戌日阳光 @BitmapDaily]

Bitmap日报 🟧 2026年10月25日星期日
Bitmap Daily 🟧 Sunday, October 25, 2026

发文时Bitmap地板价（0.0001119BTC，数据来源：Satflow）

1⃣Bitmap 市场数据：据 Satflow 页面，Bitmap 近 24 小时成交约 0.037 BTC（昨日约 0.018 BTC），近 7 日成交约 0.147 BTC，7 日地板价变化 +1.8%，当前挂单约 6.5K 个，总供应约 97.3 万块。成交播报账号 https://t.co/48RRmSLoHY（@bitmaptrade）显示：976.bitmap 以 0.00511 BTC（约 413 美元）通过接受出价在 Satflow 成交。
数据：https://t.co/RIve7w5DvA
原帖：https://t.co/hkqvHGT39q

2⃣Bitmap 创始人 blockamoto（@blockamoto）在 GitHub 公开 blocators（比特币定位符，原名 BPS）规范，并起草 BIP（比特币改进提案）：以“偏移.输出.交易.区块”格式直接定位链上数据，无需运行近 1TB 的全节点（full node），并将作为 Gateway 默认索引（index）方式。回应 bop（@boppleton）时他表示，子地块（parcel）索引依赖区块地块（district）索引，可并行处理，逐块按规则集校验。
原帖：https://t.co/ZSFwFruNDJ
更新：https://t.co/1wj0UIUjjZ
规范：https://t.co/MtRJGsLSA5

3⃣Bitmap 社区成员 sixo（@six0Bitmap）指出，近期 Bitmap 铸造中出现的“Ghost”来自私有矿池铸造，目前只有 Mara 和 Spider Pool 能做到，这也是避开抢跑机器人的唯一方式，两家矿池合计约占全网算力 4%。他认为使用私有内存池存在争议，但不可避免。
原帖：https://t.co/zyZHGOj73s

4⃣https://t.co/SYF93MmcpO 建设者 Switch-900（@Switch_900）分享基于 three.js 打造的 https://t.co/SYF93MmcpO 测试日常，调侃称自己花数年搭建，新任“质量测试主管”几分钟就能找出漏洞。
原帖：https://t.co/fMA18nzbco
页面：https://t.co/ANYyeU8DOt

5⃣Bitmap 3D 世界构建者 Bitmap Meta（@BitmapPlotz）分享 3D 世界中狼奔跑、狐狸追兔的动画进展。
原帖：https://t.co/50rwtdkLKB
相关：https://t.co/kKJ567xX1T

6⃣创作者 Choirzooh（@choirzooh）发布 Bitmap 城市主题视频长帖：Bitmap 是一座自下而上生长的城市，约每 10 分钟新增一个区块地块；每笔交易化为一栋建筑，大小由其转移的价值决定，繁忙区块成为密集街区，安静区块成为开阔土地；地块写入比特币本身，无法被重划、移动或抹除。他另补充更正：标注为 0.bitmap 的方格实为 792,435 号区块（0.bitmap 于 2023 年 6 月 1 日铭刻），而 District 0 本身是比特币创世区块。
原帖：https://t.co/49Car8joqV
相关：https://t.co/E1juaQLedJ

📢以上内容均来源于互联网，仅为信息分享，无任何立场和广告，不构成投资建议。数字资产波动极大，请自行核实并谨慎决策。
👉关注我，获取Bitmap最新动态
🧡您的转发和点赞是我坚持不懈的动力
🫱购买Bitmap参考：https://t.co/3klgaOSJgF

#BitmapDaily #Bitmap #Ordinals #Bitcoin #BTC

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@boppleton How so?

The district parent must exist, it's the only way to create a child.
You can't create a child before the district parent exists.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@boppleton Gotcha!

The parcel index is dependent on district index but you can index in parallel. It goes block-by-block and checks against the ruleset in https://t.co/m1FHDb4bdW.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@boppleton This is for bitcoin indexing, so to index districts and parcels you can just save the key pair of district or parcel number and blocator.

That's what happens by default with bitmap district/parcel indexing.

You can convert to inscription ID instead of blocator with export.

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@bitnat_sats @palpiitaaa the old resource:

https://t.co/m2Zc9th6Yc

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

@bitnat_sats @palpiitaaa This isn't new, it's been that way for years now.

[bitmap.trade @bitmaptrade]

🟨 𝗕𝗜𝗧𝗠𝗔𝗣 𝗦𝗔𝗟𝗘 𝗔𝗟𝗘𝗥𝗧 🟨

✨ Sweep Alert ✨

🧹 dek3 just swept 6 bitmap for 0.00403 BTC ($327.13 USD)
🕵️‍♂️ Buyer: https://t.co/lT0xn1Im1F

🦉 Automated by hootertech

[sixo @six0Bitmap]

👻Ghost is from "private pools" bitmap mint.

Mara and Spider Pool can only do this.
It is the only way you not noticed from the bot!
Those pools share around 4% of the Total hashrate of the network.

It is Controversial to use private mempool, but it is Inevitable

[bitmap.trade @bitmaptrade]

🟨 𝗕𝗜𝗧𝗠𝗔𝗣 𝗦𝗔𝗟𝗘 𝗔𝗟𝗘𝗥𝗧 🟨

✨ Sweep Alert ✨

🧹 dek3 just swept 7 bitmap for 0.00375 BTC ($304.34 USD)
🕵️‍♂️ Buyer: https://t.co/lT0xn1Im1F

🦉 Automated by hootertech

[Viva La Vandal @viva_la_vandal]

Looks Rare 👀💨

[Bitfest — Bitcoin IRL @Bitfestuk]

Coming to Manchester soon.

[戌日阳光 @BitmapDaily]

Bitmap日报 🟧 2026年10月24日星期六
Bitmap Daily 🟧 Saturday, October 24, 2026

发文时Bitmap地板价（0.00010858BTC，数据来源：Satflow）

1⃣Bitmap 市场数据：据 Satflow 页面，Bitmap 近 24 小时成交约 0.018 BTC，近 7 日成交约 0.12 BTC，7 日地板价变化 +0.3%，当前挂单约 6.5K 个，总供应约 97.3 万块。成交播报账号 https://t.co/48RRmSLoHY（@bitmaptrade）显示：Perfect Punk 特征地块 53188.bitmap 以 0.00338 BTC（约 275 美元）在 Satflow 成交；买家 dek3 先后两次扫货，分别以 0.00403 BTC 扫入 6 块、以 0.00375 BTC 扫入 7 块。
原帖：https://t.co/xHVRY6zJP6
相关：https://t.co/hqVeGAjjqB

2⃣Bitmap 创始人 blockamoto（@blockamoto）在 GitHub 发布经过修订的 Bitmap 标准（Districts 区块地块与 Parcels 子地块两项标准），用于厘清此前的灰色地带。他表示，如果仍有问题无法通过这两份标准的措辞解答，就说明还有工作要做；其审计分支中还附有制定理由，以及历史索引器审计中标准与非标准规则的说明页面。
原帖：https://t.co/bIvQ9ZUM4J

3⃣Bitmap 链上世界应用 BitmapWin 开发者 urⓑanⓑor.ⓑtc（@UrbanBor）介绍 BitmapWin 上线前的 Launch Grandstand 页面：一个 3D 体素观众体育场，为正式上线倒计时。480 个真实 Bitmap 钱包按最早的链上活动获得永久座位，前 100 席为 Founders Row；头像会渲染持有者的链上 BITMAP Pixel 形象与所持 BITMAP 旗帜；持有者可通过 BIP-322 签名验证所有权入座，还有爆米花小游戏（30 BIT）。他随后表示，已有 4 位 Bitmap 持有者把 VIP 上线门票直接铭刻到自己钱包的聪上，VIP 可解锁金色座位、金色挂绳和 Bit-Café 后台 VIP 休息室。
原帖：https://t.co/EN01fIszeH
相关：https://t.co/Vqsdxx3Pg3

4⃣Bitmap 基础设施项目 BitmapCorp（@BitmapCorp）完成 BitmapCore 交互世界的第三个任务：收集比特币金币。金币以 49876 号铭文为参考，是挑战中首个 GLB 金币资产。整条路线共 307 枚金币，玩家需收集至少 70%（217 枚）才算达标；金币分布在五条车道上，每 100 米变换位置，玩家必须不断变道，难度高于此前的 Runestone 任务。团队初步目标是开发 20 个任务，完成后将转为每周固定更新。
原帖：https://t.co/nQW4UUSQPJ

5⃣Bitmap 社区成员 Weirdamoto（@Weirdamoto）发长文称，Bitmap 是草根项目而非 VC 资助项目，进展需要时间；Casey 的最新更新解锁了建设者所需的能力，全部数据已上链，Bitmap On Chain Index 已实时同步到最新区块。他列举了正在建设的项目：Bop 在做 Gladion，9ine 在推 BLiX，Bitmap News 正把 X Space 搬进一个 bitmap，BitmapSunset、Urban、Dabber 等也在各自开发。他同时批评有人试图把 Bitmap 变成以个人为中心的规则与控制，主张“不需要路线图、不需要许可、不需要国王”，Bitmap 的未来应由大家共同建设。
原帖：https://t.co/Lul1quSdF8

6⃣https://t.co/OaC83ymB9V 创始人 dabber.sats（@elevateddabber）发布 Avalon Nexus 相关内容，称 Bitmap 的价值生态正在搭建，强调互动性与互操作性；并重申“区块成为领地，领地成为建筑，建筑成为文化，bitmap is for builders”。
原帖：https://t.co/FVbGWfeKEj
相关：https://t.co/NzyaER8Idd

7⃣Bitmap 社区成员 sixo（@six0Bitmap）预告“好东西即将到来”，称将推出人人可参与的 Bitmap 铸造。
原帖：https://t.co/nUfvexZqTn

📢以上内容均来源于互联网，仅为信息分享，无任何立场和广告，不构成投资建议。数字资产波动极大，请自行核实并谨慎决策。
👉关注我，获取Bitmap最新动态
🧡您的转发和点赞是我坚持不懈的动力
🫱购买Bitmap参考：https://t.co/3klgaOSJgF

#BitmapDaily #Bitmap #Ordinals #Bitcoin #BTC

[bitmap.trade @bitmaptrade]

🟨 𝗕𝗜𝗧𝗠𝗔𝗣 𝗦𝗔𝗟𝗘 𝗔𝗟𝗘𝗥𝗧 🟨

𝗧𝗥𝗔𝗜𝗧: Perfect Punk 🤘

🤝 qz44 just accepted an offer on 53188.bitmap for 0.00338 BTC ($275.24 USD)

🕵️‍♂️ Buyer: 24hl
marketplace: @Satflow

🦉 Automated by hootertech

[bitoshi blockamoto 🧱 BITMAP 🟧 @blockamoto]

The Bitmap Standards

I've just published bitmap GitHub, with the refined Standards for Districts and Parcels. It serves to clarify any grey areas.

https://t.co/FoH3WjQ4KU

If there are any questions that cannot be answered by the wording of these two standards, then there is still work to do.

You can read my rationale in the audit branch, including pages for standard and non-standard rules in historic indexer audits.

[Smol @smolbmp]

Living in a bitmap.