Integrate the use of subdomains of ENS(Ethereum Name Service) and text resolvers into WTIndex and Hotel smart contracts, where each hotel and hotel URIs will have their own subdomain ens.
Use cases
Will allow any hotel registered in the WT_INDEX smart contract to have a unique id identifier like hotelname.windingtree.ens, the hotel will have ownership over it.
Access offers and content via ENS, the hotel content can be fetched from the URI stored in content.hotelname.windingtree.ens. This content can be showed in a readable format on the explorer by accessing explorer.windingtree.com/hotelname.
More readable addresses, is much better if I ask for a payment to pay.hotel.windingtree.ens rather than a 40 characters hexadecimal string.
Summary
Integrate the use of subdomains of ENS(Ethereum Name Service) and text resolvers into WTIndex and Hotel smart contracts, where each hotel and hotel URIs will have their own subdomain ens.
Use cases
hotelname.windingtree.ens, the hotel will have ownership over it.content.hotelname.windingtree.ens. This content can be showed in a readable format on the explorer by accessingexplorer.windingtree.com/hotelname.pay.hotel.windingtree.ensrather than a 40 characters hexadecimal string.Mentor
Makoto Inoue: https://github.com/makoto
Resources
wt-contracts: https://github.com/windingtree/wt-contracts/tree/master/contracts ENS: https://ens.domains/ ENS Public Resolver contract: https://github.com/ensdomains/ens/blob/master/contracts/PublicResolver.sol