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.
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: https://github.com/telosnetwork/telos-decide/blob/b17261e830d2549dfc54e0f9a0e5eb357e5c8a95/contracts/decide/src/committee.cpp#L117