Rendezvous Server Address
/onion3/loafcihytcg5hhgmreeupx2buxq4fkouyrkbmxiwpegpfxcpl4emgmid:8888/p2p/12D3KooWPUXnQPH5MqKgig9q5qDhVZeyBJFXfTLmVrhX8ASSE2EG
Who is running the server?
duskswap (same operator as swap.0xhaha.com / rendezvous.duskswap.com). We run an ASB and hit the same "why are we never listed" question as #1199, so we tested all 4 current defaults directly (REGISTER vs. DISCOVER separately, not just "no errors"): discovery.eigenwallet.org and dht.stealthswap.ninja both REGISTER fine but their DISCOVER path fails on both wss and onion — matches what's already reported in #1163. Only the PR #1152 onion reliably served both for us.
So we stood up a dedicated box running this repo's own rendezvous-node binary (nothing custom), single-purpose, no other services on it, and verified end-to-end ourselves before submitting: our ASB's own client log shows the affirmative Registered with rendezvous node line against this peer, the server logs a matching Peer registered for our ASB's peer ID, and a separate throwaway libp2p client (not our ASB, not this node) issued a real DISCOVER query against it and got our ASB's peer ID + onion address back. So both directions are proven, not just "seems up."
We intend to run this long-term, same spirit as PR #1152. Currently onion-only (this binary's WS transport has a listener bug we ran into and filed a note about on #1163 — happy to submit a fix for that separately if useful) — direct clearnet TCP also up at /ip4/2.29.57.218/tcp/8888/p2p/12D3KooWPUXnQPH5MqKgig9q5qDhVZeyBJFXfTLmVrhX8ASSE2EG if that's wanted alongside the onion.
Claude Code assisted with drafting this and running the verification steps described; the server, the testing and the decision to submit are ours.
Rendezvous Server Address
Who is running the server?
duskswap (same operator as swap.0xhaha.com / rendezvous.duskswap.com). We run an ASB and hit the same "why are we never listed" question as #1199, so we tested all 4 current defaults directly (REGISTER vs. DISCOVER separately, not just "no errors"):
discovery.eigenwallet.organddht.stealthswap.ninjaboth REGISTER fine but their DISCOVER path fails on both wss and onion — matches what's already reported in #1163. Only the PR #1152 onion reliably served both for us.So we stood up a dedicated box running this repo's own
rendezvous-nodebinary (nothing custom), single-purpose, no other services on it, and verified end-to-end ourselves before submitting: our ASB's own client log shows the affirmativeRegistered with rendezvous nodeline against this peer, the server logs a matchingPeer registeredfor our ASB's peer ID, and a separate throwaway libp2p client (not our ASB, not this node) issued a real DISCOVER query against it and got our ASB's peer ID + onion address back. So both directions are proven, not just "seems up."We intend to run this long-term, same spirit as PR #1152. Currently onion-only (this binary's WS transport has a listener bug we ran into and filed a note about on #1163 — happy to submit a fix for that separately if useful) — direct clearnet TCP also up at
/ip4/2.29.57.218/tcp/8888/p2p/12D3KooWPUXnQPH5MqKgig9q5qDhVZeyBJFXfTLmVrhX8ASSE2EGif that's wanted alongside the onion.Claude Code assisted with drafting this and running the verification steps described; the server, the testing and the decision to submit are ours.