-
Notifications
You must be signed in to change notification settings - Fork 399
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
Making r/users
package grc721
compliant
#297
Comments
We discussed this w/ Jae; in our case, the r/users is not exactly like an ENS, and we want to make it more unique (no way to have multiple ones on an individual address), but we also want to allow transferring it to another account.
Let's keep this discussion open to get more feedback and decide later. FYI, r/users will be a later central point of the governance and will eventually be moved to something like r/system/users. Maybe it makes more sense to split the governance usernames completely from those specialized for NFTs and 2nd market usages. Or perhaps make the grc721 and see how things are going. If we want to make it grc721, we also need to support new features like "selecting the main one" so we can call the realm to get a username from an address and always have the same. |
Thanks for bringing clarity on I saw some of the usage of
You can actually keep an 1-1 relationship and be grc721 compliant, |
Yep, this can be the solution.
And, this can be the other one. I think we'll have both, and maybe the two packages can communicate somehow. Perhaps |
Currently, the realm package
users
associates a user profile to an address, it seems the associated address for a name can no longer be updated after registration.Is there a specific motivation or idea behind this not being possible?
This issue is about implementing the
grc721
interface to make aUser
tokenised and transferable, which would allow:The text was updated successfully, but these errors were encountered: