feat(namecoin): resolve .bit NIP-05 identifiers via Namecoin ElectrumX

[mstrofnone]

Summary

Adds optional Namecoin .bit verification: NIP-05 addresses ending in .bit (and the d/<name> / id/<name> shorthands) are resolved over the Namecoin blockchain instead of HTTPS, giving users a DNS-free alternative for identity verification. Everything else still flows through nostr-tools exactly as today.

Why

.bit is a censorship-resistant naming layer (Namecoin, since 2011). For a calm reader-oriented client like nostter, this lands as a one-line suffix check in the existing NIP-05 path — no new UI noise, no new badges, no new top-level components. The existing verified checkmark either lights up for a .bit address or it doesn't, same as for a .com address.

Scope

• One module: src/lib/namecoin/ (cache + WSS ElectrumX client + ifa-0001 value parser + tests).
• One hook: src/lib/Nip05.ts wraps nostr-tools queryProfile. .bit shapes route to the Namecoin resolver; everything else falls through unchanged.
• Two existing call sites updated to use the wrapper (NostrAddress.svelte and the [slug=npub] slug-overwrite path).
• No new top-level UI elements.
• Falls back silently on resolver failure (transport error, missing nostr field, expired name).

Wire format

Same wire format used in Amethyst (Kotlin), Nostur (Swift), dart-nostr (merged), and the in-review PRs against nostrudel, jumble, and nostr-tools:

• d/<domain> records: read nostr.names[<local-part>] (with _ as the root entry), with optional nostr.relays map keyed by pubkey.
• id/<name> records: read nostr.pubkey plus optional flat nostr.relays array.
• Shorthand "nostr": "<hex>" accepted as the root entry of a d/ record.

See the N1 NIP draft for the formal definition.

Try it

• _@mstrofnone.bit resolves to the same pubkey as the existing mstrofnone npub on the Namecoin chain.
• mstrofnone.bit (the bare shorthand) does the same.

Footprint

+1012 / -8 across 10 files (most of that is the WSS client + tests). The two existing Svelte components each get a 2-line import-swap; everything else is new code under src/lib/namecoin/.

Tests & checks

• 21 new vitest tests for the parser + mock-socket resolver path.
• Full suite: 103/103 pass.
• Prettier + ESLint clean for new files.
• svelte-check: zero regressions (11 pre-existing errors, same count before and after; none introduced by this change).

Server pool note

The shipped default list is the 4-of-6 browser-WSS subset of Amethyst's DEFAULT_ELECTRUMX_SERVERS. Two of Amethyst's entries are bare IPs that browsers refuse over WSS (no IP-SAN cert), so they're deliberately omitted here. This is documented inline in electrumx.ts. Of the four shipped servers, electrum.nmc.ethicnology.com is the most browser-friendly today (Let's Encrypt-fronted); the other three serve self-signed certs and will only succeed once the user has TOFU-trusted them. The calm-failure UX means this is fine: .bit verification is optional, and if every server fails the checkmark just stays dark.

[mstrofnone]

Cross-posted as a kind:30023 long-form note: https://njump.me/naddr1qvzqqqr4gupzqscctm0vke6cj2pykx3h54lnusrlhh3wmfeqrguznwx0fwnutd8sqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqz9mhwden5te0wfjkccte9e6x2um5d3ejucnfwshsq8twd9c8xttwv9kk2cm0d9hz6mn0wd68getj94c8ytfjxyersjj3d9a

[SnowCait]

I know nothing about Namecoin, so I cannot judge whether I should implement a specification that does not exist in NIP-05. Also, I cannot verify your code.
I am very sorry, but I will have to reconsider this after it has been merged into the NIPs and reflected in nostr-tools.

[mstrofnone]

sure @SnowCait that seems very reasonable