Google Makes Ethereum Dataset Publicly Available in BigQuery

Internet giant Google has now made ethereum dataset publicly available to its big data analytics platform BigQuery, after adding Bitcoin dataset earlier this year. Google BigQuery is a cloud-based web service for processing very large read-only data sets. The company said that all historical data, including daily updates, will be publicly available on the Ethereum blockchain dataset.

If further added that while the Ethereum blockchain peer-to-peer (P2P) software has an application program interface (API) for a subset of commonly used random-access functions (for example: checking transaction status, looking up wallet-transaction associations, and checking wallet balances), API endpoints don’t exist for easy access to all of the data stored on-chain. API endpoints also don’t exist for viewing the blockchain data in aggregate. Aiming the new service to provide more of a Big Data window into ethereum.

The giant has built a software system on Google Cloud that synchronizes the Ethereum blockchain to computers running Parity in Google Cloud, performs a daily extraction of data from the Ethereum blockchain ledger, including the results of smart contract transactions, such as token transfers, and de-normalizes and stores date-partitioned data to BigQuery for easy and cost-effective exploration.

Google then demonstrated a few examples. The first of which was CryptoKitties (a crypto collectibles game), for which it visualized the CryptoKitty pedigree for accounts that own at least 10 CryptoKitties – Color indicated owner, while size indicated the PageRank (reproductive fitness) of each CryptoKitty. Another example was a look at one of the most popular tokens is OmiseGO ($OMG), with a visualization that shows how on September 13, 2017, there was a large increase in the number of $OMG receivers but no increase in the number of senders. This corresponds to the beginning of the OmiseGO Token Airdrop.

Continue Reading

Leave a Reply

Your email address will not be published. Required fields are marked *