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

Decentralised Directory (DeDir): Requirements/Features #503

Closed
10 of 12 tasks
vatsa287 opened this issue Aug 23, 2024 · 2 comments · Fixed by #559
Closed
10 of 12 tasks

Decentralised Directory (DeDir): Requirements/Features #503

vatsa287 opened this issue Aug 23, 2024 · 2 comments · Fixed by #559
Assignees
Labels
enhancement New feature or request next-release

Comments

@vatsa287
Copy link
Member

vatsa287 commented Aug 23, 2024

Current implementation of DeDir #502 is based on a blob based and there also exists a discarded attributes based model. #495

Supported Dispatchable Functions:

  • create_registry - Create a registry, with digest, blob.
  • create_registry_entry - Create a registry entry for the created registry.
  • registry_entry_state_change - Change the status of the registry entry.
  • add_delegate - Add a account as a delegate with specific permission.
  • remove_delegate - Add a existing account from authorised delegates list.
  • update_delegate_permission - Update the permission of an existing delegate.

Features:

  • Blob based data model.
  • Delegates Management.
  • Identifier Management from SDK.
  • Selective Data Attributes for selective provable access. (TODO).

Unit Tests:

  • Successful scenarios of all dispatch able extrinsics.
  • Failure test cases ( check for errors defined in enum Errors would suffice). (TODO)
@amarts
Copy link
Member

amarts commented Dec 13, 2024

@vatsa287 thinking more about current version... can we not have 'registry_id' as part of create? let it be always be created in create() method.

@vatsa287
Copy link
Member Author

@vatsa287 thinking more about current version... can we not have 'registry_id' as part of create? let it be always be created in create() method.

It can be removed. Currently it's more of a dummy argument, the identifier creation logic is part of create() itself.

I think it was added on thoughts of having the identifier creation on application side.

Will send a PR for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request next-release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants