Bob Wallet Logo
Download

LearnHNS Wallet

LearnHNS Wallet (Chrome Extension)

LearnHNS Wallet is the newer extension line focused on modern Handshake workflows, including DNS record editing for owned names.

Install from Chrome Web Store All Extensions

Important safety note

Do not restore a primary wallet seed into this build. Please test only with a low-risk wallet or account that already owns a low-value name you are comfortable updating.

Who Should Test

  • Someone comfortable loading an unpacked Chrome extension.
  • Someone with a low-risk LearnHNS Wallet setup.
  • Someone who owns a name they can safely update.

What Changed

The Domain page lets you add, edit, remove, and submit DNS records through the Handshake update transaction flow.

DSNSGLUE4GLUE6SYNTH4SYNTH6TXT

What To Avoid

  • Main wallet seeds.
  • High-value names.
  • Wallets holding meaningful balances.
  • Broadcasting unless you understand it is a real on-chain update.

Install

  1. Open the LearnHNS Wallet listing.
  2. Click Add to Chrome.
  3. Pin the extension to your toolbar for easy access.
  4. Open LearnHNS Wallet and start with a low-risk wallet/account while you get comfortable.

Test Flow

  1. Open the extension.
  2. Go to an owned domain.
  3. Find the Root Zone DNS section.
  4. Click Add Record.
  5. Add a simple TXT or NS record.
  6. Click Submit Changes.
  7. Confirm that an update transaction is added to the queue.
  8. Review the queued transaction and verify the records look correct.

Optional deeper tests

  • Edit an existing record.
  • Remove one record while keeping others.
  • Try all supported record types.
  • After a DNS update confirms, open the name through hns.best as a no-install browser check.
  • Cancel before broadcasting if you only want to inspect the queued transaction.

Protocol reminder

Handshake DNS updates replace the full resource payload. Before broadcasting, check that the queued transaction includes the full intended record set, not only the single record you changed.

Restore and Address FAQ

If I restore the same seed in Chrome, should I see the same address?

Usually the first default receive address is deterministic, so the same seed on the same network should be able to derive the same addresses. But the address shown first after restore may not be the exact address you remember if the old wallet generated later receive addresses, used change addresses internally, or used a non-default account.

Do I need to remember the exact address I used before?

You should not need a specific address to recover in principle. The seed phrase is what matters. The wallet may need a rescan or deeper account/address discovery to find all HNS, names, bids, and past activity. An old address is still useful for troubleshooting because it tells support which derivation path or scan range to check.

Why does Bob Wallet show different addresses than the extension?

A seed phrase can generate many addresses. Bob may show current and older receive addresses for the desktop wallet, while the extension may show only its current receive address. Change addresses and non-default accounts can also make two apps look different even when they are derived from the same seed.

What should I do if names or HNS are missing after restore?

First make sure the wallet is on the expected network and has finished syncing or rescanning. Then check whether you used multiple accounts or generated multiple receive addresses in the old extension. Do not assume the seed is wrong just because the first visible address is different.

Never share your seed phrase, private keys, wallet files, or sensitive logs. If support asks for details, share public addresses, screenshots with private data removed, app version, network, and what restore or rescan steps you tried.

What To Report

  • Chrome version and operating system
  • Whether you used an existing extension wallet or a fresh test wallet
  • Whether your name had no records, one record, or multiple existing records
  • Which record type you tested
  • Whether transaction creation succeeded
  • Whether the queued confirmation showed the full intended record list
  • Any visible UI errors or confusing steps
  • Whether you broadcasted or stopped at queue/confirmation

Screenshots are useful, especially the domain page before editing, the editor before submit, the queued confirmation, and any error message. Never share seed phrases, private keys, wallet files, or sensitive logs.