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

Unlocked by Template.png

Research

The march toward an interoperable and onchain-by-default internet depends on reliable messaging and value transfer across heterogeneous domains. Crosschain protocols now process >$1.3T in combined annual transfer volume and secure tens of millions of user interactions, yet no single design dominates.

article-image

The goal, per Santiago Santos, is to make crypto a relatable piece of tech for people who may not even understand it

article-image

Stripe stablecoin unit aims to operate under a federal charter enabling regulated stablecoin issuance and custody services

by Blockworks /
article-image

Will TradFi make crypto better or create more problems than it solves?

article-image

Subtle decisions by risk curators saved Aave from significant turmoil

article-image

The new Rootstock Institutional unit aims to connect professional investors to Bitcoin-native yield and liquidity strategies anchored in BTC’s security layer

by Blockworks /
article-image

DOJ files record civil forfeiture against more than 127,000 BTC linked to scam activity

by Blockworks /