-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add nostr to hs-names #14
Comments
An upcoming soft-fork for the Handshake will lock a subset of this list until hard-fork can occur, but it does not add any new names. Updated subset of this list for the lockup can be found at https://github.com/handshake-org/hs-names-2023/. The soft-fork has already been set in motion and is likely to be activated soon (https://forkwatch.htools.work/). It will only have effect in 2024 February when claims are supposed to expire. Another note: |
Yes, it's a member of the community that got it, for us. We're hoping to do a nostr first solution, and nostr + nomen is a working solution that is starting to gain more traction. So is there a path to getting into the exclusion list for Feb 2024? Or some fork date after that? |
If you already own the name on the network, there's no need to be on any list. If you always renew, it will be there. Reservation list was intended for the CLAIMs on the network and so others could not auction the name. The reservation ends in 2024 February and lockup soft-fork makes sure a subset that has not been claimed can not be auctioned until a hard fork. Adding new names on hard-fork is question I can't answer - as the details of the hard-fork have not been discussed. It is technically possible to add new CLAIM names and IF the name ever expires then it can't be auctioned again, only claimed (it could be locked "forever" with soft-fork). |
Would it be possible to add the nostr protocol to the list of projects working on their own TLD
We have some work in progress in this front:
Nostr is a global network of relays used for discovery and realtime updates. We would like to build out our own SLD using our existing infrastructure.
PR: #13
The text was updated successfully, but these errors were encountered: