Multi-party Agreements
Status: conceptual, last checked 2026-11-02. The approval model is not final or implemented.
A company requires two of three directors to approve any supplier payment over 10,000 USDC.
The pattern
- Define roles and a threshold in a policy, and give that policy a version.
- Propose the action. A signed proposal references the exact terms and the policy version. One signature here means a proposal, not agreement.
- Collect approvals. Each approver signs those same terms. An approval to different terms doesn’t count.
- Verify the threshold independently: distinct signers, each authorized under that policy version and unexpired.
- Execute only once the threshold is met, with evidence of who approved.
Edge cases to decide up front
| Case | Rule to state explicitly |
|---|---|
| Terms change after one approval | Earlier approvals become invalid |
| A signer is removed during approval | Decide whether their earlier signature still counts |
| Delegation | Delegated authority has its own scope and expiry, and can’t exceed the delegator’s |
| Policy update | Goes through the current policy’s own threshold |
| Revocation after execution | Can’t undo execution, and only blocks future actions |
A signed agreement may or may not be legally enforceable. Check with counsel for your jurisdiction.
Explore invoicing: Programmable Invoicing
Last updated on