Open Name Tags Destinations

Step 1

Load The Name

Start with the owned name you control. The site will load its current owner and any destinations already published.

Start here

What You Need

The owner private key saved for this name.
The destinations you want apps to use now.
The resolver receives the signed update, not your private key.

Enter an owned name to load its current owner and destinations.

Step 2

Edit Destinations And Sign

Paste the owner private key, update the destination list, and sign the change locally.

After step 1

Use the owner key for this name. This is the control key you saved when you won the auction or received the name, not the Sparrow funding wallet key unless you intentionally made them the same.

Owner Private Key After you load a name, this key will be checked against the current owner.

Destinations

Add the places this name should point right now. Apps can use the entries they understand.

Examples: btc -> bc1qxy...0wlh, lightning -> lno1q...9sa, email -> alice@example.com, website -> alice.example, cashapp -> $alice1234.

Load an owned name, then sign the destination update locally in this browser.

Step 3

Publish The Update

Send the signed update to the resolver. Ownership stays on-chain; the resolver stores the latest owner-authorized destinations.

After step 2

Publishing sends only the signed JSON update. The owner private key never leaves the page.

Sign the update first. Then this step will publish it to the resolver and reload the current destinations.

Reference

Destination guide ONT from zero