-
Notifications
You must be signed in to change notification settings - Fork 20
Description
I figured I would make this a Github Issue to track progress and so its not only something we write about on TG.
As the Lamden Name Service is actually a big success in terms of usage I see a need to further improve it.
According to the NFT Marketplace Stats - https://taurusnft.art/stats.html
We already have 6364 Names minted at 1 TAU each and resales at 200+ TAU by different people. The most successful NFT collection on Lamden yet.
The first goal of it is pretty simple, use it as an Alias for your Lamden Wallet. As the Holder of a name it is already somewhat connected to your address.
https://blockservice.opticprotocol.finance/current/all/con_nameservice_v3/collection_balances
The idea I have in mind for Lamden Wallet is

The click on next would simply send it to the matching address.
Pretty simple right?
You can either use my already existing api to get the result:
https://lns.reflecttau.io/resolve/stu.tau (append the .tau when you are doing a request to api from wallet)
or use this code as a starting point to resolve it yourself:
https://github.com/crosschainer/Lamden-Name-Service/blob/main/resolver.py