To which forum to I post this idea to Proposal : Use Handshake (HNS) Web 3 domain services as a decentralised alias/attestation layer for Tor onion identities. like say gerry.g3wip .onion is noy Web3. The Web3 name is just a signed pointer to the onion identity. Making .onion a Handshake TLD. That would indeed clash conceptually, because .onion is a special-use ICANN/IETF-reserved name. Use Handshake as a decentralised alias/attestation layer for Tor onion identities. Something like: gerry.g3wip TXT/DS-style record says: onion=jee3z7cpmfhcc62hhs33utyovghbyr3hlhumxwkr2zoo5mzskz5cvhqd.onion proof=signature from onion service key Then a resolver/browser/plugin can verify: 1. gerry.g3wip is owned via Handshake. 2. The record points to a long onion. 3. The onion service proves "yes, I authorised this alias". 4. User gets taken to the onion, without trusting a central shortener. I'm not proposing .onion as a Handshake namespace. I'm proposing a decentralised naming/attestation layer where a Handshake name can publish and cryptographically verify a mapping to a Tor v3 onion service, similar to how DNS can advertise service endpoints, but without replacing Tor's self-authenticating onion address. Gerry Bulger