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

[REQUEST] MIT domain certificates #365

Open
canguruhh opened this issue Jan 10, 2020 · 2 comments
Open

[REQUEST] MIT domain certificates #365

canguruhh opened this issue Jan 10, 2020 · 2 comments

Comments

@canguruhh
Copy link
Member

When creating a MST the user can get a domain certificate that restricts the creation of other MSTs that use the same domain prefix. The domain certificate MVS for example restricts the creation of MST symbols that start with MVS. for example MVS.ABC

For MITs we currently don't have certificates. Instead of creating new certificate types we can reuse the MST domain certificates for this purpose.

Change the rules of the mvsd transaction validation to restrict the creation of MIT.

  1. If a user creates a MIT for which symbol there is no existing domain certificates it should be allowed like it is today.
  2. If there is a domain certificate that matches the prefix of the MIT symbol then this domain certificate must be added as in and output of the transaction.
  3. Other MST certificates should not restrict MIT creation (name certificates).

The mvsd command registermit must be adjusted to automatically check if the user has access to the required domain certificate and add it to the transaction. This is the same behaviour as the MST issuance.

@baidang201
Copy link
Contributor

@baidang201
Copy link
Contributor

MIT domain certificates is work in prive chain now,
https://github.com/baidang201/metaverse/tree/365-mit-domain-cert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants