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.

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

Safe
Change the threshold on the existing Safe by executing a transaction authorized under its current owner rule. The address stays the same. Subsequent transactions are checked against the resulting owners and threshold. Review queued proposals and their signatures before the change, then check the Safe address, owner list and threshold after execution.
Bitcoin
For a Bitcoin Core wsh(sortedmulti(…)) wallet, changing the threshold or the keys produces a different receiving script. Existing funds still require the old script’s approvals to spend. On regtest, verify both descriptors and rehearse moving funds from the original address to the new one with the original keys.

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

  1. Record the current account, rule, eligible keys and outstanding requests. Verify who can authorize the change using the current rule.
  2. 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.
  3. 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.
  4. Apply the provider’s approved change after the checks pass. Recheck fresh access, queued requests and recovery before retiring the old setup.