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

Upcoming Events

Old Billingsgate

Mon - Wed, October 13 - 15, 2025

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.

Industry City | Brooklyn, NY

TUES - THURS, JUNE 24 - 26, 2025

Permissionless IV serves as the definitive gathering for crypto’s technical founders, developers, and builders to come together and create the future.If you’re ready to shape the future of crypto, Permissionless IV is where it happens.

Brooklyn, NY

SUN - MON, JUN. 22 - 23, 2025

Blockworks and Cracked Labs are teaming up for the third installment of the Permissionless Hackathon, happening June 22–23, 2025 in Brooklyn, NY. This is a 36-hour IRL builder sprint where developers, designers, and creatives ship real projects solving real problems across […]

recent research

Research Report Templates.png

Research

The convergence of DePIN and energy generation aims to address modern grid challenges by incentivizing distributed generation.

article-image

While Arizona’s governor could veto another crypto reserve bill, similar North Carolina and Texas laws are approaching the finish line

article-image

However, they noted there’s now an increased risk that unemployment and inflation will rise in the coming months. 

article-image

The network’s most ambitious upgrade since the Merge brings validator streamlining, smart account UX and doubled blobspace to Ethereum

article-image

Debate over extra Bitcoin use cases has returned, two years on from Ordinals

article-image

Altcoin season may be on a permanent pause as the market matures and paths grow more selective