-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement: Lamden Name Service #269
Comments
Additionally it would be good if the nameservice contract can be changed in Lamden Wallet Settings, like you can edit the networks you are connected to. |
@Dapiguabc add this to your list for a release after the Node Admin dashboard 👍 |
@crosschainer Thks for your advice ! I have a question. Whether the domain name is case-sensitive? |
@Dapiguabc its all lowercase always |
also "con_...." is not allowed since only alphanumeric charcters allowed |
@JeffWScott I've added this feature to wallet. I think we should offer official name resolver service for wallet and then I can push this update. |
Can you add an endpoint to the blockservice to resolve names? I don't want to have to run more things |
okay~
|
Bump) |
@crosschainer @cross_chain1 Allen’s priorities are to get the node dashboard out for Mainnet release. That’s a large task so this endpoint down the list. |
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
![Bildschirmfoto 2022-11-12 um 09 32 51](https://user-images.githubusercontent.com/68580992/201466016-d59a4f02-2e81-4b99-bd05-38596aa3906f.png)
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
The text was updated successfully, but these errors were encountered: