# wstETH deployment on Starknet

**URL:** <https://research.lido.fi/t/wsteth-deployment-on-starknet/6335>\
**Category:** Lido Multichain\
**Created:** [January 9, 2024, 2:49pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335 "2024-01-09T14:49:30Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Natan\_SW](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@Natan\_SW](https://research.lido.fi/u/Natan_SW)\
**Post date:** [January 9, 2024, 2:49pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/1 "2024-01-09T14:49:30Z")

</div>

## Introduction

StarkWare proposes the deployment of wstETH (Wrapped staked ETH) to Starknet, with the ultimate goal of recognition of the wstETH bridge endpoints as canonical by the Lido DAO.

### Starknet’s Growth and Ecosystem

We believe in the potential of wstETH on Starknet to bring new opportunities within the DeFi ecosystem and boost the demand for wstETH across various platforms.

Since Nov ‘21, developers worldwide have worked tirelessly to build and develop Starknet’s Mainnet, the first Turing-complete Validity Rollup on Ethereum. As a result, Starknet is now the largest developer ecosystem among all L2s, having grown 14% over the past year to become the [8th largest](https://www.developerreport.com/) blockchain developer community and the leader in the L2 landscape.

References: [Developers Report](https://www.developerreport.com/).

### High Demand for wstETH

Lido’s (w)stETH has secured its position as a leading DeFi protocol on Ethereum mainnet. Starknet, as a leading Ethereum scaling solution, is seeing significant demand for the adoption of the wstETH as it opens up opportunities for users to utilize stETH holdings in various DeFi protocols. Launching wstETH on Starknet supports the missions of Lido, Ethereum, and Starknet, making Ethereum scalable, decentralized, and approachable. Therefore, major ecosystems such as Starknet have significant demand for wstETH as it opens up opportunities for users to utilize stETH holdings in various DeFi protocols.

## Implementation

Currently, wstETH is bridged to Starknet via StarkGate, the canonical bridge of Starknet developed by StarkWare. All the bridge components, both L1 and L2, are upgradeable. Starkware will enable a cross-chain governance solution that will enable Lido to govern the bridge’s wstETH. We estimate that the feature will be available by the end of Q2 2024.

### Next Steps

The relevant source code and audits will be made available after the development of the cross-governance future is finished. These will be published to provide full transparency and accessibility to the Lido community. In addition to the cross-governance feature, we will propose upgrading the wstETH bridge to the latest version of StarkGate, StarkGate 2.0. This version is already live on Goerli and will soon be launched on Mainnet (For other tokens). The community will be encouraged to review the code and raise any questions or concerns they might have before the mainnet launch.

## Conclusion

The recognition of wstETH bridge endpoints as canonical of the bridging components by Lido DAO will represent a significant step toward enhancing the DeFi ecosystem within Starknet and the continued adoption of wstETH.The importance of this initiative is underscored by the steady growth and high potential of Starknet, together with the strong demand for wstETH.

We invite the Lido community to engage in discussions and provide feedback as we move forward with this exciting development.

## Audits

- Current wstETH bridge and L2 ERC20: [https://drive.google.com/file/d/1w6vo0imWfX9WqTiCiMkXcSV0rpkKNfd8/view?usp=sharing](https://drive.google.com/file/d/1w6vo0imWfX9WqTiCiMkXcSV0rpkKNfd8/view?usp=sharing)
- StarkGate 2.0 bridge and L2 ERC20 (Currently on Goerli): [https://drive.google.com/file/d/1y\_DAMf91RM7tn3ELRych\_mabsb\_18Gni/view?usp=sharing](https://drive.google.com/file/d/1y_DAMf91RM7tn3ELRych_mabsb_18Gni/view?usp=sharing)

## Mainnet Contracts (StarkGate 1.0)

- L1 wstETH token address: “0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0”,
- L1 bridge address: “0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B”,
- L2 bridge address: “0x0088eedbe2fe3918b69ccb411713b7fa72079d4eddf291103ccbe41e78a9615c”,
- L2 wstETH token address: “0x42b8f0484674ca266ac5d08e4ac6a3fe65bd3129795def2dca5c34ecc5f96d2”

## Testnet (Goerli) Contracts (StarkGate 2.0)

- L1 wstETH token address: “0x6320cD32aA674d2898A68ec82e869385Fc5f7E2f”,
- L1 bridge address: “0x190c98506a5396A30CA759A139F3Fb59EF519A5D”,
- L2 bridge address: “0x0399a6011b666888d647665fd65d6dcc7c2690c72d4c4454cae987f19f6ef609”,
- L2 wstETH token address: “0x0335bc6e1cf6d9527da4f8044c505906ad6728aeeddfba8d7000b01b32ffe66b”

## Levers setup wstETH StarkGate bridge (suggested):

### L1 Ethereum

- governance\_admin - StarkWare extreme cold wallet (Lido DAO agent):
  - Assign governance\_admin
  - Assign upgrade\_governor
  - Assign app\_role\_admin

- upgrade\_governor - StarkWare cold wallet (Lido DAO agent):
  - Can upgrade the bridge contract on L1.

- app\_role\_admin - StarkWare cold wallet (Lido DAO agent):
  - Assign app\_governor
  - Assign token\_admin

- app\_governor - StarkWare cold wallet (Lido DAO agent):
  - Change Max TVL limit.

- token\_admin - StarkWare cold wallet (Lido DAO agent):
  - Register token.

### L2 Starknet

- governance\_admin - StarkWare extreme cold wallet (Lido DAO agent through gov. feature):
  - Assign governance\_admin
  - Assign upgrade\_governor
  - Assign app\_role\_admin

- upgrade\_governor - StarkWare cold wallet (Lido DAO agent through gov. feature):
  - Can upgrade the bridge contract on L1.

- app\_role\_admin - StarkWare cold wallet (Lido DAO agent through gov. feature):
  - Assign app\_governor
  - Assign token\_admin

## Source code and Documentation

- Source code [repo](https://github.com/starknet-io/starkgate-contracts) for StarkGate (Live on Mainnet).
- Source code [repo](https://github.com/starknet-io/starkgate-contracts/tree/v2.0) for StarkGate 2.0 (Live on Goerli).
- StarkGate [Documentation](https://docs.starknet.io/documentation/tools/starkgate-bridge/).

---

<div class="post-metadata">

**Author:** ![Jommi](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/jommi/32/3919_2.png) [@Jommi](https://research.lido.fi/u/Jommi)\
**Post date:** [January 15, 2024, 11:52am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/2 "2024-01-15T11:52:31Z")

</div>

Absolutely needed, and a huge step forward in terms of marking Starknet getting closer to its full launch as well as inspiring confidence that it will be a legitimate venue for scaling ethereum-based defi further than any other project before.

---

<div class="post-metadata">

**Author:** ![nathanvdh](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/nathanvdh/32/3931_2.png) [@nathanvdh](https://research.lido.fi/u/nathanvdh)\
**Post date:** [January 16, 2024, 1:56pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/3 "2024-01-16T13:56:59Z")

</div>

I’d be really happy to see this, and the timing for this proposal makes a lot of sense as Starknet currently is lacking options in terms of ETH staking.

---

<div class="post-metadata">

**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:** [January 17, 2024, 7:45am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/5 "2024-01-17T07:45:21Z")

</div>

Hey, @Natan_SW

Absolutely amazing proposal given the StarkWare experience and proven track record in ZK-STARKs pioneering and adoption.

I am particularly in love with [StarkWare x Herodotus](https://starkware.co/resource/proving-ethereums-state-on-starknet-with-herodotus/) collab to make storage proofs available across ecosystem paving the way for more robust bridging and DeFi opportunities.

* * *

With regards the proposal presented, would love to be in touch for connecting the dots with technical and security stuff counseling and advising, including a possible governance forwarder implementation.

As for me, having those is highly desirable to run a transparent Snapshot vote given the long-term opportunities and ecosystem maturity.

---

<div class="post-metadata">

**Author:** ![Ohad\_Barta](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ohad_barta/32/3940_2.png) [@Ohad\_Barta](https://research.lido.fi/u/Ohad_Barta)\
**Post date:** [January 18, 2024, 5:43pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/6 "2024-01-18T17:43:08Z")

</div>

Hey @TheDZhon , thanks for your warm comment! I’m Ohad from the StarkWare team and I work closely with Natan. We are now in initial phases of designing the governance forwarder, and we think designing it with maximal collaboration and transperancy is essential for moving toward a vote and build trust between our ecosystems.

Therefore I’d love to discuss with you the governance forwarder design, as well as any other concern you have, around the proposed way to integrate wstETH to Starknet.

If anyone else would like to discuss it LMK! I’m @OhadStarkWare on TG.

---

<div class="post-metadata">

**Author:** ![Natan\_SW](https://avatars.discourse-cdn.com/v4/letter/n/c77e96/32.png) [@Natan\_SW](https://research.lido.fi/u/Natan_SW)\
**Post date:** [August 15, 2024, 12:24pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/7 "2024-08-15T12:24:29Z")

</div>

# wstETH Proposal update

We are thrilled to announce the successful completion of the cross-governance solution for wstETH on Starknet. This milestone has been made possible through dedicated efforts from the Nimbora team by [SpaceShard](https://www.spaceshard.io/) and strong backing from StarkWare.

As we move forward, we encourage the Lido community to engage in discussions and provide feedback on this development.

The Starknet Foundation has also separately committed to assigning [Defi Spring](https://www.starknet.io/blog/defi-spring-2-0/) rewards to wstEth in order to incentivise wstEth holders to bridge and deploy their wstEth on Starknet.

Below is the updated information regarding audits, mainnet and testnet contracts, and source code repositories.

## Audits

- StarkGate 2.0 bridge and L2 ERC20: [https://drive.google.com/file/d/1y\_DAMf91RM7tn3ELRych\_mabsb\_18Gni/view?usp=drive\_link](https://drive.google.com/file/d/1y_DAMf91RM7tn3ELRych_mabsb_18Gni/view?usp=drive_link)
- Lido - Starknet governance forwarder: [QuillAudit\_Reports/Lido Starknet Governance Forwarder Audit Report - QuillAudits .pdf at master · Quillhash/QuillAudit\_Reports · GitHub](https://github.com/Quillhash/QuillAudit_Reports/blob/master/Lido%20Starknet%20Governance%20Forwarder%20Audit%20Report%20-%20QuillAudits%20.pdf)

## Mainnet Contracts - StarkGate 2.0

- L1 wstETH token address: “[0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0](https://etherscan.io/address/0x7f39c581f595b53c5cb19bd0b3f8da6c935e2ca0)”,
- L1 bridge address: “[0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B](https://etherscan.io/address/0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B)”,
- L2 bridge address: “[0x0088eedbe2fe3918b69ccb411713b7fa72079d4eddf291103ccbe41e78a9615c](https://starkscan.co/contract/0x0088eedbe2fe3918b69ccb411713b7fa72079d4eddf291103ccbe41e78a9615c)”,
- L2 wstETH token address: “[0x42b8f0484674ca266ac5d08e4ac6a3fe65bd3129795def2dca5c34ecc5f96d2](https://starkscan.co/token/0x042b8f0484674ca266ac5d08e4ac6a3fe65bd3129795def2dca5c34ecc5f96d2)”
- Lido - Starknet governance forwarder: “[0x7ba4bb6a9ec398598c9c08424af6bdb83f56e78ffc8f07f0da0dfae8deca432](https://starkscan.co/contract/0x07ba4bb6a9ec398598c9c08424af6bdb83f56e78ffc8f07f0da0dfae8deca432)”

## Testnet (Sepolia) Contracts - StarkGate 2.0

- L1 wstETH token address: “[0xB82381A3fBD3FaFA77B3a7bE693342618240067b](https://sepolia.etherscan.io/address/0xb82381a3fbd3fafa77b3a7be693342618240067b)”,
- L1 bridge address: “[0xaCbb1B9021eC68370B9821d5F36ddE26796bb436](https://sepolia.etherscan.io/address/0xacbb1b9021ec68370b9821d5f36dde26796bb436)”,
- L2 bridge address: “[0x0172393a285eeac98ea136a4be473986a58ddd0beaf158517bc32166d0328824](https://sepolia.starkscan.co/contract/0x0172393a285eeac98ea136a4be473986a58ddd0beaf158517bc32166d0328824)”,
- L2 wstETH token address: “[0x030de54c07e57818ae4a1210f2a3018a0b9521b8f8ae5206605684741650ac25](https://sepolia.starkscan.co/token/0x030de54c07e57818ae4a1210f2a3018a0b9521b8f8ae5206605684741650ac25)”
- Lido - Starknet governance forwarder: “[0x07d52ac5647e26ec8e356ae5a15900e92e2e7e52ddd3cbaf8f15300906c4a89a](https://sepolia.starkscan.co/contract/0x07d52ac5647e26ec8e356ae5a15900e92e2e7e52ddd3cbaf8f15300906c4a89a)”

## Source code and Documentation

- Source code [repo](https://github.com/starknet-io/starkgate-contracts) for StarkGate 2.0 (Live on Mainnet).
- Source code [repo](https://github.com/0xSpaceShard/lido-starknet-governance-forwarder) for the Lido - Starknet governance forwarder.
- StarkGate [Documentation](https://docs.starknet.io/documentation/tools/starkgate-bridge/).

---

<div class="post-metadata">

**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:** [September 10, 2024, 5:08pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/8 "2024-09-10T17:08:58Z")

</div>

GM, thank you for updating the proposal, excited about the prospect of having wstETH recognized within the Starknet ecosystem.

To facilitate the upcoming snapshot vote, the Network Expansion Workgroup has engaged the well-known Nethermind Security team, who are deeply familiar with Starknet, to conduct a thorough review of the deployment artifacts and overall solution setup. Their insights might provide valuable information to help DAO token holders make a more informed decision.

Once the deployment verification report is finalized and any necessary adjustments are made, the report will be shared in this thread.

---

<div class="post-metadata">

**Author:** ![Shani\_Rozenzweig](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/shani_rozenzweig/32/5165_2.png) [@Shani\_Rozenzweig](https://research.lido.fi/u/Shani_Rozenzweig)\
**Post date:** [October 30, 2024, 9:22am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/9 "2024-10-30T09:22:21Z")

</div>

# wstETH Proposal update

Hey everyone, I’m Shani from the StarkWare team, and I recently took over StarkGate, replacing Natan.

Below you can find the updated information regarding audits (including a recent audit report), mainnet and testnet contracts, and source code repositories.

## Audits

- StarkGate 2.0 bridge and L2 ERC20 - Oct 2024: [StarkGate - Zellic Audit Report - Oct 2024](https://drive.google.com/file/d/1Ou0y0_nHCVyYqykLbw8xI07awDZqLLPk/view?usp=sharing)
- StarkGate 2.0 bridge and L2 ERC20 - Oct 2023: [StarkGate - Zellic Audit Report - Oct 2023](https://drive.google.com/file/d/1y_DAMf91RM7tn3ELRych_mabsb_18Gni/view?usp=drive_link)
- Lido - Starknet governance forwarder: [QuillAudit\_Reports/Lido Starknet Governance Forwarder Audit Report - QuillAudits .pdf at master · Quillhash/QuillAudit\_Reports · GitHub](https://github.com/Quillhash/QuillAudit_Reports/blob/master/Lido%20Starknet%20Governance%20Forwarder%20Audit%20Report%20-%20QuillAudits%20.pdf)

## Mainnet Contracts - StarkGate 2.0

- L1 wstETH token address: “[0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0](https://etherscan.io/address/0x7f39c581f595b53c5cb19bd0b3f8da6c935e2ca0)”,
- L1 bridge address: “[0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B](https://etherscan.io/address/0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B)”,
- L2 bridge address: “[0x0088eedbe2fe3918b69ccb411713b7fa72079d4eddf291103ccbe41e78a9615c](https://starkscan.co/contract/0x0088eedbe2fe3918b69ccb411713b7fa72079d4eddf291103ccbe41e78a9615c)”,
- L2 wstETH token address: “[0x42b8f0484674ca266ac5d08e4ac6a3fe65bd3129795def2dca5c34ecc5f96d2](https://starkscan.co/token/0x042b8f0484674ca266ac5d08e4ac6a3fe65bd3129795def2dca5c34ecc5f96d2)”
- Lido - Starknet governance forwarder: “[0x7ba4bb6a9ec398598c9c08424af6bdb83f56e78ffc8f07f0da0dfae8deca432](https://starkscan.co/contract/0x07ba4bb6a9ec398598c9c08424af6bdb83f56e78ffc8f07f0da0dfae8deca432)”

## Testnet (Sepolia) Contracts - StarkGate 2.0

- L1 wstETH token address: “[0xB82381A3fBD3FaFA77B3a7bE693342618240067b](https://sepolia.etherscan.io/address/0xb82381a3fbd3fafa77b3a7be693342618240067b)”,
- L1 bridge address: “[0xaCbb1B9021eC68370B9821d5F36ddE26796bb436](https://sepolia.etherscan.io/address/0xacbb1b9021ec68370b9821d5f36dde26796bb436)”,
- L2 bridge address: “[0x0172393a285eeac98ea136a4be473986a58ddd0beaf158517bc32166d0328824](https://sepolia.starkscan.co/contract/0x0172393a285eeac98ea136a4be473986a58ddd0beaf158517bc32166d0328824)”,
- L2 wstETH token address: “[0x030de54c07e57818ae4a1210f2a3018a0b9521b8f8ae5206605684741650ac25](https://sepolia.starkscan.co/token/0x030de54c07e57818ae4a1210f2a3018a0b9521b8f8ae5206605684741650ac25)”
- Lido - Starknet governance forwarder: “[0x07d52ac5647e26ec8e356ae5a15900e92e2e7e52ddd3cbaf8f15300906c4a89a](https://sepolia.starkscan.co/contract/0x07d52ac5647e26ec8e356ae5a15900e92e2e7e52ddd3cbaf8f15300906c4a89a)”

## Source code and Documentation

- Source code [repo](https://github.com/starknet-io/starkgate-contracts) for StarkGate 2.0 (Live on Mainnet).
- Source code [repo](https://github.com/0xSpaceShard/lido-starknet-governance-forwarder) for the Lido - Starknet governance forwarder.
- StarkGate [Documentation](https://docs.starknet.io/documentation/tools/starkgate-bridge/).

---

<div class="post-metadata">

**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:** [November 5, 2024, 6:53pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/10 "2024-11-05T18:53:43Z")

</div>

Hey, @Shani_Rozenzweig!

Thank you for continuing the thread. It’s good to see that the [up-to-date audit](https://drive.google.com/file/d/1Ou0y0_nHCVyYqykLbw8xI07awDZqLLPk/view) allowed to reveal and resolve quite a severe finding in the previously deployed version.

## ![image](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/9/959c50c6f6d99bf9c4244806cde8cd37044426cc.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/5/5eeab8b8e4d0829667d7dac6a08c0a2bb340bef8.png)

I see that the [L1 bridge proxy](https://etherscan.io/address/0xBf67F59D2988A46FBFF7ed79A621778a3Cd3985B) was upgraded to the following [impl](https://etherscan.io/address/0x6ad74D4B79A06A492C288eF66Ef868Dd981fdC85) deployed 26 days ago and marked as _‘StarkWare\_StarknetERC20Bridge\_2.0\_5’_ as in the [fix commit](https://github.com/starknet-io/starkgate-contracts/commit/45941888479663ac93e898cd7f8504fa9066c54c#diff-b371bb4caf609dac1e5d4792f4dada14c1d18fc6ac497264d1a0c7561ffd5182R135).

Nevertheless, as said earlier, to proceed, the Network Expansion Workgroup suggests waiting for the final deployment verification report from Nethermind Security to provide an outlook on the deployment artifacts’ state and overall setup.

Please stay tuned.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [November 7, 2024, 7:40am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/11 "2024-11-07T07:40:32Z")

</div>

Happy to join the discussion 🙂

I’m looking forward to moving this proposal because I think bridging wstETH between Ethereum and Starknet will not only boost the liquidity but also enhance Lido’s presence in Starknet’s growing DeFi ecosystem.

Starknet is a unique L2 and having significant wstETH presence on Starknet will grant Lido first mover advantage.

---

<div class="post-metadata">

**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:** [November 19, 2024, 5:28pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/12 "2024-11-19T17:28:32Z")

</div>

Hey everyone,

the Nethermind Security team has finalized the verification report, which contains an overview of the provided solution regarding the audited code state, roles, initialization, and previously used unofficial guidelines covering the design recommendations and bridging approaches.

The report has been uploaded to the audits repo: [audits/L2/Starknet-2024-11-14-deployment-verification.pdf at main · lidofinance/audits · GitHub](https://github.com/lidofinance/audits/blob/main/L2/Starknet-2024-11-14-deployment-verification.pdf)

It is worth highlighting that:

- the levers setup hasn’t been finalized, as it is contingent on the Lido DAO’s potential bridging endpoints and token recognition
- the token contract is unverified on Starkscan due to the longstanding [issue](https://github.com/starkscan/starkscan-verifier/issues/8) with Cairo 1 support

---

<div class="post-metadata">

**Author:** ![BlockworksResearch](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/blockworksresearch/32/4777_2.png) [@BlockworksResearch](https://research.lido.fi/u/BlockworksResearch)\
**Post date:** [November 19, 2024, 8:43pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/13 "2024-11-19T20:43:33Z")

</div>

### General Thoughts

Thank you to all the work from the multiple teams pushing wstETH improvements on Starknet/Lido forward. In general, the more control Lido DAO exercises over the flow of wstETH and stETH to external chains, the better. Historically, we’ve seen similar social checks/balances on wstETH bridging solutions, like optimism’s, and believe that viewing the proposed wstETH improvements through a lens of past precedent may be prudent. While we read the final deployment verification report from Nethermind Security, we feel the following questions would be helpful answering for visibility:

### Questions

1. Who are the actors capable of upgrading/disabling/enabling the bridging solution on the L1 and L2 side?

2. What safety measures are in place in case Lido governance experiences connectivity issues and loses the power to enforce its will?

3. With the recency of LIP 22, which enabled rebasable stETH on L2s from the stable balancer wrapper of wstETH, we find it pertinent to ask why a similar transition from wstETH to stETH was not taken on Starknet?

> **Sources**
>
> > [@LIP-22: stETH on L2](https://research.lido.fi/t/lip-22-steth-on-l2/6855):
> >
> > TL;DR Propose an architecture framework for the rebasable stETH token on L2 to be used across various Ethereum Layer 2 (L2) networks. The idea is to create a canonical version of stETH on these networks, being wrapped on top of wstETH (sort of ‘wrapped twice’). This approach will streamline the process of moving stETH across Ethereum rollups, making use of the existing wstETH infrastructure and liquidity venues on L2 networks. As a practical example, explore a design of upgrading the wstETH cus…
> 
> > [@wstETH on Optimism: bridging security management](https://research.lido.fi/t/wsteth-on-optimism-bridging-security-management/2427):
> >
> > Bridging stETH to Optimism Making Lido’s stETH available across L2 has been pronounced as [one of the main Lido’s OKRs for 2022](https://research.lido.fi/t/lido-teams-objectives-and-key-results-for-2022/1570#objectives-1). As part of this work, the Lido dev team is preparing to release a bridging solution for Optimism that aims at providing the benefits of yield-bearing staking tokens to users on Optimism. General bridging solution overview Because of its rebasing nature, bridging stETH adds a whole layer of complexity to the bridging itself, and to the upcoming integrations of the bri…

---

<div class="post-metadata">

**Author:** ![Remo\_Labin](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/remo_labin/32/5317_2.png) [@Remo\_Labin](https://research.lido.fi/u/Remo_Labin)\
**Post date:** [November 20, 2024, 12:21pm UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/14 "2024-11-20T12:21:47Z")

</div>

_1. Who are the actors capable of upgrading/disabling/enabling the bridging solution on the L1 and L2 side?_

- We have a few roles defined, these roles are mapped to the various restricted calls.  
the roles names, heirarchy and general “order of things” are the same for L1 & L2.  
`governance_admin` is the root of the roles heirarchy, it’s the “owner” of the contract, it can nominate upgrade\_governors (and `app_role_admin`)  
**upgrade related actions** - restricted to addresses that hold **upgrade\_governor** role (applies to L1 bridge, L2 bridge, L2 token)

security actions:  
**enable\_withdrawal\_limit** - restricted to the role of `security_agent` (both L1 & L2 bridge)  
**disable\_withdrawal\_limit** - restricted to the role of `security_admin` (both L1 & L2 bridge)

security\_admin can also nominate security\_agent & security\_admin (security roles are a separated role heirarchy).

on L1 bridge there is also the option to limit/disable deposit using `setMAxTotalBalance`  
which is restricted to the app\_governor (nominated by an app\_role\_admin)

_2. What safety measures are in place in case Lido governance experiences connectivity issues and loses the power to enforce its will?_

- assuming connectivity issues are conceived as more probable on the younger chain, the L2, then the ones on L1 can be used. deposits can be blocked as aforementioned, and withdrawals can be limited.

if the discontinuation of governance is due to compromise - that indicates the importance of managing well the two different levels of roles. the gov admin - that cannot execute, but can nominate, and the upgrage gov ,that cannot nominate, but execute and its execution is (can be) time delayed.

1. The enrollment of wstEth onto Starknet was done 18 ago, we didn’t know about LIP22. The basic pattern of token bridging does not do this wrapping pattern by default. we can talk about it 😉

---

<div class="post-metadata">

**Author:** ![itamarl](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/itamarl/32/1336_2.png) [@itamarl](https://research.lido.fi/u/itamarl)\
**Post date:** [November 25, 2024, 10:38am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/15 "2024-11-25T10:38:13Z")

</div>

Is this still an issue?  
You should be able to verify Cairo 1 contracts on voyager: [https://voyager.online/](https://voyager.online/)  
That’s where we have been doing it on Starknet. If any issue I can reach out to the team at Nethermind.

---

<div class="post-metadata">

**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:** [November 26, 2024, 7:46am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/17 "2024-11-26T07:46:50Z")

</div>

It seems that it’s not a blocker because the bytecode verification of the token deployed has passed against the audited commit (which is more strict and rigid).

Nevertheless, the request has been propagated to the team behind the proposal to check the feasibility of this approach and not delay the delivery.

---

<div class="post-metadata">

**Author:** ![Shani\_Rozenzweig](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/shani_rozenzweig/32/5165_2.png) [@Shani\_Rozenzweig](https://research.lido.fi/u/Shani_Rozenzweig)\
**Post date:** [November 28, 2024, 7:46am UTC](https://research.lido.fi/t/wsteth-deployment-on-starknet/6335/18 "2024-11-28T07:46:17Z")

</div>

The Voyager Verifier has a prerequisite that the contract code be built using Scarb, which is not the case for wstETH token (since it was built a while back). Refactoring the code to use Scarb would inevitably alter the class hash (even if the code is identical), because relative paths contribute to the class hash.  
In short - we cannot use the Voyager tool to verify the deployed contract.