> For the complete documentation index, see [llms.txt](https://zmakin.gitbook.io/BNS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zmakin.gitbook.io/BNS/bitmap-naming-system.md).
# Bitmap Naming System
#### \* Disclaimer - DO NOT spend any money or create any inscriptions until a publicly announced block \*
I for one love some of my bitmap numbers. I got a couple 420s and some 69s, who wouldn't be happy? But those of us with rando strings like 628143.bitmap, what are we gonna do if we want to connect to or even remember the damn address of our beloved bitmaps? Not to mention the 4 digit Parcels on 6 (soon 7) digit Districts...
This is where we need to humanize and connect with our bitmap, we need a registry of names that are easily indexed and provable by on-chain analytics. I propose we establish the Bitmap Naming System so that we can make those connections to our bitmaps, so that we can share our names with others and give meaning on a deeper level to these addresses.
I feel that through this next step of connection to bitmap, this existential layer, we begin to lay the groundwork for bitmap to stretch its tendrils into and around all of what we now know as the interconnected web.
Bitmap IS Web3 \
\
I am only laying out here my thoughts from discussions with[ Dev9](https://x.com/Bitmapbuilder) and [Boppleton](https://x.com/boppleton), among many others as the idea expands. Thank you to all who helped or contributed.
None of this would be valid until a BLOCKHEIGHT determined after consensus on methodology and made public beforehand. At this public announcement might also be information on how to pre-register a social media linked account to a bitmap address through a method to be determined. For example, I have a Twitter account that is more than a year old and I go by Zmakin, this would allow me to register Zmakin.bitmap before the public open call. I will have 420 Blocks to register before public, and then have an additional 420 Blocks after public registration begins to transfer the name back to my same bitmap address and validly re-register the name. This list will be annotated on this post, and become part of the base ruleset of valid BNS for each registry. This is open to additions/modifications and discussion on already created names registering to a bitmap.
*Let it be understood that I do not have the coding knowledge to explain how this could all be done on-chain, but I hope that everything could eventually be run through code that lives on-chain and renders this information in an easily searchable manner for everyone to utilize freely. It should operate quickly and be up to date as each block is mined. This may only be possible for those who have core and ord indexed, and I fully accept this as a requirement to access the information the inscription is looking for.*
*I am foolishly hopeful in my ignorance at times, lol*
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://zmakin.gitbook.io/BNS/bitmap-naming-system.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.