Resolve Handshake SLDs trustlessly.
npm install aliasingResolve Handshake SLDs trustlessly.
Install hipr, then run
``
hipr install hipr-aliasing
to install the aliasing middleware, and spin up your hipr server (assuming you have an hsd root resolver on port 5349):
hipr hipr-aliasing :5333 :5349
To test if it's working, try running dig @127.0.0.1 -p 5333 luke.dsub +short. you should get 66.42.108.201.
If a Handshake TLD _{tld}_ sets a HIP-5 NS record "_{hip5data}_._aliasing", then any HIP-5 extension implementing the aliasing protocol must:
1. For any SLD _{label}.{tld}_, compute the _{alias}_: the base32 encoding of the blake3 hash of _{label}_ concatenated (as strings) with the _first_ label of _{hip5data}_ (line 24).
2. Forward the original DNS query for _{label}.{tld}_ to _{alias}_ (line 30) after substituting _{label}.{tld}_ for _{alias}_ (line 25), then return the response after substituting _{alias}_ for _{label}.{tld}_ (lines 34-41)
A TLD owner wishing to open their TLD for SLD registration should set a single HIP-5 NS record as above with a unique public key as hip5 data, then set their TLD to renew-only. They can use the public key to prove that they originally owned the TLD.
A HIP-5 extension supporting the aliasing protocol might also resolve top-level records for the TLD using the public key as a decentralized zone address, as we do in the experimental implementation discussed below. If it does, it must specify the distributed zone protocol that it is using as a sublabel, such as: {public-key}._hyper._aliasing`. For this reason, only the first label of _{hip5data}_ should be used to compute _{alias}_.