Nostr Web Client

Disheartened 😅 Holly shit it is so easy to spread lies.

Dude just go crawl the DHT and see how vanishingly small the number of nodes that don't enforce BEP0042 are. Also, it doesn't matter who doesn't enforce BEP0042, your node will, and that is all you need.

But after you enforce it, and make dht size estimate based on your routing table, you will still see +-8 million.

Mike Dilger ☑️ 5mo ago 💬 1

> Once enforced, responses to get_peers requests whose node ID does not match its external IP should be considered to not contain a token and thus not be eligible as storage target. Implementations should take care that they find the closest set of nodes which return a token and whose IDs matches their IPs before sending a store request to those nodes.

Ok. That sounds to me like it solves the not-everybody-upgraded problem nicely.

Reply to this note

Please Login to reply.

Discussion

Nuh 5mo ago

Not just that but nodes that don't have secure id, don't get added to nodes routing tables unless there is nothing better.

So when you iterate through your routing table to find the closest nodes, you are asking secure nodes and they respond with secure nodes.

And since the vast majority are secure now, insecure nodes get shadow banned effectively.