Skip to content

Names

A bWalletX name is alice@bwalletx.com, or $alice for short. It points to one wallet’s identity key. People pay the name, and the money goes to that key.

Claim your $name
FIG. Claim a free $name
Names filter in the wallet
FIG. Your names

Your wallet signs a short statement: “this name points to my key, version N”. Our name server hands that signature out with the key. We can’t make that signature for a key we don’t hold.

Before every payment to a bWalletX name, the paying wallet checks it and shows one of three things:

  • Signed by its owner. The key’s holder put this name on this key.
  • Not signed by its owner yet. A grey note. The payment still works. Wallets sign their names when they next open.
  • Bad signature. The payment is blocked.

If a name’s key changes after you’ve paid it before, the wallet stops and asks before paying the new key.

Every change to who a name points to is written to a public, hash-chained log, including changes we make ourselves (marked admin). Read it at https://pay.bwallet.space/api/paymail/name-log. More in Name bindings for developers and at bwalletx.com/name-bindings.

YOUR WALLET$you → 02a1…9fsigned with youridentity keyBINDINGPAYMAIL SERVERChecks + storesserves it onpki lookupsPUBLIC LOG#1 npg@prev 0000…#2 npgx@prev 3f1c…#3 you@prev a07e…#4 nextANYONEVerifiessignature + eachentry's prev hash
D-02A signed nameYou sign the binding · the server publishes it · anyone can check

A handover needs two signatures: the current owner signs a release, and the new owner signs to accept. Our server can’t move a name on its own.

  • ✓ Owner-signed names, checked before paying
  • ✓ Key-change warning
  • ✓ Public name log
  • ✓ Two-party handovers
  • ◻ Daily on-chain anchor of the log
  • ◻ On-chain names (OpNS) as the long-term home for names