Docs

List a name

1. Write the TXT records

The format follows RFC 10023 (_for-sale). On-chain Handshake records can't have subdomains, so they go on the name itself. Each TXT record starts with v=FORSALE1; and carries exactly one tag:

v=FORSALE1;fval=HNS5000
v=FORSALE1;fval=USD120
v=FORSALE1;furi=mailto:me@example.com
v=FORSALE1;ftxt=X @me

A name is listed when it has at least one contact (furi or ftxt), so a single v=FORSALE1;ftxt=X @meis enough (shown as "Make an offer"). It must also be registered, not expired, not revoked and not in the middle of a transfer. A name's whole on-chain resource is limited to 512 bytes, so keep the records short.

2. Publish them with your wallet

An update replaces all of a name's records. Always include the records you already have (NS, DS, GLUE…) alongside the new TXT records, or the name stops resolving.

Bob Wallet: open the name in the Domain Manager, add one TXT record per line above next to your existing records, and submit the update.

hsd: check the current records, then send the full set:

hsd-rpc getnameresource example

hsw-rpc sendupdate example '{"records": [
  {"type": "NS",  "ns": "ns1.example."},
  {"type": "TXT", "txt": ["v=FORSALE1;fval=HNS5000"]},
  {"type": "TXT", "txt": ["v=FORSALE1;ftxt=X @me"]}
]}'

Many names in one transaction. As with sendupdate, include each name's existing records in its list:

hsw-rpc sendbatch '[
  ["UPDATE", "name1", {"records": [{"type": "TXT", "txt": ["v=FORSALE1;fval=HNS5000"]}, {"type": "TXT", "txt": ["v=FORSALE1;ftxt=X @me"]}]}],
  ["UPDATE", "name2", {"records": [{"type": "TXT", "txt": ["v=FORSALE1;fval=HNS900"]}, {"type": "TXT", "txt": ["v=FORSALE1;ftxt=X @me"]}]}]
]'

3. Verify

Wait for one confirmation (about 10 minutes), then click List names, paste your names (up to 100 at a time) and verify. Each name shows whether it was listed or why not.

Contacts

Contacts are shown exactly as written on chain, with known platforms turned into links:

Update or delist

Listings are re-checked against the chain automatically. To apply a change sooner, verify the name again from List names.

• Change price or contact: update the TXT records.
• Delist: remove the v=FORSALE1 TXT records. The listing is removed after a few failed checks.
• After a sale:records survive a transfer, so the new owner should remove or replace them. A listed name stays listed while it is being transferred; other names can't be listed mid-transfer.

Buy and sell safely

A deal for a listed name can close in a single Handshake transaction with Bob Wallet's Finalize With Payment: the buyer pays and receives the name at the same moment, so neither side has to trust the other. No escrow, no fees. The deal page guides both sides and checks each step on chain.

1. Buyer:after agreeing on a price, open the listing's contact button → Buy safely, enter your Bob address and the price, and send the deal link to the seller.
2. Seller:in Bob, transfer the name to the buyer's address. Handshake holds every transfer for about 2 days; the buyer hasn't paid yet and the seller can still cancel.
3. Seller: open the name in Bob → Finalize With Payment, enter the price, paste the result on the deal page and send the payment link to the buyer.
4. Buyer: copy the payment request, then in Bob open Domain Manager → Claim Paid Transfer, paste it, verify and confirm.

A payment request stays valid for about 4 months, or until the seller cancels the transfer. Deal links only carry public data: the name, addresses, price and the seller's signed transaction. Once the payment confirms, the sale is listed on Stats with the name, price and date.

Quality score

Every listing gets a 0–100 quality score, recomputed each time it is verified. Listings scoring below 30 are hidden by default. Anyone can show them with the Show low quality switch, so nothing is removed. The score is a heuristic for ranking and spam filtering, not a valuation.

Boost

A boost moves a listing up the Best ranking for 30 to 180 days: 100 HNS per point for every 30 days, sent from any wallet. Active boosts add up to +10, shown next to the score (e.g. 77⁺⁵). Anyone can boost a listed name. Lookalikes and listings hidden by the quality score can't be boosted: a boost changes the order, not what is shown.

Send the exact amount the boost page shows: its decimals identify the name and the period. Then paste the transaction ID on the page. The boost starts once the payment confirms.

Public API

Read-only JSON over HTTPS. No key needed, and CORS is open, so it can be called from any website, wallet or script. Responses are cached for up to 60 seconds. Each IP can make 120 requests per minute; beyond that the API returns 429.

GET /api/listings

All listings, newest first.

curl https://shakex.fun/api/listings

{ "listings": [ Listing, ... ] }

GET /api/listings/{name}

One listing. Returns 404 with {"error": "Not listed"} if the name isn't for sale, and 400 for an invalid name. Unicode names are accepted and converted to punycode.

curl https://shakex.fun/api/listings/example

Listing object

{
  "name": "example",
  "prices": [
    { "unit": "HNS", "amount": "5000" },
    { "unit": "BTC", "amount": "0.0015" }
  ],
  "contacts": [
    { "type": "uri", "value": "mailto:me@example.com" },
    { "type": "text", "value": "X @me" }
  ],
  "usd": 98.5,
  "score": 67,
  "boost": 0,
  "locked": 1250,
  "createdAt": "2026-09-19T10:00:00.000Z",
  "verifiedAt": "2026-09-19T14:00:00.000Z"
}

The API serves a cache of on-chain data, re-checked regularly. Contact values are written by sellers, so treat them as untrusted input. Always confirm ownership on chain before paying.