# wstETH Deployment on Scroll **URL:** \ **Category:** Lido Multichain\ **Created:** [February 13, 2024, 2:50pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603 "2024-02-13T14:50:56Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![sherooberoo](https://avatars.discourse-cdn.com/v4/letter/s/53a042/32.png) [@sherooberoo](https://research.lido.fi/u/sherooberoo)\ **Post date:** [February 13, 2024, 2:50pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/1 "2024-02-13T14:50:56Z")
**Point of Contact:** Shahryar Hasnani - Scroll, Partnerships Manager ### **1. Introduction** Scroll proposes the deployment of wstETH (Wrapped staked ETH) to Scroll, with the ultimate goal being recognition of wstETH bridge endpoints as canonical by the Lido DAO. ### **2. Scroll’s Rapid Growth and Ecosystem** [Scroll](https://scroll.io/) is an EVM-equivalent ZK-Rollup built upon Ethereum, designed for scaling without sacrificing security, developer, or user experience: - **EVM Equivalence & Developer Friendliness:** Scroll is bytecode-compatible and builds upon Geth, enabling seamless migration of infrastructure and will support all existing development tools, including debuggers. Developers can work with a familiar development environment. No bytecode re-audits are required, minimizing the risk surface tremendously. - **Ethereum-native & Community first:** Scroll originated in close collaboration with the Ethereum Foundation’s zkEVM research within the [PSE (Privacy and Scaling Explorations) group](https://github.com/privacy-scaling-explorations)—in fact, our team has contributed [~50% of the upstream PSE zkEVM codebase over the past 2 years](https://twitter.com/pseudotheos/status/1664249089998077960)! Scroll has been open source & peer reviewed since day one, our testnet has been permissionless since its inception, and we continuously [publish](https://twitter.com/VitalikButerin/status/1585145691311329280?s=20&t=v8fXgqmJV_M1gmDRNEj7GA) [research](https://twitter.com/leonardoalt/status/1614189758774665221?s=20&t=ZbiCsoXsUW-XxnhDwm9qwQ) in an effort to demystify the inner works of [zk circuits and cryptography](http://scroll.io/blog). - **Decentralization & Security:** Scroll has continually made upgrades across testnets to make it more trustless, and is committed to decentralizing both its sequencing and proving. In addition, Scroll has a strong in-house security team that found and reported bugs in fellow ZK-Rollup’s proving systems in the past. In addition, Scroll has a [$1M Immunefi bug bounty and has audits from OpenZeppelin, Trail of Bits, Zellic, and Kalos.](https://scroll.io/blog/scrolls-security-measures) ZK-Rollups are widely considered to be the Holy Grail of Ethereum scaling. Scroll’s vision is to build a fully EVM-compatible ZK-Rollup that any existing Ethereum application can easily migrate to. Scroll launched mainnet on October 17th, 2023, and since then, we’ve had significant traction, seeing: - ~70M bridged TVL / ~30M DeFi TVL - 16M+ transactions (averaging over 100k+ tx/day) - 3M unique wallet addresses In addition, between our Alpha (Goerli) and Beta (Sepolia) Testnets, we’ve ~60M transactions, 10M wallet addresses, and 7M blocks produced. We’ve also seen 150+ projects deployed on Scroll, ranging from established DeFi protocols to brand-new Scroll-native applications. ### **3. High Demand for wstETH** Lido’s stETH (and wstETH) is a critical asset in the Ethereum ecosystem with a significant market capitalization, and has emerged as a crucial component in DeFi applications. Naturally, a wide variety of protocols on Scroll—both established and native—have already indicated significant demand for wstETH across various use cases. Examples of this include wstETH’s usage as collateral, in lending protocols, DEX pools, vaults, yield optimizers / farming, indexes, LST-backed stablecoins, etc. Furthermore, already more than 3700 wstETH tokens have minted on Scroll, with over 7000 unique holders. There has been steady, organic growth of the asset with clear demand since Scroll’s mainnet launch. ### 4. Implementation Scroll has already implemented the canonical wstETH L1 and L2 Gateways, and has concluded its audit. The design uses the architecture of [wstETH on Optimism and Arbitrum](https://github.com/lidofinance/lido-l2) and [governance forwarder](https://github.com/lidofinance/governance-crosschain-bridges) used on multiple L2s as reference. Moreover, the path forward is upgrading in response to reference architecture and governance decision-forwarding demand, not redeploying the token from scratch, significantly simplifying the necessary next steps. Further details below: - [Governance Forwarding](https://github.com/scroll-tech/governance-crosschain-bridges/) - Emergency Brakes: The upgrade architecture allows emergency pause functionality for wstETH deposits/withdrawals, activated using the established mechanism of [Emergency Breaks](https://research.lido.fi/t/emergency-brakes-signer-rotation/5286). ### 5. Conclusion In conclusion, this proposal seeks recognition of wstETH bridge endpoints as canonical by the Lido DAO; this will be a crucial step forward in enabling wstETH as a core asset in the Scroll ecosystem and encouraging new use cases for it on the network. Scroll itself will also work towards researching and developing new areas for wstETH utility, in an effort to increase the application, decentralization, and community support / adoption of wstETH. ### Scroll Bridge and Rollup Contract Audits - Bridge and Rollup contract - OpenZeppelin - [Phase 1](https://blog.openzeppelin.com/scroll-layer-1-audit-1) - [Phase 2](https://blog.openzeppelin.com/scroll-phase-2-audit) - [GasSwap, Multiple Verifier, Wrapped Ether and Diff](https://blog.openzeppelin.com/scroll-gasswap-multiple-verifier-wrapped-ether-and-diff-audit) - [ScrollOwner and Rate Limiter](https://blog.openzeppelin.com/scrollowner-and-rate-limiter-audit) - [USDC Gateway](https://blog.openzeppelin.com/scroll-usdc-gateway-audit) - [Contract diff](https://blog.openzeppelin.com/scroll-diff-audit-report) - Zellic - [Contract v1](https://github.com/Zellic/publications/blob/master/Scroll%20-%2005.26.23%20Zellic%20Audit%20Report.pdf) - [Contract v2](https://github.com/Zellic/publications/blob/master/Scroll%20-%2009.27.23%20Zellic%20Audit%20Report.pdf) ### Audits - [Governance crosschain bridges (ScrollBridgeExecutor)](https://drive.google.com/file/d/1X6YKpSLN9VYaTnsMOaEcMRNz2rcpzNI6/view?usp=sharing) - [wstETH on Scroll (L1LidoGateway, L2LidoGateway, L2WstETHToken, LidoBridgeableTokens, LidoGatewayManager)](https://drive.google.com/file/d/1X6YKpSLN9VYaTnsMOaEcMRNz2rcpzNI6/view?usp=sharing) ### Testnet Contracts **Core Protocol** - wstETH token: [0xB82381A3fBD3FaFA77B3a7bE693342618240067b](https://sepolia.etherscan.io/address/0xB82381A3fBD3FaFA77B3a7bE693342618240067b) - Aragon Agent: [0x32A0E5828B62AAb932362a4816ae03b860b65e83](https://sepolia.etherscan.io/address/0x32A0E5828B62AAb932362a4816ae03b860b65e83) (proxy) **Lido on L2** **Ethereum component** - L1LidoGateway (_proposed_): [0xF22B24fa7c3168f30b17fd97b71bdd3162DDe029](https://sepolia.etherscan.io/address/0xF22B24fa7c3168f30b17fd97b71bdd3162DDe029) (proxy) - L1LidoGateway (_proposed_): [0x99845934FC8Ed44F3E6e66b3BAecf24d9e457F7f](https://sepolia.etherscan.io/address/0x99845934FC8Ed44F3E6e66b3BAecf24d9e457F7f) (impl) - ProxyAdmin (_proposed_): [0x0dB416f4387ED89c1C99955fe0Ecad458f07c467](https://sepolia.etherscan.io/address/0x0dB416f4387ED89c1C99955fe0Ecad458f07c467) for L1LidoGateway **Scroll component** - ScrollBridgeExecutor (_proposed_): [0x6b314986E3737Ce23c2a13036e77b3f5A846F8AF](https://sepolia.scrollscan.com/address/0x6b314986E3737Ce23c2a13036e77b3f5A846F8AF) - L2LidoGateway (_proposed_): [0x635B054A092F6aE61Ce0Fddc397A704F6626510D](https://sepolia.scrollscan.com/address/0x635B054A092F6aE61Ce0Fddc397A704F6626510D) (proxy) - L2LidoGateway (_proposed_): [0x906CD1Bfa5C3f7B2FF9BFBB5950ada841ED99E72](https://sepolia.scrollscan.com/address/0x906CD1Bfa5C3f7B2FF9BFBB5950ada841ED99E72) (impl) - L2WstETHToken (_proposed_): [0x2DAf22Caf40404ad8ff0Ab1E77F9C08Fef3953e2](https://sepolia.scrollscan.com/address/0x2DAf22Caf40404ad8ff0Ab1E77F9C08Fef3953e2) (proxy) - L2WstETHToken (_proposed_): [0xaed405fc13d66e2f1055f6efe9a5ce736652fa55](https://sepolia.scrollscan.com/address/0xaed405fc13d66e2f1055f6efe9a5ce736652fa55) (impl) - ProxyAdmin (_proposed_): [0xc6cdc2839378d50e03c9737723d96d117b09bda5](https://sepolia.scrollscan.com/address/0xc6cdc2839378d50e03c9737723d96d117b09bda5) for: - L2LidoGateway - L2WstETHToken **We will follow up shortly in the comments with mainnet contracts and levers setup when it is completed.** ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [February 14, 2024, 8:08pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/2 "2024-02-14T20:08:10Z")
Hey, @sherooberoo Thank you for posting the proposal! It’s thrilling to see wstETH adoption happening on zk rollups and facing game-changing Dencun hardfork soon. Also, the mentioned organic growth of wstETH is quite surprising and promising. It is charming to see that the testnet deployment on Sepolia has been conducted and fully corresponds to the expected parameters and the code covered with audits. * * * To approach the Mainnet **upgrade** deployment, I’d suggest a two-phased scheme presented here: [wstETH on Scroll mainnet preparations - HackMD](https://hackmd.io/oBQrAyemTqSJ80bMTAFAwQ?view) ### Stage I (pre-Vote) > The first stage paves the way for both NEW and MixBytes() verification, and, as a result, a snapshot vote started as a part of the regularly maintained cadence 1. Deploy new impls - new `L1LidoGateway` - new `ScrollBridgeExecutor` - new `L2LidoGateway` - new `L2WstETHToken` 2. Bind the new impls - `L1CustomERC20Gateway` upgrade to `L1LidoGateway` - `L2CustomERC20Gateway` upgrade to `L2LidoGateway` - `ScrollStandardERC20` upgrade to `L2WstETHToken` 3. Assign the interim pre-vote ACL - `L1LidoGateway` owner and deposit enabler is `DAO Agent` - `L1LidoGateway` deposit pausers are `DAO Agent` and `L1 emergency breaks` - `L2LidoGateway` owner and deposit enabler is `DAO Agent` - `L2LidoGateway` deposit pausers are `ScrollBridgeExecutor` and `L2 emergency breaks` ### Stage II (after the vote, if supported) > The second stage would consummate the DAO recognition process if the snapshot vote had been supported 1. Assign the final post-vote ACL - `L1LidoGateway` proxy admin is `DAO Agent` - `L2LidoGateway` proxy admin is `ScrollBridgeExecutor` - `L2WstETHToken` proxy admin is `ScrollBridgeExecutor` ---
**Author:** ![Tane](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/tane/32/4083_2.png) [@Tane](https://research.lido.fi/u/Tane)\ **Post date:** [February 20, 2024, 11:10pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/3 "2024-02-20T23:10:38Z")
Hi @sherooberoo, thank you so much for the proposal! We would love to support the deployment, as we’ve seen a lot of great progress made by the Scroll team both on Scroll itself and on research within PSE. We are very much looking forward to the rise of the Scroll DeFi ecosystem, and we hope to discuss the deployment of appropriate incentives as progress is made. ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [March 5, 2024, 1:42pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/4 "2024-03-05T13:42:58Z")
The suggested pre-vote txes have been executed: - [Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0xd755174ba6bacec85b68b77c9ec2a8b966955746be59a6efa932f47c37dda482) - [Scroll Transaction Hash (Txhash) Details | Scrollscan](https://scrollscan.com/tx/0x64c28a89bdfa47a14998cdaaa4d85113e72c451e817a294930f93bdee4a3d598) There will be a follow-up from the NEW members and MixBytes() with regards to the deployed setup review and assigned levers in a few days ahead. ---
**Author:** ![sherooberoo](https://avatars.discourse-cdn.com/v4/letter/s/53a042/32.png) [@sherooberoo](https://research.lido.fi/u/sherooberoo)\ **Post date:** [March 7, 2024, 8:16pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/5 "2024-03-07T20:16:28Z")
### Mainnet contracts listed here: ##### Emergency Brakes Multisigs - Scroll (_proposed_): [`0xF580753E334687C0d6b88EF563a258f048384Ee6`](https://safe.scroll.xyz/home?safe=scr:0xF580753E334687C0d6b88EF563a258f048384Ee6) ##### Ethereum part - L1LidoGateway (_proposed_): [`0x6625c6332c9f91f2d27c304e729b86db87a3f504`](https://etherscan.io/address/0x6625c6332c9f91f2d27c304e729b86db87a3f504) (proxy) - L1LidoGateway (_proposed_): [`0xF4f2066EE72D62e3caF9678459149BA7FCf2262F`](https://etherscan.io/address/0xF4f2066EE72D62e3caF9678459149BA7FCf2262F) (impl) - ProxyAdmin (_proposed_): [`0xCC2C53556Bc75217cf698721b29071d6f12628A9`](https://etherscan.io/address/0xCC2C53556Bc75217cf698721b29071d6f12628A9) for L1LidoGateway ##### Scroll part - ScrollBridgeExecutor (_proposed_): [`0x0c67D8D067E349669dfEAB132A7c03A90594eE09`](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) - L2LidoGateway (_proposed_): [`0x8aE8f22226B9d789A36AC81474e633f8bE2856c9`](https://scrollscan.com/address/0x8aE8f22226B9d789A36AC81474e633f8bE2856c9) (proxy) - L2LidoGateway (_proposed_): [`0x2B9beB2890DBeFC7cA25Af3164100d139B623C24`](https://scrollscan.com/address/0x2B9beB2890DBeFC7cA25Af3164100d139B623C24) (impl) - L2WstETHToken (_proposed_): [`0xf610A9dfB7C89644979b4A0f27063E9e7d7Cda32`](https://scrollscan.com/address/0xf610A9dfB7C89644979b4A0f27063E9e7d7Cda32) (proxy) - L2WstETHToken (_proposed_): [`0x38224D52ecC979aEdfEb31b1EEa0cfCEbd55247e`](https://scrollscan.com/address/0x38224D52ecC979aEdfEb31b1EEa0cfCEbd55247e) (impl) - ProxyAdmin (_proposed_): [`0x8e34D07Eb348716a1f0a48A507A9de8a3A6DcE45`](https://scrollscan.com/address/0x8e34D07Eb348716a1f0a48A507A9de8a3A6DcE45) for: - L2LidoGateway - L2WstETHToken ---
**Author:** ![DZahar0v](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dzahar0v/32/3480_2.png) [@DZahar0v](https://research.lido.fi/u/DZahar0v)\ **Post date:** [March 12, 2024, 9:18am UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/6 "2024-03-12T09:18:50Z")
[MixBytes](https://mixbytes.io/) team was engaged and has verified wstETH deployment on Scroll. Three security researchers checked the presented information according to the internal checklist. The results are as follows: 1. Scroll aims to build a fully compatible zkEVM that will have all the features and precompiles that the standard EVM version does. This allows protocols to deploy as is, using contracts that were developed for the Ethereum blockchain. The current zkEVM version that is used by Scroll differs only for [these opcodes](https://docs.scroll.io/en/technology/chain/differences/), but these opcodes don’t affect the scope. 2. Bridge architecture is simple and allows transfers of wstETH and governance decisions only. The wstETH token on Scroll has an unnecessary callback, which brings additional possible risks to token integration in the future. Protocols that will integrate wstETH on Scroll should be aware of this callback. 3. All deployed contracts fully match the audited ones. All contracts are deployed from EOA, so there is no risk of a [changeable contract code](https://mixbytes.io/blog/metamorphic-smart-contracts-is-evm-code-truly-immutable). 4. All contracts were correctly deployed and initialized. 5. All roles for the contracts are set as expected. ProxyAdmin for the `L1LidoGateway` should be updated to [this address](https://etherscan.io/address/0xCC2C53556Bc75217cf698721b29071d6f12628A9); for the `L2LidoGateway` and `L2WstETHToken` ProxyAdmin should be updated to [this address](https://scrollscan.com/address/0x8e34D07Eb348716a1f0a48A507A9de8a3A6DcE45). Currently, ProxiAdmins are controlled by the Scroll team, but this should be changed in the second stage of the deployment. ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [March 12, 2024, 10:11am UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/7 "2024-03-12T10:11:39Z")
A working group of the Lido on Ethereum protocol contributors (@arwer13, @TheDZhon) has evaluated the current proposal and ended up with the following: - The [proposed contracts](https://docs.lido.fi/deployed-contracts/#scroll) adhere to the established design of the wstETH token on Layer 2 solutions described in depth in the [wstETH rollup bridging guide](https://docs.lido.fi/token-guides/wsteth-bridging-guide) - The deployments are in full correspondence with the presented [audit](https://drive.google.com/file/d/1X6YKpSLN9VYaTnsMOaEcMRNz2rcpzNI6/view?usp=sharing), source code, and bytecode wise, with no significant issues found - All configurations and parameters are relevant and meet expectations. - The access control list (ACL) configuration appears reasonable regarding the Lido DAO ownership and usage of the [Emergency Breaks](https://research.lido.fi/t/emergency-brakes-signer-rotation/5286) setup for [both L1 and L2 counterparts](https://docs.lido.fi/deployed-contracts/#emergency-brakes-multisigs). **NB:** It’s suggested that the proxy admin instances be passed to the Lido DAO on condition of the successful snapshot vote run. * * * Pre-vote ACL and levers setup: - for [ScrollBridgeExecuror](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) - A bridge admin and role holder on L1 is the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - A bridge admin and role holder on L2 is the [ScrollBridgeExecutor](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) - Emergency breaks msig on L1 is [0x73b047fe6337183A454c5217241D780a932777bD](https://snapshot.org/#/lido-snapshot.eth/proposal/0xfe2a6a6506a642b616118363bc29aa83dd9ef2ec80447bb607a8f52c0a96aed0), 3/5 threshold: - Emergency breaks msig on L2 is a new one [`0xF580753E334687C0d6b88EF563a258f048384Ee6`](https://safe.scroll.xyz/home?safe=scr:0xF580753E334687C0d6b88EF563a258f048384Ee6) inheriting the same EOAs as for L1, 3/5 threshold: * * * ⏭ Post-vote (if the vote is supported) finalizing actions from the Scroll side: - for L1LidoGateway - assign the [`proposed ProxyAdmin on L1`](https://etherscan.io/address/0xCC2C53556Bc75217cf698721b29071d6f12628A9) having the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) `owner` - for [L2WstETHToken](https://scrollscan.com/address/0xf610A9dfB7C89644979b4A0f27063E9e7d7Cda32) and L2LidoGateway - assign the [`proposed ProxyAdmin on L2`](https://scrollscan.com/address/0x8e34D07Eb348716a1f0a48A507A9de8a3A6DcE45) having the [ScrollBridgeExecuror](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) `owner` * * * We suggest that Lido DAO take this proposal favorably, which would enhance the presence of wstETH in one of the most up-and-coming L2 solutions. ---
**Author:** ![governance-data-bot](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/governance-data-bot/32/2204_2.png) [@governance-data-bot](https://research.lido.fi/u/governance-data-bot)\ **Post date:** [March 14, 2024, 4:36pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/8 "2024-03-14T16:36:15Z")
## Snapshot vote started Please get your wallets ready to cast a vote ✅, the [Should the Lido DAO recognize the wstETH Bridge Endpoints on Scroll as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0xcdb7d84ea80d914a4abffd689ecf9bdc4bb05d47f1fdbdda8793d555381a0493) Snapshot has started! The Snapshots ends on Thu, 21 Mar 2024 16:00:00 GMT. ---
**Author:** ![governance-data-bot](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/governance-data-bot/32/2204_2.png) [@governance-data-bot](https://research.lido.fi/u/governance-data-bot)\ **Post date:** [March 21, 2024, 4:06pm UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/9 "2024-03-21T16:06:45Z")
## Snapshot vote ended Thank you all who participated in [Should the Lido DAO recognize the wstETH Bridge Endpoints on Scroll as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0xcdb7d84ea80d914a4abffd689ecf9bdc4bb05d47f1fdbdda8793d555381a0493) Snapshot, we reached a quorum! 🙏 The results are: **Recognize** : 71.8M LDO **Don’t recognize** : 0 LDO ---
**Author:** ![TheDZhon](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/thedzhon/32/800_2.png) [@TheDZhon](https://research.lido.fi/u/TheDZhon)\ **Post date:** [March 22, 2024, 7:42am UTC](https://research.lido.fi/t/wsteth-deployment-on-scroll/6603/10 "2024-03-22T07:42:16Z")
Happy to confirm that the post-vote transactions have been executed: - L1: [Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0xec8f670e965d98abd9e7ae4a075880de238bea6411a89026a7c10f18687a519c/advanced) - L2: [Scroll Transaction Hash (Txhash) Details | Scrollscan](https://scrollscan.com/tx/0x224ade0580f3fcc435a7ab2b5850abad85a8a5e637ee7aafa9314a498f8ff7b0) Therefore, the levers setup is complete for those proxy admin entities: - for L1LidoGateway - [`ProxyAdmin on L1`](https://etherscan.io/address/0xCC2C53556Bc75217cf698721b29071d6f12628A9) having the [Lido DAO Agent](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) `owner` - for [L2WstETHToken](https://scrollscan.com/address/0xf610A9dfB7C89644979b4A0f27063E9e7d7Cda32) and L2LidoGateway - [`ProxyAdmin on L2`](https://scrollscan.com/address/0x8e34D07Eb348716a1f0a48A507A9de8a3A6DcE45) having the [ScrollBridgeExecuror](https://scrollscan.com/address/0x0c67D8D067E349669dfEAB132A7c03A90594eE09) `owner`