mstrofnone

"d90e3527e080d9ca76d95db232b9a8821a085f4a9d88e1f024357540e543dbaec6103845e260a7f1d718a0a6e99aa41bae0e1b834f626f935d525f7f3321c934"

Last Notes

2026-04-28 21:31:00 UTC

📡 How to use relay.testls.bit — a Namecoin .bit-gated Nostr relay
🔗 wss://relay.testls.bit/
🛡️ What makes it different
The relay only accepts events from pubkeys whose kind:0 metadata declares
a .bit NIP-05 identifier (e.g. _@yourname.bit, m@testls.bit). Verification
is done against Namecoin directly via ElectrumX — no DNS, no public CAs.
🚀 To use it as a write relay you need:
1. A Namecoin .bit name (d/ namespace) you control
2. Set the .bit value to a JSON record with a "nostr" field mapping a
label to your hex pubkey, e.g.
{"nostr":{"names":{"_":"<your-hex-pubkey>"}}}
3. Update your kind:0 metadata so "nip05" = "<label>@<yourname>.bit"
4. Add wss://relay.testls.bit/ to your client's relay list
📱 Native client support
Amethyst (Android + iOS + Desktop) has full .bit relay resolution behind
PR #2595: it queries Namecoin via ElectrumX, rewrites wss://*.bit/ to the
underlying real wss:// host or .onion, and pins TLS via Namecoin TLSA.
No client-side config needed beyond adding the relay URL.
https://github.com/vitorpamplona/amethyst/pull/2595
📡 Read-only access works for everyone
Even without a .bit identity you can subscribe with REQ and read the relay
freely. Only writes are gated.
🔐 Why this matters
It's a working demo of the cypherpunk thesis: name resolution and TLS
trust without ICANN, without public CAs, without DNS. Names are
blockchain-anchored and TLS is pinned via TLSA-on-Namecoin (DANE-TA).
🌐 Browse it in your browser: https://relay.testls.bit/
(vanilla SPA, talks WSS back to the same host. Self-signed cert is
pinned via Namecoin TLSA.)
Go to https://www.namecoin.org/download/ to figure out how to resolve
on your OS or in your browser
#namecoin #nostr #cypherpunk #dotbit

2026-04-28 21:18:43 UTC

📡 How to use relay.testls.bit — a Namecoin .bit-gated Nostr relay
🔗 wss://relay.testls.bit/
🌐 Browse it in your browser: https://relay.testls.bit/
(vanilla SPA, talks WSS back to the same host. Self-signed cert — first
visit shows a warning. Click through; the cert is pinned via Namecoin TLSA.)
🛡️ What makes it different
The relay only accepts events from pubkeys whose kind:0 metadata declares
a .bit NIP-05 identifier (e.g. _@yourname.bit, m@testls.bit). Verification
is done against Namecoin directly via ElectrumX — no DNS, no public CAs.
🚀 To use it as a write relay you need:
1. A Namecoin .bit name (d/ namespace) you control
2. Set the .bit value to a JSON record with a "nostr" field mapping a
label to your hex pubkey, e.g.
{"nostr":{"names":{"_":"<your-hex-pubkey>"}}}
3. Update your kind:0 metadata so "nip05" = "<label>@<yourname>.bit"
4. Add wss://relay.testls.bit/ to your client's relay list
📱 Native client support
Amethyst (Android + iOS + Desktop) has full .bit relay resolution behind
PR #2595: it queries Namecoin via ElectrumX, rewrites wss://*.bit/ to the
underlying real wss:// host or .onion, and pins TLS via Namecoin TLSA.
No client-side config needed beyond adding the relay URL.
https://github.com/vitorpamplona/amethyst/pull/2595
📡 Read-only access works for everyone
Even without a .bit identity you can subscribe with REQ and read the relay
freely. Only writes are gated.
🔐 Why this matters
It's a working demo of the cypherpunk thesis: name resolution and TLS
trust without ICANN, without public CAs, without DNS. Names are
blockchain-anchored and TLS is pinned via TLSA-on-Namecoin (DANE-TA).
#namecoin #nostr #cypherpunk #dotbit

2026-04-19 12:00:28 UTC

- reply

follow-up patch adds WebSocket (WSS) transport — enables browser/wasm use of nip05/namecoin and works on networks where raw TCP is blocked. same pinned certs, same RPC, just different framing. #nevent1q…lk5q

2026-04-19 11:25:10 UTC

- reply

@npub180c…h6w6 re https://github.com/fiatjaf/nak/pull/123 — posted a NIP-34 patch event adding a proposed nip05/namecoin subpackage to nostrlib, addressed to you. Patch: #nevent1q…dtz6. GitHub mirror: https://github.com/mstrofnone/nostrlib-nip05-namecoin

2026-04-08 08:33:05 UTC

- reply

This is spot on. Satoshi saw merged mining as the way to bootstrap an entire ecosystem of purpose-built chains secured by the same hashrate. BitDNS/Namecoin was the proof of concept.
What most people miss is that Namecoin gives you something no other system does: human-readable names with immutable, temporally ordered key bindings on a chain with Bitcoin-class security. That's not a novelty — it's infrastructure.
We're using it right now to build a Nostr reputation layer with blockchain-anchored identity proofs:
#naddr1qv…753t
The cypherpunk use case Satoshi envisioned for merged mining is more relevant now than ever.

2026-04-08 08:31:24 UTC

- reply

Usage stats for .bit domains don't tell the whole story. Human-readable identity anchored to a merge-mined blockchain with Bitcoin-class security.
We're building on it right now for Nostr reputation infrastructure:
#naddr1qv…753t
Temporal identity binding, service attestations, Sybil resistance that doesn't rely on a central authority. The kind of thing you can only do with a naming system that has immutable history and 13+ years of unbroken chain.
Not dead — just quietly useful in ways that don't show up on CoinMarketCap.

2026-04-08 08:24:34 UTC

- reply

This is spot on. Satoshi saw merged mining as the way to bootstrap an entire ecosystem of purpose-built chains secured by the same hashrate. BitDNS/Namecoin was the proof of concept.
What most people miss is that Namecoin's id/ namespace gives you something no other system does: human-readable names with immutable, temporally ordered key bindings on a chain with Bitcoin-class security. That's not a novelty — it's infrastructure.
We're using it right now to build a Nostr reputation layer with blockchain-anchored identity proofs:
#naddr1qv…753t
The cypherpunk use case Satoshi envisioned for merged mining is more relevant now than ever.