Closed jcps07 closed 1 year ago
DCL P_P_G: "Every role SHALL be associated with a separate key such that no single key will have multiple roles."
From description, current implementation supports multiple roles for an account (key): dcld tx auth propose-add-account --address=<bench32 encoded string> --pubkey=<protobuf JSON encoded> --roles=<role1,role2,...> --vid=<uint16> --from=<account>
dcld tx auth propose-add-account --address=<bench32 encoded string> --pubkey=<protobuf JSON encoded> --roles=<role1,role2,...> --vid=<uint16> --from=<account>
Removed from v1.3. DCL-TT: The dcl software allows it but it's being monitored by Alliance Trustee prior proposing. If the policy changes in the future, no need to update the code.
DCL P_P_G: "Every role SHALL be associated with a separate key such that no single key will have multiple roles."
From description, current implementation supports multiple roles for an account (key):
dcld tx auth propose-add-account --address=<bench32 encoded string> --pubkey=<protobuf JSON encoded> --roles=<role1,role2,...> --vid=<uint16> --from=<account>