Avatar
Yuval Adam ⚡️
2719dfdd5cec684fe518b1d1e85ddd682787964cfa68ae9b90a18df19285dd3c

I ran into some difficulties. I set it up but for some reason it doesn't seem to be considered valid... Can't figure out what's wrong:

https://n.btcbb.me/.well-known/nostr.json set up with:

{ "names": { "bitcoinbellybutton": "npub1nemykkw0jtwaf4038vpcfv4g22r2qnfm66tsu90gjsjf68skphuqv6h5rp" } }

Any suggestions?

yep, you used your npub instead of hex format

Replying to Avatar ⚡️🌱🌙

One of the biggest weaknesses of nostr is its reliance on local DNS servers typically residing at 8.8.8.8 or 8.8.4.4 as setup by ISP’s.

Essentially this gives every governments a single point failure within their jurisdiction with which to take nostr offline relays offline. If they desired.

However, the Authoritative DNS servers that serve the DNS root zone are visible on the network and their addresses are in the public domain. They are configured in the DNS root zone as 13 named authorities, as follows.

a.root-servers.net

198.41.0.4, 2001:503:ba3e::2:30

Verisign, Inc.

b.root-servers.net

199.9.14.201, 2001:500:200::b

University of Southern California,

Information Sciences Institute

c.root-servers.net

192.33.4.12, 2001:500:2::c

Cogent Communications

d.root-servers.net

199.7.91.13, 2001:500:2d::d

University of Maryland

e.root-servers.net

192.203.230.10, 2001:500:a8::e

NASA (Ames Research Center)

f.root-servers.net

192.5.5.241, 2001:500:2f::f

Internet Systems Consortium, Inc.

g.root-servers.net

192.112.36.4, 2001:500:12::d0d

US Department of Defense (NIC)

h.root-servers.net

198.97.190.53, 2001:500:1::53

US Army (Research Lab)

i.root-servers.net

192.36.148.17, 2001:7fe::53

Netnod

j.root-servers.net

192.58.128.30, 2001:503:c27::2:30

Verisign, Inc.

k.root-servers.net

193.0.14.129, 2001:7fd::1

RIPE NCC

l.root-servers.net

199.7.83.42, 2001:500:9f::42

ICANN

m.root-servers.net

202.12.27.33, 2001:dc3::35

WIDE Project

It is possible to bypass the local dns server / recurser and go straight to DNS root in order to get the IP addresses for relays. This would make nostr even more censorship resistant, but would slow things down. Maybe this could be an anti-censor mode that clients could attempt if clients detect all relays are unreachable or if some kind of DNS error is returned?

Also… Anycast should be implemented for reads instead of unicasting. This could massively improve performance by reducing network traffic and relay load when it comes to reads. Relay proxies as proposed by Cameri would allow anycast reads and would vastly reduce the bandwidth requirements of nostr and dramatically reduce the load on each relay.

Unicasting and data duplication should be maintained for writes, with anycast proxies serving reads.

Anycast proxy relays could potentially allow a client to access a vastly greater number of relays and also improve the access surface making nostr more resilient to DDOS.

If you are assuming nation state censorship, you can't stop at DNS, IP traffic can just as easily be blocked. In such a threat model you need a Tor-like solution e.g. custom bridges with pluggable transports.

More of a faux pas than anything else, not in the spirit of the protocol. Also can't advertise relays, but I guess you can add support for that in the future

The downside of using hosted NIP-05 verification services like nostrverified and nostr-check is that they dump literally all their users in nostr.json - not great not terrible. Self host your own nostr.json, it's really not that hard.

Sooner or later this is bound to happen. L1 will eventually be too expensive for that usage. Adopt LN.

Weird I only see nsec*******

Added main relay recommendations on my NIP-05 JSON

Setting up my personal relay on wss://nostr.yuv.al 🔥