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

by Bessie Liu /
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

Digital Asset Summit 2025

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.

buy ticketslearn more

recent research

Research

by Research Team

news

article-image

Policy

Federal judge denies Ripple, SEC motion for indicative ruling

Judge Analisa Torres said the parties have not demonstrated that vacating her prior ruling is in the best interest of the public

by Casey Wagner /
article-image

Empire NewsletterOpinion

Why Kalshi’s new $2B valuation makes sense

Prediction markets have found a mainstream fit

by Katherine Ross /
article-image

The Breakdown

Permissionless IV, Day 2 takeaways

Money for enemies isn’t fun, but crypto can be

by Byron Gilliam /
article-image

Lightspeed NewsletterMarkets

Risk-on in Solana, even as ceasefire cools tensions

Onchain SOL perps wiped $31 million, outpacing CEX volumes two days in a row

by Jeff Albus /
article-image

Forward Guidance NewsletterPolicy

Powell says Fed will continue to monitor inflation before cutting rates

Fed Chair Jerome Powell told Senators Wednesday that the timeline on lowering interest rates is up in the air

by Casey Wagner /
article-image

FinanceForward Guidance Newsletter

Newly tokenized Janus Henderson CLO strategy sees $1B inflow

Credit infrastructure DeFi protocol Grove makes allocation into a CLO segment “ripe for movement into DeFi”

by Ben Strack /