Google Launches Blockchain Node Engine, Says ‘Ethereum Will Be the First Blockchain Supported’

After revealing Alphabet Inc.’s Google Cloud partnership with Coinbase, the multinational technology conglomerate holding company has announced the firm’s “Google Cloud Blockchain Node Engine.” While more blockchains will be supported, Google said that “Ethereum will be the first blockchain supported by Blockchain Node Engine.”

Google Launches Cloud-Based Blockchain Node Engine

Alphabet Inc., otherwise known as Google (Nasdaq: GOOGL), revealed the firm’s newly launched Google Cloud Blockchain Node Engine on Thursday. The reason Google decided to release the engine is because it believes “self-managed nodes are often difficult to deploy and require constant management.”

The Blockchain Node Engine product is a “fully managed node-hosting service” that can be leveraged by crypto companies and Web3 service providers. The company further detailed on Thursday that the new node engine service will support the second-leading crypto asset network by market cap, Ethereum.

“Ethereum will be the first blockchain supported by Blockchain Node Engine, enabling developers to provision fully managed Ethereum nodes with secure blockchain access,” the tech company said in the recently published blog post.

The news follows Google’s recent partnership with Coinbase in order to drive Web3 innovation. With the latest blockchain engine product, “Web3 companies who require dedicated nodes can relay transactions, deploy smart contracts, and read or write blockchain data with the reliability, performance, and security they expect from Google Cloud compute and network infrastructure.”

Moreover, a Blockdata study shows that Google is one of the top investors in blockchain technology as it invested in firms like Fireblocks, Digital Currency Group (DCG), Dapper Labs, and Vultage. The tech giant’s entry into the world of decentralized finance (defi) and Web3 was revealed last May when it formed a Web3 team within its cloud unit.

“We’re providing technologies for companies to use and take advantage of the distributed nature of Web3 in their current businesses and enterprises,” a Google spokesperson said at the time. The latest node engine offering announcement says the service aims to provide “streamlined provisioning,” “secure development,” and “fully managed operations.”

“By reducing the need for a dedicated Devops team, and by offering Google Cloud’s service level agreement (SLA), Blockchain Node Engine can let your team focus on your users instead of your infrastructure,” Google’s blog post concludes. We look forward to supporting organizations with a reliable, easy-to-use blockchain node hosting service so they can focus their time on innovating and scaling their Web3 applications.

Tags in this story
Bitcoin, Coinbase, coinbase web3, Crypto, Cryptocurrency, Dapper Labs, Digital Currency Group (DCG), Fireblocks, Google, google accepts crypto, google blockchian, Google Cloud, Google Cloud Coinbase, Google Cloud Coinbase partner, Google Cloud crypto, Google Cloud cryptocurrency, Google Cloud web3, google cryptocurrencies, Google web3, Node, node service, Vultage, Web3

What do you think about Google’s Blockchain Node Engine product? Let us know your thoughts about this subject in the comments section below.

Jamie Redman

Jamie Redman is the News Lead at Bitcoin.com News and a financial tech journalist living in Florida. Redman has been an active member of the cryptocurrency community since 2011. He has a passion for Bitcoin, open-source code, and decentralized applications. Since September 2015, Redman has written more than 6,000 articles for Bitcoin.com News about the disruptive protocols emerging today.




Image Credits: Shutterstock, Pixabay, Wiki Commons

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

Read disclaimer

Source