This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AP-698 Core contracts deployed to Polygon (mainnet)
Multisig configs
Protocol-Level Fees (in bps):
|
stevieraykatz
changed the title
AP-698 mainnet readiness
[WIP] AP-698 mainnet readiness
Aug 24, 2023
stevieraykatz
commented
Aug 24, 2023
stevieraykatz
commented
Aug 24, 2023
0xNeshi
suggested changes
Aug 25, 2023
…ions optional signers
SovereignAndrey
changed the title
[WIP] AP-698 mainnet readiness
[WIP] AP-724 mainnet readiness
Aug 26, 2023
stevieraykatz
changed the title
[WIP] AP-724 mainnet readiness
AP-724 mainnet readiness
Aug 26, 2023
AP-698 Core contracts deployed to Polygon (mainnet)
Registrar configs
Multisig configs
Protocol-Level Fees (in bps):
|
0xNeshi
suggested changes
Aug 29, 2023
0xNeshi
reviewed
Aug 30, 2023
* FYEO-ANGL-ID-29: MISSING ZERO ADDRESS CHECKS * validator used in core contracts * add more checks w/ Validator; Fix validator imports; --------- Co-authored-by: Andrey <SovereignAndrey>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: https://linear.app/angel-protocol/issue/AP-698/core-contracts-deployed-to-polygon-mainnet
Explanation of the solution
At some point we started deploying contracts with
proxyAdmin
signer instead ofdeployer
. This PR changes the deployer back todeployer
signer.In prod, we don't want the
proxyAdmin
to be an EOA wallet but instead to be a multisig. If we use a multisig that is a proxy for this proxyAdmin ms, then it needs a proxy admin and we get into a weird "who watches the watcher" situation. The solution I've employed is to deploy an immutable proxyAdmin multisig which largely resembles theGenericMultisig
we use extensively in our protocol sans the upgrade path. In the rare event that we need to update the implementation of our ProxyAdmin wallet, we can deploy a new immutable multisig and then transfer proxy admin from the old admin ms to the new one.In a lot of cases, our deployment scripts did an implicit lookup for the old proxyAdmin signer and then passed the signer's address into the proxy admin arg for proxy initialization. I've added an argument to these scripts so that the admin address must be specified explicitly.
Instructions on making this work
yarn
oryarn install
to install npm dependencies