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

allow resource creator to restrict resource actions to a component without requiring their signature in each transaction #1145

Open
sdbondi opened this issue Sep 17, 2024 · 0 comments
Milestone

Comments

@sdbondi
Copy link
Member

sdbondi commented Sep 17, 2024

Problem

Various resource actions may need to be performed by a large group or everyone in a pre-defined/controlled way. Using badges in this case is unwieldy and also does not prevent another template/component from executing those actions.

Proposal 1

Add a restriction where only the owning component is authorised to perform resource actions.

ResourceBuilder::fungible()
  .locked_to_component(component_addr)

Hooking this idea into the access rules may be more elegant and allow fine-grained control. However, if this is impractical the above method is acceptable as that should cover the majority of use cases.

ResourceBuilder::fungible()
.mintable(rules![locked_to_component(component_addr))])
@sdbondi sdbondi added this to the v0.0.1 milestone Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant