A working group of the Lido on Ethereum protocol contributors (@TheDZhon,
@arwer13) has evaluated the current proposal and ended up with the following:
- the proposed contracts adhere to the established design of the wstETH token on Layer 2 solutions described in depth in the wstETH rollup bridging guide;
- the deployments are in full correspondence with the presented audit, source code, and bytecode wise, with no significant issues found;
- all configurations and parameters are relevant and meet expectations, according to this state configuration file;
- the access control list (ACL) configuration appears reasonable regarding the Lido DAO ownership and usage of the Emergency Breaks setup for both L1 and L2 counterparts .
Namely, the ACL and levers setup is:
- For OptimismBridgeExecutor
getEthereumGovernanceExecutoris Lido DAO Agent (admin)
- On L1ERC20TokenBridge contract Lido DAO Agent is holder of roles:
DEFAULT_ADMIN_ROLEWITHDRAWALS_DISABLER_ROLEWITHDRAWALS_ENABLER_ROLEDEPOSITS_DISABLER_ROLEDEPOSITS_ENABLER_ROLE
- On L2ERC20TokenBridge contract ScrollBridgeExecutor is holder of roles:
DEFAULT_ADMIN_ROLEfor L2ERC20TokenBridgeWITHDRAWALS_DISABLER_ROLEfor L2ERC20TokenBridgeWITHDRAWALS_ENABLER_ROLEfor L2ERC20TokenBridgeDEPOSITS_DISABLER_ROLEfor L2ERC20TokenBridgeDEPOSITS_ENABLER_ROLEfor L2ERC20TokenBridge
- Emergency breaks msig on L1 is 0x73b047fe6337183A454c5217241D780a932777bD , 3/5 threshold, holds roles:
WITHDRAWALS_DISABLER_ROLEof L1ERC20TokenBridgeDEPOSITS_DISABLER_ROLEof L1ERC20TokenBridge
- Emergency breaks msig on L2 is a new one
0x244912352A639001ceCFa208cDaa7CB474c9eadEinheriting the same EOAs as for L1, 3/5 threshold, holds roles:WITHDRAWALS_DISABLER_ROLEof L2ERC20TokenBridgeDEPOSITS_DISABLER_ROLEof L2ERC20TokenBridge