stETH/wstETH deployment on Unichain

Proposals Lido Multichain
1

Introduction:

The Uniswap Foundation proposes the deployment of stETH and wstETH (wrapped staked ETH) to Unichain, with the ultimate goal of acceptance of ownership of the wstETH bridging components by the Network Expansion Committee.

1. Unichain’s Positioning and Growth Potential:

Unichain is an OP-stack L2 and member of the Superchain. In the next few months, upgrades will be made to enable faster inclusion times (<250ms thanks to Rollup Boost) and stronger finality assurances for transactions that are posted to mainnet (thanks to the UNI Validation Network). These will be the first customizations of Unichain but not the last; the goal is to build a chain that is truly optimized for DeFi.

Because Unichain is a member of the Superchain, it is highly scalable and secure. The core chain infrastructure is in production across numerous L2s, serving billions of dollars of AUM and millions of users daily. Optimism’s interoperability roadmap describes an exciting, imminent step towards unifying this liquidity; Unichain (and Uniswap’s protocol engineers) will be on the front lines of this transition.

We plan to leverage these technical differentiators and Uniswap v4’s potential for deep, expressive liquidity to make Unichain the home for DeFi. The Uniswap Foundation will fuel this growth with a robust grants program targeting DeFi developers on Unichain. Lido’s staked ETH and wrapped staked ETH are fundamental building blocks of any new protocol, and as we fund the exploration of new use cases that v4’s hooks enable, we are excited to see stETH and wstETH put to work in creative, valuable ways.

Finally, Unichain launched with the best day 1 developer infrastructure offering ever. We are proud to have worked with the many partners listed here.

References: Unichain Website | Unichain L2Beat | Unichain Whitepaper

2. Unichain’s DeFi Ecosystem and High Demand for stETH/wstETH:

We were thrilled to launch Unichain with day 1 support from many top-tier DeFi protocols, including:

  • Venus
  • Compound
  • Bunni
  • Beefy
  • Revert
  • Steer
  • Swell
  • Renzo
  • Gamma Strategies

The ecosystem will grow rapidly over the next three months, as the many protocols in our pipeline deploy to Unichain. We are working with the top teams across every category, including:

  • Liquid restaking
  • Borrow / lend
  • Real-world assets
  • Structured trading products
  • BTC-fi
  • Stablecoins

For a more granular look at our pipeline, please see here.

A Lido deployment on Unichain will be mutually beneficial as the DeFi ecosystem there evolves. Access to ETH staking yield is a vital unlock for the many protocols planning a Unichain deployment. Likewise, Unichain’s fertile ground for experimentation will unlock new use cases for stETH and wstETH as developers fully investigate the design space unlocked by v4’s hooks. The result will be a useful, positive-sum ecosystem that drives real value for its end users.

Proposal

This proposal outlines the recognition of stETH/wstETH bridge endpoints on Unichain as canonical.

The contracts have been deployed on Ethereum and Unichain mainnets and verified in block explorers with the below addresses.

On Ethereum

  • (proposed) OpStackTokenRatePusher: 0x3F9600439Ad97fC6f55C2AC7C118f8Fd0595eB74
  • (proposed) L1LidoTokensBridge: 0x755610f5Be536Ad7afBAa7c10F3E938Ea3aa1877 (proxy)
  • (proposed) L1LidoTokensBridge: 0x6078232C54d956c901620fa4590e0F7E37c2B82f (impl)

On Unichain

  • (proposed) WstETH ERC20BridgedPermit: 0xc02fE7317D4eb8753a02c35fe019786854A92001 (proxy)
  • (proposed) WstETH ERC20BridgedPermit: 0xB5CF096A406C1D5297D2493073168F44EB4a1A1d (impl)
  • (proposed) StETH ERC20RebasableBridgedPermit: 0x81f2508AAC59757EF7425DDc9717AB5c2AA0A84F (proxy)
  • (proposed) StETH ERC20RebasableBridgedPermit: 0x5A007D6E37633FB297b82c074b94Bb29546BEbc3 (impl)
  • (proposed) TokenRateOracle: 0xD835fAC9080396CCE95bDf9EcC7cc27Bab12c9f8 (proxy)
  • (proposed) TokenRateOracle: 0x537A7F9D551da3C2800cB11ca17f2946D21029AF (impl)
  • (proposed) L2ERC20ExtendedTokensBridge: 0x1A513e9B6434a12C7bB5B9AF3B21963308DEE372 (proxy)
  • (proposed) L2ERC20ExtendedTokensBridge: 0x332CA368dd09AD309c51dC6350730e0Bca85CffE (impl)
  • (proposed) Governance Bridge Executor: 0x3b00f262e39372DF2756f809DD5DC36aeEdFC4A0

UI

Next steps if there are no objections

  • Launch UI for wstETH on Unichain on the Lido Multichain Page for better DeFi options accessibility and improved user experience.
  • Launch support materials such as a bridging help guide.
  • Announcements via Blog posts, Twitter, Discord, and Telegram for community engagement.

Audits

External deployment verification

  • To be provided by GRAPPA

Conclusion

The recognition of wstETH bridge endpoints as canonical bridging components by the Network Expansion Committee would mark a significant milestone in strengthening the DeFi ecosystem within Unichain and driving further adoption of wstETH. We are excited to start this conversation, and welcome any feedback the Lido community may have.

7 Likes
2

Hi! MixBytes CTO is here :raised_hands:
MixBytes team, as a part of the GRAPPA initiative, was engaged and verified stETH and wstETH deployment on the Unichain Network. Four security researchers checked the presented information according to the internal checklist. The results are as follows:

  1. The Unichain Network, part of the Superchain Network of Optimism forks, operates similarly to Optimism, which has been previously verified for deployment. The Unichain Network is built on the OP stack with no significant differences except for faster block times.

  2. The same team that audited the scope also conducted the deployment verification, ensuring that all security measures were implemented and no changes were made post-audit. The scope was additionally checked to ensure proper functionality with fast block times.

  3. The bytecode of the deployed contracts is identical to the audited version. All contracts were deployed from an externally owned account (EOA), eliminating the risk associated with metamorphic contracts.

  4. The contracts are properly initialized, safeguarded against reinitialization, and configured with the correct parameters.

  5. Roles have been accurately assigned to the appropriate addresses, and there are no unidentified addresses within the multisig. The multisig addresses on L2 correspond exactly to those on L1.

3 Likes