Skip to content

Smart contract cannot give up Committee update rights, nor receive one #6

@villesundell

Description

@villesundell

Describe the bug
Current code requires authorizations from both, the current owner of Committee update rights, and the receiver of these rights. Although this is a clever way to check the account really exists, it's not feasible with smart contracts, which would need to have rights to each other, since transaction authorizations cannot be forwarded.

Expected behavior
Account currently owning the Committee update rights, should be able to assign any account, including a contract account.

Additional context
The problematic line is here:

require_auth(permission_level{updater_account, updater_auth});

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions