Skip to content
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

Open
moul opened this issue Sep 21, 2024 · 3 comments
Open

r/sys/users Mainnet v1 (mvp) & v2 #2827

moul opened this issue Sep 21, 2024 · 3 comments

Comments

@moul
Copy link
Member

moul commented Sep 21, 2024

For the launch (or ideally, before), we need to rewrite r/demo/users into a better version and rename it r/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:

  • Usernames must be unique.
  • Usernames should start with three letters.
  • Usernames should end with three numbers.
  • Example: moul123.
  • A simple anti-squatting mechanism will be implemented, such as a DAO-managed blacklist of keywords, or a better option if available.
  • Users must either receive an invite or pay a fee.
  • Usernames will not be transferable at this stage.
  • Implementation Details: The MVP should resemble the current r/demo/users implementation but with the new constraints, and the system needs to be upgradeable.## Final(?) Vision (v2) Requirements

v2

The final version (v2) will enhance the MVP with advanced features:

  • Vanity Usernames: Users can register vanity usernames without the limitation of numbers. If a user already has a free username, they can retain it and add a vanity username, though several factors need consideration.
  • Advanced Anti-Squatting System: We will integrate a robust anti-squatting mechanism. -> Anti-squatting System for gno.land namespaces #2727
  • Auction System: An auction system will be implemented in conjunction with the anti-squatting system.
  • Dual Username Considerations: We need to define how to handle previous accounts, specifically whether to prevent their use.
sequenceDiagram
    participant Alice
    participant r/users
    Alice->>r/g1234567/foo: addpkg
    Alice->>r/users: RegisterV1("alice123")
    Alice->>r/alice123/foo: addpkg
    Alice->>r/users: RegisterV2Vanity("alice")
    Alice->>r/alice/foo: addpkg
Loading
@irreverentsimplicity
Copy link
Contributor

I would like to give this a shot. Could work well with the teams realm I'm writing now.

@irreverentsimplicity
Copy link
Contributor

Since I'm not working on the teams realm anymore, I'll withdraw from this for now.

@MikaelVallenet
Copy link
Contributor

MikaelVallenet commented Oct 25, 2024

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?
If it's from scratch, would it be better to develop a “dao manager/maker/factory/builder” pkg first, before tackling the new r/sys/users that would need it?

I link the PR: #2963 that could be used to build the dao that manage the users realms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🎯 Current Topics
Development

No branches or pull requests

4 participants