btc.glass
Give your .btc name a home.
Bring your name and something worth sharing. When you’re done, anyone can open yourname.btc.glass in their browser.
01 Start with your name
A .btc name is a plain-text inscription like yourname.btc. The first inscription of a name owns it. You can inscribe a new one with any Ordinals inscription tool, or buy one on a marketplace.
Names are one word: no spaces, no punctuation (so no hyphen (-) or underscore (_)), up to 32 bytes including .btc. Emoji and non-Latin letters work.
02 Inscribe your site
The easy way: make your site, connect UniSat and press Publish. In UniSat you sign once (no money moves) and approve the first payment for the website. After 10 to 60 minutes you approve a second, smaller payment that connects your name. Usually US$13 to US$20 in total. US$5 of that is the btc.glass fee.
Prefer to do it yourself? Download the HTML from the editor, upload it under Files on UniSat, then follow step 3.
Inscribe an HTML page, an image, a video, even a game. Keep the files small, or split them into several inscriptions and load them from your page with paths like /content/<inscription id>. That’s called recursion, and it works on btc.glass exactly as on ordinals.com.
03 Connect your name and content
Inscribe this text from the wallet that holds your name, with your own name and your site’s inscription id. The newest one wins, so you can change your site any time by inscribing a new pointer.
{
"p": "btcname",
"op": "routing",
"name": "yourname.btc",
"ord_handle": "www",
"ord_index": "<your site's inscription id>i0"
}
Then open yourname.btc.glass. It usually shows up within a few minutes of the inscription confirming.
How it works
When you open name.btc.glass, btc.glass looks up who owns name.btc, finds the newest pointer they inscribed, and shows the inscription it points to. Content comes from three independent Ordinals servers, and the blocks they return are checked against Bitcoin’s own records before they’re used.
Each name runs as its own website, so one site can’t read another site’s data or touch btc.glass.
For builders
| Path or header | What it gives you |
|---|---|
| /content/<id> | An inscription’s content. Use it to load other inscriptions from your site. |
| /r/… | Ordinals recursive endpoints (block height, children, sat info), same as ordinals.com. |
| x-target-inscription | Sent with every site, together with x-name-inscription and x-routing-inscription, so you can check them on any Ordinals explorer. |
Safety
Browsing never needs a wallet. Publishing asks for three things in UniSat, and nothing else: to connect, to sign a short message, and to approve two payments, first for your website and later a smaller one that connects your name. Publishing asks you to sign a message proving you control the name. It cannot move funds. btc.glass never holds your money or your keys; payments go to UniSat, which inscribes your site.
Technical details
The BIP-322 simple signature binds the name, holder address, refund address, site SHA-256, job ID and issue time; one authorization per job, valid for ten minutes. Taproot, P2WPKH and P2SH-P2WPKH holders are supported; legacy P2PKH is not. One-click payment uses UniSat sendBitcoin, only for the order the server has just re-verified, only for its exact amount, capped at 0.01 BTC. Paying by QR from any wallet also works. Before UniSat opens, the server records the payment attempt, so btc.glass will not open a second payment for the same order from another tab or browser. If a payment result is unclear, the order is left alone until UniSat expires it; check UniSat's activity before paying any new order. Keep the status link to resume a job instead of starting another.
Silent Receive separately requests a message signature at btc.glass/bind. A *.btc.glass site that asks you to connect or sign is run by that site’s author, not by us. See a phishing or malicious site? Tell us at abuse@btc.glass and we’ll block it on btc.glass.