Before adoption, a single-time deploy and configuration needs to happen so Sky protocol can safely include changes to the scope within spells. The deployment will happen with the following steps:
-
EOA AgreementV2 deployment
- Anyone can deploy an instance of the
AgreementV2
contract through its factory - Since the initial configuration is too big to safely fit within a spell execution, the first step will be done through an EOA
- Anyone can deploy an instance of the
-
Initial chain configuration
- The EOA will use the reference sheet to create the initial state of the scope
- This includes adding all necessary chains and contracts, as well as the asset recovery addresses
-
Ownership transfer to DSPause
- After the initial setup is done, the EOA will fully transfer the ownership of the
AgreementV2
contract to the PauseProxy - This enables the PauseProxy to modify the scope in the future
- After the initial setup is done, the EOA will fully transfer the ownership of the
-
Adoption
- On a future spell, the pause proxy will call
safeharborRegistry.adoptSafeHarbor(agreementAddress)
- This officially accepts the terms and initiates the validity of SafeHarbor integration
- On a future spell, the pause proxy will call