-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Handle OVM_DeployerWhitelist initialization automatically #560
Copy link
Copy link
Closed
Labels
C-featureCategory: featuresCategory: features
Description
OVM_DeployerWhitelist has a function initialize() which must be called after the contract is created. We currently have a manual process for doing this. Ideally, this process would be handled automatically during the state dump generation step. It's necessary to note that we cannot call initialize() directly because the state dump is generated by deploying to an L1 chain (the contract is compiled for L2). Instead, we would need to directly manipulate the relevant storage slots chugsplash style (chugsplash could easily handle this case).
This contract can't have a constructor that sets the owner? We can't forget to call this on L2 post regenesis
Other solutions:
take-dump.tscallsinitialize()with a configurable value- We use the geth config option
address-manager-ownerand set the storage slot on startup
Originally posted by @tynes in #548 (comment)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-featureCategory: featuresCategory: features