Bridging protocols express 'concern' over LayerZero's wstETH token integration

Quick Take

  • Interoperability protocols gathered together to express “concern” over LayerZero’s issuance of a wstETH OFT standard. 
  • “We believe this action is the direct consequence of a broken system of incentives around interoperability that can only be fixed through standardization and healthy competition at every layer of the bridge stack,” the protocols wrote in a joint statement. 

Interoperability protocol LayerZero is facing a backlash for the way it portrayed the integration of wstETH on its omnichain fungible token (OFT) standard, a technology that's designed to move the token across three new blockchains.

Interoperability projects including Connext Network, ChainSafe and Sygma announced a unified call for open bridge standards in a Friday statement, claiming that OFTs endorse vendor lock-ins and that "token-issuing DAOs should be the ultimate arbiters of what version of their asset is canonical on a given chain.”

"As a group of leading interoperability projects, we would like to express concern about the recent actions of LayerZero, their deployment of a proprietary representation of wstETH to Avalanche, BNB Chain and Scroll without support from the Lido DAO," the interoperability protocols wrote. "We believe this action is the direct consequence of a broken system of incentives around interoperability that can only be fixed through standardization and healthy competition at every layer of the bridge stack.” 

The tension is between LayerZero's ability to create this token — which it can do across permissionless systems — and the question of whether Lido's governance officially endorses it.

THE SCOOP

Keep up with the latest news, trends, charts and views on crypto and DeFi with a new biweekly newsletter from The Block's Frank Chaparro

By signing-up you agree to our Terms of Service and Privacy Policy
By signing-up you agree to our Terms of Service and Privacy Policy

A crypto researcher known as Hasu, who is a strategic advisor for LidoDAO, said they were speechless about LayerZero's approach.

"By unilaterally deploying a bridge and marketing it in an official-seeming way, it feels like you are trying to pressure the DAO into accepting your proposal to avoid liquidity fragmentation and bad UX for users," Hasu added. "Driving users to it through marketing makes accepting an alternate bridge proposal more painful. These actions put the DAO, Lido stakers, and participating chains in a difficult position."

Responding to the backlash

Regarding the community response, LayerZero told The Block that, "the omnichain fungible-token standard is a multi-audited, open source set of reference contracts used by more than 75 projects to enable native, horizontally composable transfers between L1s and between L2s. More than $3 billion in value has been transferred by contracts that have integrated OFT."

"By design, developers always maintain the ability to permissionlessly select their validation layer and can include other bridges as part of the immutable LayerZero framework. Once the Lido DAO accepts ownership of the contracts, wstETH on AVAX and BNB, a deployment organized with encouragement and feedback from Lido core team members, is entirely owned by Lido with no reliance on LayerZero Labs," it added.


© 2023 The Block. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

About Author

MK Manoylov has been a reporter for The Block since 2020 — joining just before bitcoin surpassed $20,000 for the first time. Since then, MK has written nearly 1,000 articles for the publication, covering any and all crypto news but with a penchant toward NFT, metaverse, web3 gaming, funding, crime, hack and crypto ecosystem stories. MK holds a graduate degree from New York University's Science, Health and Environmental Reporting Program (SHERP) and has also covered health topics for WebMD and Insider. You can follow MK on X @MManoylov and on LinkedIn.

Editor

To contact the editor of this story:
Tim Copeland at
[email protected]