Commit 0cd44702 authored by Maurelian's avatar Maurelian

specs: Define deployment order for liveness contracts

parent 57cfa4d3
...@@ -106,8 +106,8 @@ contract LivenessModule_TestInit is Test, SafeTestTools { ...@@ -106,8 +106,8 @@ contract LivenessModule_TestInit is Test, SafeTestTools {
_minOwners: minOwners, _minOwners: minOwners,
_fallbackOwner: fallbackOwner _fallbackOwner: fallbackOwner
}); });
safeInstance.enableModule(address(livenessModule));
safeInstance.setGuard(address(livenessGuard)); safeInstance.setGuard(address(livenessGuard));
safeInstance.enableModule(address(livenessModule));
} }
} }
......
...@@ -86,3 +86,14 @@ The following security properties must be upheld: ...@@ -86,3 +86,14 @@ The following security properties must be upheld:
5. The module implements the correct checks prior to removing a signer. 5. The module implements the correct checks prior to removing a signer.
6. The module sets the correct threshold upon removing a signer. 6. The module sets the correct threshold upon removing a signer.
7. During a shutdown the module correctly removes all signers, and converts the safe to a 1 of 1. 7. During a shutdown the module correctly removes all signers, and converts the safe to a 1 of 1.
### Deployment
The module are guard are intended to be deployed and installed on the safe in the following sequence:
1. Deploy the guard contract, this will set a timestamp for each existing owner on the Safe.
1. Deploy the module.
1. Enable the module on the safe.
1. Set the guard on the safe.
This order of operations is necessary to satisfy the constructor checks in the module, and is
intended to prevent owners from being immediately removable.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment