Coming soon. Quorum policies shape below may change before release.
allow or deny. Quorum policies add a third outcome: require approval. Instead of blocking an action outright, you can require that other members sign off before it proceeds.
Quorum uses the same requireApprovals block everywhere. Set how many approvals are needed and which roles can approve.
Wallet actions
AttachrequireApprovals to a rule on any layer you already use. It composes with the other rule fields, so a threshold and an approval requirement can be one rule:
A Signer-Layer requirement is the way to give one member more oversight than another. Layers cannot exempt anyone: a Signer-Layer can raise a requirement above the Account-Layer, but it can never lower it.
You can attach
requireApprovals to a rule that has no other restrictions if the only requirement is approvals.Account actions
AttachrequireApprovals to the business account, keyed by the action it governs:
How approvals work
The flow is the same for wallet and account actions.- A member takes an action as they do today (no new call).
- If a requirement applies, the action returns a proposal instead of completing, and eligible approvers are notified.
- Each approver reviews the proposal and approves it. Approvals are signed by the approver, so they cannot be forged or reassigned to a different action.
- Once enough approvals are collected, the action completes.
A member cannot approve their own proposal, and each member can approve a proposal once.
The final flow may complete automatically when the last approval is received, or it may require an explicit
executeProposal call. The example above shows the explicit version.What can require approval
Quorum applies to business accounts only. A personal wallet has no second member to approve.