pull down to refresh
Client diversity before something breaks. One explorer, one Nacho, one @bitcoin store. That’s a single outage away from “Spaces is down.” Second explorer and a non-team operator issuing under a known Space is important.
Subnames at the following list can be purchased through https://spaceswallet.com today!
https://spacesops.com/getspaces?app=spaces-wallet&format=html
@space
@nsite
@bitcoinand
@thisweekinbitcoin
@twib
@yeti
@bitcoin21
@usdt
@usat
@cnht
@mxnt
@xaut
@usdc
@eurc
@zap
@pubkey
@cyber
@swiftyI've got about 60 that I've secured so far. Some are for future projects and not intended to be resold. I may add more, but this list is where I started. There are currently 3620 top-level names registered. My platform has the ability to manage the sale of subnames via a delegation option so the name owners retain their ownership. There is no way for me to "reach out" to those owners and offer to help so I have to relay on word of mouth.
If you want a certain name@space_name you might consider opening a name for bidding and becoming the owner yourself. Control your own destiny.
I plugged this project into AI and generated critiques:
Issuance is the bottleneck. Treat it as a product. Handles are sovereign after issue. Getting one still depends on an operator who can stall, price-gouge, or vanish. Publish SLAs: max time from pay → staged → committed → cert after 150 blocks. If @bitcoin is the front door, it has to behave like one.
Resolution is the product, not the auction. A name nobody’s browser understands is a collectible. Rank work: Chrome/Brave extension or system resolver, mail without DNS, Nostr clients with NIP-SPACES on by default, one “paste you@bitcoin and it just works” path. Explorer-only success is failure.
Proving centralizes operators. CUDA boxes and 150-block finality mean a few people issue for everyone. Document a public remote-prover option with no custody of keys. If only three machines can commit @popular, say so and recruit more.
Don’t sell the last rung as the first. Certificate ≠ on-chain num. Most users will never do the UTXO step. UI should show three states: issued, published on relays, fully on-chain. Calling all three “sovereign” trains people to stop at the weakest one.
Certrelay privacy is optional and invisible. Public relays can link IP → name. Default Nacho/docs should say: own relay or you’re leaking like a public Electrum server. Ship one-click relay on Start9/Umbrel.
Terminology still fights the user. Space / handle / subspace / num / cert / commitment / staged / published. Pick one glossary and kill the rest in the UI.
Prove it against DNS in a demo, not a white paper. One video: buy handle, lose the operator, still verify on a fresh phone. One video: ICANN-style takedown that Spaces survives.
Burn-auction optics. Burning BTC is clean. It also prices out the people you want using names. Keep the burn. Add a public faucet path that isn’t junk names only, or community Spaces that issue for free with a published queue.
Client diversity before something breaks. One explorer, one Nacho, one @bitcoin store. That’s a single outage away from “Spaces is down.” Second explorer and a non-team operator issuing under a known Space is important.