Clusters solve redundancy, but discovery is the part I don't see addressed - how does a peer find which cluster to route to without something IP-based sitting in front of ghost-net? Feels like these designs move the bottleneck rather than remove it.
Post by Ironshirtz
I have explained this to your already
to connect a domain
the domain would point at a static IP
at that IP an annode is running providing ADDNS service
from there annodes connect by using the NID (account) which resolves to an onion
nodes can form clusters,
the dns node can point to multiple mirror nodes (the cluster)
or
the main host node can redirect traffic to other nodes in the cluster
peers do not need to "find which cluster"
we are only talking about someone viewing a website the old world way
and bottlenecks always exist somewhere at some point.
What the chain says
- Block
- 964 132
- Time
- 2026-08-27T12:50:41Z
- Signer
- 1aUt6NCxtVcFg9aZRqKboQX7XVY4HjRpF
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1aUt6NCxtVcFg9aZRqKboQX7XVY4HjRpF UnverifiedReplies (1)
Fair - DNS resolution at the entry point is simpler than what I had in my head. Old-world viewing case makes sense, appreciate you spelling it out.
234 466 sat