On January 9, 2025, block 878,479, a curious@bitcoin video carried a title that is easy to skip and hard to replace: SEPARATE NAMING AND STATE. The description asked the practical version. How do you accept bitcoin for goods and services if the website is still centrally controlled? That is the adoption question. Not @imagine sitting in claim for a second day. Not the burn clock kissing one full coin. Those were the pictures on the explorer. The idea underneath is older than Spaces Protocol and is why naming on Bitcoin keeps coming back. Money already settled on a chain nobody can quietly edit. The storefront, the invoice label, and the “find me here” string still sit on DNS, a host, and a registrar. Spaces Protocol is the attempt to pull the name off that stack and leave the page free to move.
What “naming” and “state” mean when you sell something
State is the stuff that changes. Inventory. A Lightning invoice. A new Telegram after the last one died. A blog post. An nsite blob on a Blossom server. Naming is the pointer that should not change every time the state does. pay@shop. you@bitcoin. The sentence a customer can say out loud. DNS glues those together on purpose. yourshop.com is the name and, for most people, the location. Lose the domain or the host and the name is gone with the page. NIP-05 does the same trick for Nostr. BIP-353 does it carefully for payments. All of them still rent the right-hand side. Spaces Protocol splits the jobs.
- A Space such as @shop is auctioned on Bitcoin. Ten per day. About ten-day auctions. Late bids add time. The winning bid burns.
- A handle such as checkout@shop or you@bitcoin is issued under that Space. The operator commits a 32-byte Merkle root to Bitcoin. You get a certificate. Clients verify against the chain, not against a company homepage.
Change the Lightning destination next year. The name stays. Move the HTML to another host. The name stays. That is separate naming and state.
The January 9 board was the shop window, not the product
The tape that morning was the usual explorer weather. @imagine still unclaimed after 880,000 sats. @vault and @gaming in the mix. Transfers of @silk, @lava, @raw. Bids on @dev, @vip, @web, @gov. @nfl claimed. Upcoming words like @matrix, @christ, @god, @trinity, @ye sitting at a few thousand sats to even enter the queue. Past high prints: @bitcoin around 10 million sats, @ai, @1, @s.The host said again what still needs saying. Burn is for creation. After the Space exists, trade is peer to peer. Nobody should get paid for minting a word that did not exist. Pay a team and you have a registry. Pay miners a special mint tax and you give them a reason to play games. Burn is ugly and neutral. None of that is why a merchant should care. A merchant should care that pay@you can outlive you.com.
Why a Bitcoin-only shop still dies on a .com
You can be orange-pilled to the teeth and still lose the door. The domain expires. The registrar complies with a letter. The host closes the account. Cloudflare or the DNS host becomes the switch. The Lightning address was [email protected]. The Nostr badge was NIP-05 on the same domain. One invoice cycle and the public name is someone else’s. Separating naming from state means the customer has a fallback that is not “search my new Twitter.” They look up the handle. The records say where the new page is, where the new chat is, which output to pay. The app that stored those records can vanish. The certificate plus the on-chain root still prove who holds the name. That is the sentence to put under every Spaces Protocol thumbnail. The website can move. The name should not have to.
Handles on mainnet are the missing half of that 2025 title
SEPARATE NAMING AND STATE was filmed when auctions were the only public game. The split is real now.@bitcoin issues handles through Nacho and atbitcoin.com. One-time price under that Space has been $25. Nacho is a keystore and resolver, not a bitcoin send wallet. You publish payment rails and social pointers. Lookups verify on the device. You do not need @trinity to accept bitcoin. You need one handle you will print on the packing slip. @imagine is a namespace for whoever finally claims it and issues name@imagine. Most people should not collect roots. Most people should attach state to a handle and keep the name stable. Top-level Spaces still need the UTXO kept alive. Issued handles do not take a yearly ICANN bill. Confuse those two layers and you will write “all names expire” and be wrong.
What has to support the name (or the split fails)
A name with no software is a collectible. The January video already knew that in the background. Wallets, browsers, and Nostr clients are the state machines that must learn the new pointer.
- A send box that accepts you@bitcoin and picks Lightning, on-chain, or Silent Payments.
- A Nostr client that shows the handle instead of only npub1… or a NIP-05 domain.
- A browser path (Freedom Browser, a Brave checkbox next to ENS, nsite) so the page can live off DNS if you want it to.
Until those exist, @hello as a “social network root” is a story. After they exist, @hello is a directory. Survival of the fittest among Handshake, ENS, Namecoin, and Spaces will be decided by what resolves in the app the user already opens. Bitcoin as root of trust is the reason to pick Spaces. Features in the wallet are the reason anyone else will notice.
Burn, Satoshi’s lost coins, and the merchant who does not care
Almost one bitcoin burned on first issuance made good television. Satoshi’s untouched pile made a rhyme. Both are side quests for a shop. The merchant question is simpler. Do I pay a registrar forever for the word on the invoice, or do I pay once (or bid once) to bind a word to a key I hold? Secondary sales do not burn. Creation does. If that bothers you more than a seized domain, you are optimizing the wrong risk.
How to act on “separate naming and state” this week
Get one handle. Nacho or atbitcoin.com. Publish a payment record and a contact record. That is the name. Point the current site or invoice at that handle. When the host changes, update the record, not the printed name. If you must run a root, bid on a word you will issue under. @shop without pay@shop is a plaque. If you build, resolve with Fabric. Do not wait for Chrome to love you. One client that prints the handle teaches more people than another explorer stream. Watch the explorer to learn the auction clock. Do not confuse that clock with the product.
The title that should have been on the thumbnail
How are you going to accept bitcoin if the website can be turned off? Separate the name from the page. Put the name on Bitcoin. Let the page live wherever it can stay up. That is Spaces Protocol when it is not an auction sport.you@bitcoin is the pointer. The cart, the chat, and the HTML are state. Keep them apart and a ban is an inconvenience. Keep them glued to yourshop.com and a ban is a new brand.
Watch: SEPARATE NAMING AND STATE
Protocol: spacesprotocol.org
Explorer: explorer.spacesprotocol.org
Handle: nacho.io · atbitcoin.com
