- Owner
- verified on-chain
- Primary address
- bc1p… connected
- Avatar
- inscription-linked
- Listing
- not listed
What is BNRP?
BNRP is an open resolution layer for BTC-native names. It gives wallets, marketplaces, and apps a shared way to read name records — ownership, avatars, addresses, inscriptions, and provenance data — directly from Bitcoin-native sources.
It is not a registry. It does not issue names. It is the resolver: a standard for reading what already exists on-chain.
- name owner address
- name primary Bitcoin address
- name avatar / inscription link
- name text records (Twitter, website, description)
- name marketplace listing status
- address primary name (reverse lookup)
- namespace supported resolver / indexer
What BTCNative uses it for
BTCNative uses BNRP to index, verify, and display BTC-native identity records across supported namespaces including .btc, .sats, .x, .ord, and others.
What BNRP does not mean
Resolver examples
These are illustrative examples of how BNRP reads name data. Live data is fetched from on-chain sources at resolution time.
- Owner
- verified on-chain
- Primary address
- bc1p… connected
- Avatar
- none set
- Listing
- listed
- Owner
- unresolved placeholder
- Primary address
- unavailable
- Avatar
- none set
- Listing
- listed
Developer reference
BNRP provides a normalized record model for BTC-native names. The API returns a consistent shape regardless of which underlying indexer resolved the name.
/v1/resolve/{name}
Forward resolve — name → records
/v1/reverse/{address}
Reverse resolve — address → primary name
/v1/batch?names=a,b,c
Batch resolve — up to 20 names
Base URL: https://api.bnrp.name/v1/
{
"name": "example.btc",
"owner": "bc1p...",
"primaryAddress": "bc1p...",
"avatar": "inscriptionId or URL",
"records": {
"twitter": "",
"website": "",
"description": ""
},
"listing": {
"status": "listed",
"price": "",
"marketplace": "BTCNative"
},
"provenance": {
"source": "unisat | btcname | sns",
"verifiedAt": "2026-01-01T00:00:00Z"
}
}