-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy CacheManager to L2 and L3 #65
Conversation
@@ -378,7 +378,7 @@ function writeL3ChainConfig(argv: any) { | |||
"AllowDebugPrecompiles": true, | |||
"DataAvailabilityCommittee": false, | |||
"InitialArbOSVersion": 30, | |||
"InitialChainOwner": "0x0000000000000000000000000000000000000000", | |||
"InitialChainOwner": argv.l2owner, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wonder if this changing the rollup creation salt and thus address would cause issue downstream
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not 100% sure, but I think in most places/repos we moved away from hard-coded addresses and instead get them by parsing files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Deploy CacheManager and enable it on L2 and L3 by calling nitro-contracts' action
Set initial chain owners on L2 and L3 to be l2owner and l3owner accounts
Resolves BLK-170