On February 19, 2025, with Bitcoin near block height 884,468 and the price trading between roughly $93,700 and $96,700, the Spaces Protocol explorer showed 799 registered spaces and more than 1.12 Bitcoin already burned through auctions. The count was climbing toward 1,000. Each burned satoshi permanently reduces the circulating supply, joining coins that can never be spent again. The activity reflects open bidding for short human-readable names that replace long alphanumeric Bitcoin addresses, serve as Nostr usernames, and function as stable identifiers across payment and social applications.
Spaces Protocol allocates top-level names through auctions that run on Bitcoin itself. Every 144 blocks, up to ten spaces advance from a pre-auction priority queue ordered by bid amount. The claim window lasts about 1,440 blocks. The highest bidder at the close controls the associated UTXO. All bids are burned. No operator, foundation, or developer retains the proceeds. The annual issuance is capped at roughly 3,600 spaces. Because the supply is fixed and allocation is open, short and memorable labels clear first. Later participants face higher bids or select from longer names that remain available. The protocol does not expand the daily or annual limit when demand rises. It continues the same auction process, burns the bids, and records the winners on Bitcoin.
The practical result is a single stable identifier. A user who owns a space can publish a Bitcoin address, a silent payment address, a Lightning offer, or other payment records behind that name. Senders resolve the name and receive the current payment instruction without copying a long string. The same name can also serve as a Nostr username. Once the name is registered, the owner controls the records that appear when the name is looked up. The records can be updated later without changing the name itself. This separation removes the need to share or verify long addresses for routine payments while keeping the underlying address under the owner’s exclusive control.
Handles issued under a claimed space follow a different path that keeps the on-chain footprint small. An operator maintains a Merkle tree of handles such as alice@bitcoin. The operator periodically commits the root of that tree to Bitcoin as a 32-byte hash. Each handle owner receives an off-chain certificate that proves inclusion in the committed tree and non-existence in every prior commitment. After the root confirms, the handle cannot be revoked by the operator or by any third party. Verification of the certificate against the Bitcoin-anchored root does not require trust in a remote server for the final proof. The design allows many handles to share a single on-chain commitment while preserving the non-revocable character of ownership once the commitment is confirmed.
The video notes that the same seed phrase can generate different addresses depending on the derivation path. A passphrase adds another layer. Multi-signature setups and other advanced configurations remain available. Spaces does not replace these tools. It provides a human-readable pointer that can resolve to whichever address or configuration the owner currently publishes. The name stays constant while the data behind it changes. This reduces the ongoing cost of maintaining a useful identifier and keeps the chain free of unnecessary data for every update.
Security follows from the underlying chain. Name registrations and root commitments are ordinary Bitcoin transactions. They inherit the same resistance to reversal that applies to any confirmed Bitcoin transfer. The cryptographic rules that prevent double-spending also prevent unauthorized reassignment of a claimed space. Users who verify the certificate against the committed root do not need to trust an intermediary for the final check. This removes the single point of failure that exists when a centralized registrar controls both the name and the resolution path.
The open-source nature of the project allows any developer to inspect the code, propose changes, or build additional clients. Contributions do not require permission from a foundation or company. The protocol itself does not rely on a token or a separate blockchain. Bitcoin is the settlement layer, and the naming rules are enforced by interpreting existing transaction patterns. Anyone who can submit a Bitcoin transaction can participate in an auction. Anyone who can verify a Merkle proof can confirm a handle. These properties keep the system open to new participants without requiring coordination with a central authority.
Compared with traditional domain systems, Spaces removes the registrar that can suspend a name for policy reasons. Compared with earlier Bitcoin naming attempts, it avoids placing large amounts of data directly on-chain and avoids dependence on soft forks that have not activated. The combination of auction-based allocation, burned bids, off-chain handle issuance, and Bitcoin-anchored commitments produces a system in which short names are scarce, ownership is non-revocable after claim, and verification is possible without a trusted resolver.
For everyday use, the practical result is a single stable identifier. A merchant can publish a Spaces handle on a sign or a receipt. Customers resolve the handle in a compatible wallet and receive the current Bitcoin or Lightning address. The merchant can rotate the underlying address later without reprinting materials. A user can share the same handle across payment apps, Nostr clients, and other services. Lookups that verify against the trust anchor derived from Bitcoin do not route the final proof through a company server. The name remains under the owner’s keys even if the original application or operator disappears.
The protocol launched on mainnet on November 20, 2024. By mid-February 2025 the registered count had reached 799 and was approaching 1,000, with more than 1.12 Bitcoin burned. Auctions continued. Handles had begun to be issued under the first production operators. Documentation and client software were available. The explorer showed open auctions, claim windows, and registered spaces. A mobile application generated keys on the device, submitted a name to an operator, and later received the certificate after the root was committed. Full-node users could run the client, bid on spaces, and verify the entire state against Bitcoin. Both paths end with control of a name whose ownership proof can be checked by any party that follows the protocol rules.
Adoption depends on continued integration by wallets and applications. Each new resolver that accepts a Spaces handle increases the number of places where a short name can be used instead of a long address. Each new auction that clears a desirable name reduces the remaining supply of short labels. The fixed annual issuance rate means that early participants secure names while availability is higher. Later participants compete for the remaining supply or purchase existing spaces on secondary markets. The underlying mechanics remain the same: open bidding, burned proceeds, non-revocable ownership, and verifiable commitments on Bitcoin.
The combination of human-readable names, Bitcoin security, and the ability to update records without changing the name addresses a long-standing friction in Bitcoin. Users no longer need to share or verify long strings for routine payments. Developers can resolve names in a few lines of code and verify the result against a Bitcoin-anchored root. Merchants can publish a stable identifier that continues to work when addresses change. These properties are available today through the existing clients and documentation. As more applications add support, the same name becomes useful across a larger set of services while remaining under the owner’s exclusive control.
The approaching milestone of 1,000 registered spaces is a visible signal of demand meeting a hard annual limit. Single-digit and two-digit combinations have already cleared or are clearing. Longer memorable names remain available, yet the total registered count is still low relative to the annual cap. The same rules that are producing today’s bids will continue to allocate the remaining supply. Participants who act while the registered total is near 800 secure names under less competition than will exist once that number approaches the yearly limit. The protocol does not expand the annual issuance to meet demand. It simply continues the auction process, burns the bids, and records the winners on Bitcoin.
Visit https://spacesprotocol.org/ to learn more, check the explorer at https://explorer.spacesprotocol.org/, review the documentation at https://docs.spacesprotocol.org/, explore the marketplace at https://spaces.market/, or get a handle through the Nacho app at https://nacho.io/.
