Google Cloud is LayerZero’s new default oracle operator

A total of 15 different blockchains will be able to rely on Google Cloud oracles for cross-chain interoperability

article-image

JHVEPhoto/Shutterstock modified by Blockworks

share

Cross-chain messaging protocol LayerZero has partnered with Google Cloud to further enhance its infrastructure.

Google Cloud will be the default oracle provider for LayerZero, meaning that any dapps on LayerZero will automatically use Google Cloud to verify transactions sent across blockchains, though they will still have the choice to use other providers. 

Oracles are a key part of blockchain infrastructure. They are responsible for connecting blockchains to external systems and sending real-world information in and out of a network.

LayerZero is an open permissionless protocol that enables decentralized app developers to decide who secures the messages between different blockchains. A total of 15 different blockchains can utilize this new cross-chain environment, including Ethereum, Arbitrum, Polygon, BNB and Avalanche.

If developers have Google Cloud selected as their oracle provider, local call messaging has to be approved by Google Cloud in order for it to be verified, Ryan Zarick, co-founder and chief technology officer of LayerZero told Blockworks.

“There’s no way an attack can happen without [Google Cloud] being compromised as well,” Zarick said.

Unlike running a single validator in Solana or Ethereum and not having the ability to stop attacks, Google Cloud will have the ability to veto the attack, Zarick explained.

“Cross-chain messaging always boils down to some level of trust, so there is no way that you can achieve trustless cross-chain messaging,” he said.

Node operators on LayerZero can introduce latency measures, but ultimately because applications have the choice to choose other oracle providers, messages themselves can never completely be censored. 

“The way LayerZero is built is that every message is sequentially nonce order enforced, what that means is that if you sent a message first and I sent one, mine can’t get delivered until yours gets there,” Zarick said. “That’s enforced by code, so transactions can’t be taken out unless they turn off the entire messaging link.”


Get the news in your inbox. Explore Blockworks newsletters:

Tags

Decoding crypto and the markets. Daily, with Byron Gilliam.

Upcoming Events

Javits Center North | 445 11th Ave

Tues - Thurs, March 24 - 26, 2026

Blockworks’ Digital Asset Summit (DAS) will feature conversations between the builders, allocators, and legislators who will shape the trajectory of the digital asset ecosystem in the US and abroad.

recent research

Research Report Templates (3).png

Research

South Korea is emerging as one of the most important global hubs for regulated digital assets, and Upbit sits at the center of this shift. Naver’s proposed acquisition could create the country’s dominant super app for payments, trading, and digital finance. This report breaks down the numbers, the regulatory tailwinds, the economics of the deal, and why the merger may unlock one of the most attractive asymmetries in Korea’s public markets.

article-image

Lido unveils a new buyback plan while BTC treasury companies slip below mNAV — can either model can truly return value?

article-image

If financial nihilism has driven you into memecoins, zero-day options, and sports betting, consider financial optimism instead

article-image

A new Sui-based protocol promises to unlock Bitcoin’s idle liquidity and eliminate wrapped-token risk

article-image

Could blockchain rails finally realize Ted Nelson’s non-linear, pro-creator “docuverse”?

article-image

What does Uniswap’s proposal to activate protocol fees and unify incentives mean for UNI token holders?

article-image

A recent mistrial illustrates how juries need more background information when it comes to judging complex systems like Ethereum