Bob Wallet Logo

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.

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.
  • 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.

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.