Experimental

A name is no longer a handle.
It is a namespace.

Create names beneath your Bitcoin name. Build your namespace on Bitcoin.

Open Subname Manager Read the protocol
Example namespace
artist.btc
├─ shop.artist.btc
├─ vault.artist.btc
└─ archive.artist.btc
Protocol

What is a subname?

Three concepts. No jargon.

Parent name

artist.btc

The main name you own on Bitcoin. You control it and everything beneath it.

Subname

shop.artist.btc

A name you create beneath your parent name. Points to an address, website, or any custom record.

Records

btc, url, avatar

What the subname resolves to: a BTC address, a website, an avatar, and more. Set by you, verified by BNRP.

Use cases

What you can build

One name. A full namespace. Each subname targets something specific.

Payment address
pay.name.btc

Send a specific address for payments only.

Cold vault
vault.name.btc

Separate address for long-term holds.

Shop
shop.name.btc

Link your store or marketplace listing.

Archive
archive.name.btc

Old work, past releases, historical records.

Collection item
001.collection.btc

Index items in a collection by subname label.

Support
support.brand.btc

Support channel for a brand or product.

Docs
docs.protocol.btc

Documentation site for a protocol.

AI agent
agent.wallet.btc

Autonomous agent wallet with a named address.

Process

How it works

Five steps from a name you own to a live subname record on Bitcoin.

01
Start with a name you own

Any Bitcoin-native name (e.g. artist.btc) held in your wallet is a valid namespace root.

02
Create a name beneath it

Choose a label like shop or vault. The full subname becomes shop.artist.btc.

03
Choose what it points to

Set a BTC address, website URL, or custom key-value records for that subname.

04
Review the record

Verify the BNRP event payload before signing. Confirm ownership and record data are correct.

05
Manage it on-chain

Update records anytime. Every change is permanent history on Bitcoin. The latest valid update is the active state.

Protocol design

Permanent history. Current state.

Every update to a subname is inscribed on Bitcoin. Nothing is deleted. The newest valid update is the active record.

Created
block #835,201
Updated BTC address
block #841,078
Added website
block #847,450
Current record
active state
How BNRP determines the active record: BNRP shows the newest authorized update. A newer update only counts if it was created by the owner or approved manager, follows the namespace rules, and has not been revoked.

What to verify before using a subname

Subname records live on Bitcoin, but trust requires verification. Read before you rely on a subname.

Only the first inscription is canonical

Re-inscribed names may have competing records. Always verify the source inscription on ordinals.com before trusting a subname record.

Check the owner

A subname points wherever its parent name owner sets it. Verify current ownership before trusting any payment address or identity record.

Experimental protocol

Subname issuance is live on testnet only. Do not use for real funds without independent verification. The protocol may change.

Parent controls

The parent name owner can update or revoke subname records at any time. A subname is not independently owned unless the protocol explicitly supports delegation.

Ready to build your namespace?

The Subname Manager lets you create and manage records beneath any name you own. Experimental. Testnet only.

Open Subname Manager Read the BNRP protocol