# wstETH on Linea: Ownership Acceptance by Lido DAO **URL:** \ **Category:** Lido Multichain\ **Created:** [November 17, 2023, 8:35pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961 "2023-11-17T20:35:44Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![0xCam](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/0xcam/32/3628_2.png) [@0xCam](https://research.lido.fi/u/0xCam)\ **Post date:** [November 17, 2023, 8:35pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/1 "2023-11-17T20:35:44Z")
**Point of Contact:** [Arthur Remy](mailto:arthur.remy@consensys.net) - Linea, Product Manager [Cam O’Donnell](mailto:cameron.odonnell@consensys.net) - @0xCam - Linea, Product Growth Manager _This proposal is not considered completed and will be transparently updated as Linea works with contributors through testing and mainnet deployment._ * * * ## Intro Linea, a zkEVM developed by Consensys, submits this proposal to seek Lido DAO’s formal recognition of the [deployed wstETH token](https://lineascan.build/address/0xB5beDd42000b71FddE22D3eE8a79Bd49A568fC8F) as canonical on Linea and to request the DAO’s acceptance of ownership for the Lido-specific bridge contracts. This proposal is written in accordance with the [_Network Expansion Workgroup’s unofficial guidelines for bridging solutions_](https://research.lido.fi/t/unofficial-guidelines-for-bridging-solutions-network-expansion-workgroup/5790). ## Background & Rationale ### About Linea Linea results from more than 20 months of R&D by Consensys’s seasoned research team, known for their contributions to the zk space and active participation in the Merge. The network offers EVM equivalence, scalability, and reduced transaction costs while maintaining Ethereum’s security guarantees through Zero-Knowledge Proofs. Linea has seen consistent growth in TVL, reaching ~$140M on the network per [L2Beat](https://l2beat.com/scaling/projects/linea), and ~$33M in tracked protocols, according to [DeFiLlama](https://defillama.com/chain/Linea). This growth over 3.5 months signals an expanding ecosystem, further bolstered by ongoing activations and integrations with Consensys products. Notably, with Linea being a primary network in MetaMask and Consensys as one of Lido’s 36 infrastructure providers, we are uniquely positioned to explore synergistic integrations across Linea, Consensys products, and Lido. The proposed integration of wstETH into Linea aims to capitalize on this momentum, enhancing user experience through canonical issuance and, in turn, driving greater adoption and utility of wstETH on Linea. ### wstETH Demand [stETH](https://etherscan.io/token/0xae7ab96520de3a18e5e111b5eaab095312d7fe84) has become a cornerstone asset in the Ethereum ecosystem, boasting a market capitalization of $17B and over 250,000 holders. Acknowledging its essential role and the growing demand throughout the Ethereum community, its introduction into a new platform is strategically targeted to benefit stETH holders, particularly in the Layer 2 space. As a key asset, wstETH plays a vital role in DeFi activities across network segments. ## Technical Implementation ### Timeline The following key dates are targeted for this deployment. **Testnet Deployment** - **Completed:** November 10, 2023 - **Contracts:** Please see the Contract section **Mainnet Deployment** - **Completed** : November 30, 2023 - **Contracts:** Please see the Contract section **Governance Proposal** - **Target Date:** **December 8-9** , **2023** - **LeversSetUp:** Please see the Levers section ### Design Consensys, in collaboration with the _Lido Network Expansion Workgroup_, worked on deploying Lido-specific bridge components. These contracts facilitate the canonical bridging of wstETH, effectively connecting wstETH on Ethereum and Linea through Linea’s Canonical Bridge. This initiative involved a comprehensive analysis of existing contracts, consultation with subject matter experts, and using proven cross-chain governance contracts. The goal was to deploy while having the ability to enable Lido to accept control of the bridge token and its upgradability path. Shortly after launch, the Linea core team deployed a bridge upgradable wstETH token that complies with the ERC-20 standard, including a permit extension as per ERC-2612. This approach aimed to prevent token fragmentation while ensuring compliance with Lido DAO standards. The token representation has already integrated into the ecosystem with more than 600 wstETH across \>150 unique holders. To prevent cumbersome token and liquidity migrations, we propose that the best way forward is to reuse the compliant architecture as much as possible. When completing the governance process, we aim to call the ‘changeProxyAdmin” function on the tokens ProxyAdmin contract to transition control to the new ProxyAdmin contract on Linea under DAO control. In establishing a benchmark for cross-chain governance, our team implemented the `LineaBridgeExecutor` — a fork of the AAVE cross-chain governance bridge and in line with the precedent set on other deployments. A critical function of the `LineaBridgeExecutor` is to authenticate and validate cross-chain transactions, upholding the decisions ratified by Lido’s Onchain Governance. The Lido Agent will send messages directly to the Network’s Canonical Bridge (Linea Messaging Service), delivering the message to the LineaBridgeExecutor. \*\*\* _The LineaBridge Executor has been audited; please see the Audits section_ ![](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/9/9566fda767dd12b78abe414cc106e776b4785d54.png) ### Ownership | Contracts | Contract Type | Current Admin | Proposed Admin | | --- | --- | --- | --- | | `LineaBridgeExecutor` | Lido Component | - | DAO Agent L1 | | `ProxyAdmin` (wstETH) | Lido Component | - | `LineaBridgeExecutor` | | wstETH Token (_L2 - canonical bridge instance_) | Global | `ProxyAdmin` (bridge instance) | `ProxyAdmin` (Lido DAO instance) | | Linea Canonical bridge | Global | Linea Security Council | Linea Security Council | **Lido Specific Contracts –** The owner of Lido bridge components at deployment will be the Linea canonical bridge instance, controlled by the Linea Security Council, which will ensure the contracts initial deployment. However, if the DAO proposal passes, the ownership of these components will be transferred to the DAO. **Linea Canonical Bridge –** The Linea Canonical Bridge ownership will remain with the Linea Security Council. Currently, the Linea Security Council has 8 internal nonrelated parties. Additionally, it is important to note that the bridge instance can be changed as the token and solution architecture allow it. ### Emergency Handling The Linea Security Council holds the authority to pause operations of the entire bridge infrastructure in response to emergencies. Although this is not targeted at wstETH, it serves as a safeguard, ensuring the integrity and security of the network and related infrastructure. Currently, the Linea Security Council is made up of 8 internal nonrelated parties with a signature set ranging from 2-6 signers depending on the action. Linea is working to decentralize the Security Council further and expects updates in the first half of 2024. ### About the Linea Canonical Bridge At the core of Linea’s Canonical Bridge is the [Linea Message Service](https://docs.linea.build/architecture/canonical-msg-service), a set of smart contracts to facilitate data transfer between Linea and Ethereum. This service is not limited to Linea’s core functionality but is a general-purpose, public infrastructure that developers can use. Building on the Linea Message Service, is the [Token bridge](https://docs.linea.build/architecture/bridges/canonical-token-bridge), a standard lock and mint design, allowing for the transfer of assets from L1\<\>L2. The Linea Security Council oversees all Linea core contracts. The bridge includes an additional layer of logic that verifies the validity of messages. Specifically, when a message is sent from Ethereum to Linea, the Linea smart contract checks the message against a list of messages sent on the Ethereum side. Only after verifying its existence on the L1 does it accept the message as valid. The risk of fraudulent messages is minimized. \*\*\* _All aspects of the canonical bridge are audited; please see the Audits section_ ## Audits We have engaged with leading security firms to conduct thorough audits on all aspects of Linea, relevant to this proposal, our bridging infrastructure. In October 2023, Consensys Diligence completed an audit of the `LineaBridgeExecutor`. Consensys Diligence and OpenZeppelin provided comprehensive audits of the Canonical Token Bridge in October 2023 and June 2023, respectively. Any critical issues are remediated. | Audit Firm | Date | Contracts | Commit | | --- | --- | --- | --- | | Diligence | December 2023 | [Custom Bridged Token](https://consensys.io/diligence/audits/2023/12/linea-custom-bridged-token/) | _[Link](https://github.com/Consensys/linea-contracts/tree/3cf85529fd4539eb06ba998030c37e47f98c528a)_ | | OpenZeppelin | October 2023 | [Canonical Token Bridge](https://blog.openzeppelin.com/linea-bridge-audit-1?utm_source=immunefi) | _[Link](https://github.com/Consensys/linea-contracts-fix/tree/0949c4096664e613f73ed3ce51c32f97fc56cdef)_ | | Diligence | October 2023 | [LineaBridgeExecutor](https://consensys.io/diligence/audits/private/1zps18ccw1anbm/) | _[Link](https://github.com/Consensys/governance-crosschain-bridges/commit/315308a2640c696937185732159b130417f29997)_ | | DIligence | June 2023 | [Canonical Token Bridge](https://consensys.io/diligence/audits/2023/06/linea-canonical-token-bridge/?utm_source=immunefi) | _[Link](https://github.com/Consensys/linea-token-bridge/tree/894686a30003de27a355ae8119e3b95b5bdd73b8)_ | | Diligence | June 2023 | [Linea Message Service](https://consensys.io/diligence/audits/2023/06/linea-message-service/?utm_source=immunefi) | _[Link](https://github.com/ConsenSys/zkevm-monorepo/commit/8ccf24731c3cd288c27696771c45e4c1a01fa8cc)_ | | Mixed | - | [All other audits](https://immunefi.com/bounty/linea/) | | ## Contracts - Supporting scripts are under review in Lido git - [Acceptance Tests](https://github.com/lidofinance/governance-crosschain-bridges/blob/4760f80e79122a5d73ad9f73d016cde3e21f9781/test/fork/crosschain-bridges.spec.ts) ### Testnet Ethereum Goerli - DAO Agent on L1: [0x4333218072D5d7008546737786663c38B4D561A4](https://goerli.etherscan.io/address/0x4333218072D5d7008546737786663c38B4D561A4) - wstETH on L1: [0x6320cd32aa674d2898a68ec82e869385fc5f7e2f](https://goerli.etherscan.io/token/0x6320cd32aa674d2898a68ec82e869385fc5f7e2f) - L1 Token Bridge (_dedicated wstETH test instance_): [0xaa012d038e6440535ec66edf2da592f4f8398133](https://goerli.etherscan.io/address/0xaa012d038e6440535ec66edf2da592f4f8398133) Linea Goerli - LineaBridgeExecutor: [0x4b38d24e70079f2dd1d79b86e2b52f4b13872a3b](https://goerli.lineascan.build/address/0x4b38d24e70079f2dd1d79b86e2b52f4b13872a3b#code) - ProxyAdmin for wstETH : [0x71062fbc3da2d792285c3d5dabba12a42339e85c](https://goerli.lineascan.build/address/0x71062fbc3da2d792285c3d5dabba12a42339e85c#writeContract) - wstETH (_for testing_): [0x9ceed01e39279a529f44deb9d35e09a04b1e67c8](https://goerli.lineascan.build/address/0x9ceed01e39279a529f44deb9d35e09a04b1e67c8#code) - L2 Token Bridge (_dedicated wstETH test instance_): [0xB191E3d98074f92584E5205B99c3F17fB2068927](https://goerli.lineascan.build/address/0xb191e3d98074f92584e5205b99c3f17fb2068927) ### Mainnet Ethereum - DAO Agent on L1: [0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - wstETH on L1: [0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0](https://etherscan.io/token/0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0) - L1 Token Bridge (_Canonical Bridge_): [0x051f1d88f0af5763fb888ec4378b4d8b29ea3319](https://etherscan.io/address/0x051f1d88f0af5763fb888ec4378b4d8b29ea3319) Linea - LineaBridgeExecutor: [0x74Be82F00CC867614803ffd7f36A2a4aF0405670](https://lineascan.build/address/0x74Be82F00CC867614803ffd7f36A2a4aF0405670#code) - ProxyAdmin for wstETH: [0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927](https://lineascan.build/address/0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927#code) - wstETH on L2: [0xB5beDd42000b71FddE22D3eE8a79Bd49A568fC8F](https://lineascan.build/address/0xB5beDd42000b71FddE22D3eE8a79Bd49A568fC8F) - L2 Token Bridge (_Canonical Bridge_): [0x353012dc4a9a6cf55c941badc267f82004a8ceb9](https://lineascan.build/address/0x353012dc4a9a6cf55c941badc267f82004a8ceb9) ### Levers setup (provided by NEW) - or the [`Linea Bridge Executor`](https://lineascan.build/address/0x74Be82F00CC867614803ffd7f36A2a4aF0405670) - `getEthereumGovernanceExecutor` is the [`Lido DAO Agent`](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - A bridge admin and `owner` on L1 is the [`Linea Security Council`](https://etherscan.io/address/0x892bb7EeD71efB060ab90140e7825d8127991DD3) - proxy admin for L1 TokenBridge - `owner` for L1 TokenBridge - A bridge admin and `owner` on L2 is the [`Linea Security Council`](https://lineascan.build/address/0xf5cc7604a5ef3565b4d2050d65729a06b68aa0bd) - Proxy admin for L2 TokenBridge - `owner` for L2 TokenBridge - For the proposed wstETH token on L2 ([CustomBridgedToken](https://lineascan.build/address/0xB5beDd42000b71FddE22D3eE8a79Bd49A568fC8F)) - ⚠ Currently, the [`Linea Security Council`](https://lineascan.build/address/0xf5cc7604a5ef3565b4d2050d65729a06b68aa0bd) is the proxy admin. The plan is to transition this role to the [`Linea Bridge Executor`](https://lineascan.build/address/0x74Be82F00CC867614803ffd7f36A2a4aF0405670) upon snapshot approval, leveraging a newly deployed [`ProxyAdmin`](https://lineascan.build/address/0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927) instance. ### Next Steps Following the submission of this proposal, as we continue to update details of the deployment, we invite the community to engage in review and provide feedback. **When applicable,** We also ask core contributors to evaluate the details presented, representing the interests of the Lido DAO. We are committed to transparency throughout this phase and look forward to discussion. ### Additional Links - [Linea Website](http://linea.build/) - [Linea Block Explorer](https://lineascan.build/) - [Linea Docs](https://docs.linea.build/architecture) - [Linea Mirror](https://linea.mirror.xyz/) - [Consensys: R&D](https://consensys.net/research-and-development/) - [Consensys R&D Gnark Library](https://github.com/consensys/gnark) - [Vortex: Building a Lattice-based SNARK scheme…](https://eprint.iacr.org/2022/1633) - [Ethresearch.ch - A ZK-EVM specification](https://ethresear.ch/t/a-zk-evm-specification-part-2/13903) - [Vitalik - A rollup-centric Ethereum roadmap](https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698) #### Update Log 1. **23/11/23 -** Updated the mainnet contract links from the Linea Message service contracts to the appropriate bridge contracts. 2. **03/12/23 -** Updated the links for deployed contracts on Linea mainnet (“LineaBridgeExecutor”, " ProxyAdmin"). Ownership of the ProxyAdmin has been given to the LineaBridgeExecutor. 3. **05/12/23 -** Updated Contract audit links to appropriate audit commits. 4. **05/12/23 -** Updated expected vote date, as the linea core team engaged to obtain a more streamlined and corrected audit reporting for the `Canonical Token Bridge` contract. 5. **06/12/23 -** Updated the corrected Audit report final commit and added Levers set up provided by NEW ---
**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 21, 2023, 8:56pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/2 "2023-11-21T20:56:25Z")
Hey, @0xCam I personally consider this proposal favorably as it presents a forward-thinking approach to bridging wstETH to Linea: - the bridged token is upgradeable - governance decision forwarder introduced - the `TokenBridge` instance has the flexibility of replacement in the future if required to pass additional data and/or implement additional logic (hope to share more updates till EOY on the path forward for network expansion forthcoming product-wise proposals) Currently, both [NEW](https://research.lido.fi/t/unofficial-guidelines-for-bridging-solutions-network-expansion-workgroup/5790) contributors and the [MixBytes](https://research.lido.fi/t/unofficial-guidelines-for-bridging-solutions-network-expansion-workgroup/5790/2) team are engaged in the evaluation and verification process. I’ll share more updates in this thread as they become available. ---
**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:** [December 6, 2023, 8:18am UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/3 "2023-12-06T08:18:54Z")
[MixBytes](https://mixbytes.io/) team was engaged and has verified wstETH deployment on Linea. Three security researchers checked the presented information according to the internal checklist. The results are as follows: - Linea rollup fully supports all EVM opcodes as they are, but state transition proof generation is carried out via a private circuit, which currently [does not support all EVM features](https://docs.linea.build/risk-disclosures#the-journey-towards-decentralization). That is okay for now, as proof verification is permissioned, but the Linea team should address it in the future. - Linea decided to use a general-purpose bridge to transfer wstETH, bringing additional complexity to the bridge’s architecture and implementation. Lido DAO will need to update wstETH on L2 to pause bridging tokens from L2 to L1 (there is no way that Lido DAO can pause bridging from L1 to L2). Bridge architecture allows users to move wstETH from L1 to L2 and back safely, according to several audit reports received by the Linea team, but Lido DAO will not have full control over wstETH in this design. - Deployed contracts match the audited scope. Most of the findings from the audit reports are fixed, but it is possible to cause [DoS in TokenBridge](https://blog.openzeppelin.com/linea-bridge-audit-1#rate-limiters-can-lead-to-a-denial-of-service-attack) which can be fixed by updating the limit parameter by Linea team. - The audit report for the TokenBridge contract doesn’t have clear information about the commit with all fixes verified by OpenZeppelin. - All contracts were correctly deployed and initialized. [ProxyAdmin](https://lineascan.build/address/0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927) contains unnecessary contracts in the verification section. - ProxyAdmin for wstETH on L2 is set to [this address](https://lineascan.build/address/0xa11ba93afbd6d18e26fefdb2c6311da6c9b370d6) but should be set to the [address](https://lineascan.build/address/0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927) (Linea team should update it after successful proposal passing) ---
**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:** [December 6, 2023, 3:15pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/4 "2023-12-06T15:15:26Z")
The tech wing representatives of the [NEW](https://research.lido.fi/t/unofficial-guidelines-for-bridging-solutions-network-expansion-workgroup/5790) (@TheDZhon and @arwer13) have evaluated the proposal and the artifacts presented, leading to the following observations: - The [proposed contracts](https://docs.lido.fi/deployed-contracts/#linea) utilize Linea’s canonical native bridge instance. This architecture, distinct from the usual custom token gateways used for wstETH on L2, involves using a shared bridge instance managed by Linea. Importantly, the token’s upgradeability is maintained, with the token proxy admin being separate from the bridge admin instance. This approach aligns with the unofficial guidelines presented by [NEW](https://research.lido.fi/t/unofficial-guidelines-for-bridging-solutions-network-expansion-workgroup/5790) and is future-ready for wstETH. However, it may introduce added complexity in implementing specific Lido protocol mechanisms in the future (e.g., integrating wstETH/stETH in-protocol rate or introducing a canonical rebasable stETH token representation on Layer 2). - The deployment preserves the integrity with the audits presented (source code, and bytecode wise, with no critical issues left unresolved, and only a single HIGH finding acknowledged having a tolerable impact on the wstETH token bridge accessibility), the following [commit #0949c409](https://github.com/Consensys/linea-contracts-fix/tree/0949c4096664e613f73ed3ce51c32f97fc56cdef) was referenced for deployment checks; as suggested by @DZahar0v, it’s advisable to ensure this commit is included in the audit report by OZ. - All configurations and parameters look appropriate and meet expectations - The levers and proxy admins are prepared to transfer the ownership of the wstETH token contract to the Lido DAO, contingent on successful snapshot approval. * * * ACL and levers setup: - For the [`Linea Bridge Executor`](https://lineascan.build/address/0x74Be82F00CC867614803ffd7f36A2a4aF0405670) - `getEthereumGovernanceExecutor` is the [`Lido DAO Agent`](https://etherscan.io/address/0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c) - A bridge admin and `owner` on L1 is the [`Linea Security Council`](https://etherscan.io/address/0x892bb7EeD71efB060ab90140e7825d8127991DD3) - proxy admin for L1 TokenBridge - `owner` for L1 TokenBridge - A bridge admin and `owner` on L2 is the [`Linea Security Council`](https://lineascan.build/address/0xf5cc7604a5ef3565b4d2050d65729a06b68aa0bd) - Proxy admin for L2 TokenBridge - `owner` for L2 TokenBridge - For the proposed wstETH token on L2 ([CustomBridgedToken](https://lineascan.build/address/0xB5beDd42000b71FddE22D3eE8a79Bd49A568fC8F)) - ⚠ Currently, the [`Linea Security Council`](https://lineascan.build/address/0xf5cc7604a5ef3565b4d2050d65729a06b68aa0bd) is the proxy admin. The plan is to transition this role to the [`Linea Bridge Executor`](https://lineascan.build/address/0x74Be82F00CC867614803ffd7f36A2a4aF0405670) upon snapshot approval, leveraging a newly deployed [`ProxyAdmin`](https://lineascan.build/address/0xF951d7592e03eDB0Bab3D533935e678Ce64Eb927) instance. - No dedicated emergency breaks msig are allocated or assigned with this proposal * * * We would propose the Lido DAO accepting the wstETH token deployment on Linea as a canonical one supporting the Ethereum ecosystem scaling endeavor. ---
**Author:** ![Jenya\_K](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/jenya_k/32/2672_2.png) [@Jenya\_K](https://research.lido.fi/u/Jenya_K)\ **Post date:** [December 8, 2023, 8:01am UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/5 "2023-12-08T08:01:19Z")
Happy to announce that the Snapshot [Should the Lido DAO recognize the wstETH Bridge Endpoints on Linea as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x9382624eeee68a175dd7d1438347dbad4899ba0d2bfcf7c3955f087cb9f5cfc4) has started! Please cast your votes before Thu, 14 Dec 2023 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:** [December 14, 2023, 4:06pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/6 "2023-12-14T16:06:45Z")
## Snapshot vote ended The [Should the Lido DAO recognize the wstETH Bridge Endpoints on Linea as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x9382624eeee68a175dd7d1438347dbad4899ba0d2bfcf7c3955f087cb9f5cfc4) Snapshot hadn’t reached a quorum. 😔 The results are: **Recognize** : 47.3M LDO **Don’t recognize** : 34.8k LDO ---
**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:** [December 18, 2023, 1:16pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/7 "2023-12-18T13:16:08Z")
## Snapshot vote started The [[rerun] Should the Lido DAO recognize the wstETH Bridge Endpoints on Linea as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2e0a975282d741aaedc7bd80cee24986da67671e84d9cf9fb10da527ef5d1177) Snapshot has started! Please cast your votes before Mon, 25 Dec 2023 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:** [December 25, 2023, 4:06pm UTC](https://research.lido.fi/t/wsteth-on-linea-ownership-acceptance-by-lido-dao/5961/8 "2023-12-25T16:06:19Z")
## Snapshot vote ended The [[rerun] Should the Lido DAO recognize the wstETH Bridge Endpoints on Linea as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2e0a975282d741aaedc7bd80cee24986da67671e84d9cf9fb10da527ef5d1177) Snapshot vote concluded! The results are: **Recognize** : 51.4M LDO **Don’t recognize** : 91 LDO