Preview a change to an approval rule
Check who could approve under a proposed threshold, whether the current rule can authorize the change, and what you need to verify for recovery.
Try a draft rule
The current rule needs two of three keys (A, B and C). Choose which keys belong in the draft and which are available. Each included key can supply one approval. The preview runs in your browser with example keys.
- Current rule
- Draft rule
- Independent recovery
With only A and B available, the current two-of-three rule can be met. Raising it to three leaves the draft one approval short. Replacing B with available D lets A and D meet a two-key draft. Only A and B count toward authorizing that change under the current rule. Verify independent recovery before applying any change.
Compare Safe and Bitcoin
What we tested
. On a local Safe 1.4.1 test account, one approval was blocked. Two authorized the increase to three. A queued request with two approvals then needed a third. On Bitcoin Core 32.1 regtest, changing the threshold or swapping a key derived a new address. The confirmed output stayed at the old address.
Check the change
- Record the current account, rule, eligible keys and outstanding requests. Verify who can authorize the change using the current rule.
- Rehearse the draft on a disposable setup. Check the provider result with enough approvals and with one fewer than required. For rules with weights, roles or separate groups, use a test that covers those conditions.
- Test recovery without the key or person you plan to remove. Confirm fresh access, and verify you can open a harmless item if the setup protects encrypted data.
- Apply the provider’s approved change after the checks pass. Recheck fresh access, queued requests and recovery before retiring the old setup.