-
Notifications
You must be signed in to change notification settings - Fork 379
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
r/sys/users
Mainnet v1 (mvp) & v2
#2827
Comments
I would like to give this a shot. Could work well with the teams realm I'm writing now. |
Since I'm not working on the teams realm anymore, I'll withdraw from this for now. |
For V1, the part I'm wondering about is the anti-squatting system managed by a DAO. Do we already have a pkg or an example of a realm that's managed by a DAO, or would the idea be to do it all from scratch? I link the PR: #2963 that could be used to build the dao that manage the users realms |
Also changed the expression to validate board names to check that the name starts with three letters and ends with three numbers. This has been defined this way to match `users` realm implementation. See: gnolang#2827 In a next iteration we can support vanity names for boards, once vanity names are supported for the `users` realm.
Have you started any work on this yet? |
Hello 👋, no i did not |
Updated the OP: -> |
For the launch (or ideally, before), we need to rewrite
r/demo/users
into a better version and rename itr/sys/users
. This issue will outline the MVP requirements and the final vision for the system.MVP / v1
The MVP (v1) implementation will focus on creating a simple username system with the following characteristics:
moul123
.Users must either receive an invite or pay a fee.It may change in the future, but for now, let's assume that the enforced pattern above will be sufficient to make it permissionless.r/demo/users
implementation but with the new constraints, and the system needs to be upgradeable.## Final(?) Vision (v2) Requirementsv2
The final version (v2) will enhance the MVP with advanced features:
The text was updated successfully, but these errors were encountered: