You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reviewing the op-deployer docs, we found the L2 PAO role was incorrectly set. The L2 ProxyAdminOwner standard check seemed to have given a false positive when the op-deployer/OPCM because the L2 key handover should’ve failed when generating a recent testnet. Can we please investigate testKeyHandover and make sure its working as expected?
Steps to Reproduce
Deploy a chain using op-deployer (before the bug was fixed)
Create the genesis file
Use superchain-registry for all the standard validation checks
Get false positive
Expected behavior
The L2 ProxyAdminOwner comparision to the standard L2 PAO role should fail.
Bug Description
While reviewing the op-deployer docs, we found the L2 PAO role was incorrectly set. The L2 ProxyAdminOwner standard check seemed to have given a false positive when the op-deployer/OPCM because the L2 key handover should’ve failed when generating a recent testnet. Can we please investigate testKeyHandover and make sure its working as expected?
Steps to Reproduce
Expected behavior
The L2 ProxyAdminOwner comparision to the standard L2 PAO role should fail.
Environment Information:
Configurations:
Logs:
Additional context
Related issue: #470
Please ensure all required sections are filled out accurately to expedite the debugging process and improve issue resolution efficiency.
The text was updated successfully, but these errors were encountered: