Welcome to another week of Bitcoin all-time highs. Get used to hearing it, because I’m not going to stop saying it. With the vacation break, some might have expected the markets to cool off. But, Bitcoin ain’t got time for that… Dollar-cost averaging into Bitcoin over the past years has been great. But, for all that live and breathe crypto every day, we’re still waiting for the retail investment party to start. That crazy, mind-numbing sick gains altcoin party! With some amazing projects added to your radar already this year, it’s time to introduce a new project that recently rolled out mainnet, and immediately hit the ground running. With this week’s review of the highly anticipated project, The Graph.
Introduction
The Graph is focused on creating an indexing protocol for querying networks like Ethereum and IPFS (InterPlanetary File Systems). A decentralized network where anyone can build and publish open APIs, called sub-graphs, to make data more accessible. These subgraphs can then be composed into a global graph of all the world’s public information. Data can be transformed, organized, and shared across many applications for anyone to query with a few simple inputs. The Graph learns what, and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph manifest defines the smart contracts of interest for a subgraph, the events in those contracts to report, and how to map this event data to record information that The Graph will then store in its database. This database is then made accessible to everyone on the Ethereum network. Once a user has written a subgraph manifest, anyone can use the Graph CLI (Command-Line Interface) to access stored manifest definitions in IPFS. Utilizing the interface and telling the hosted service to start indexing data for that specific subgraph. This allows anyone to set a defined real-time measurement of anything happening in a dApp through a system of simple query-based transactions.
DApps are requiring higher and higher amounts of data to interact with users and operate base functions. As each transaction creates events between the user and dApp contract, functions of dApps are beginning to slow down due to lag. To help solve these issues, The Graph Node is always scanning Ethereum for new blocks of data defined by the subgraph parameters. The Graph Node then finds Ethereum events for your subgraph in these blocks and runs the mapping handlers you provided. The mapping is done using a WASM (WebAssembly) module that modifies data entities that The Graph Node stores in response to Ethereum events. DApps can query The Graph Node for data indexed from the blockchain, using the node’s GraphQL endpoint. The Graph Node in turn translates the GraphQL queries into queries for its underlying data in order to fetch this data, making use of the store’s indexing capabilities. The decentralized application then displays this data for end-users, which they can use to issue new transactions on Ethereum. If you don’t have an account on Graph Explorer, you can signup with GitHub. Once you create an account, you can start creating subgraphs through the UI, and deploying them from your terminal. The Graph Node supports many Ethereum testnets including Rinkeby, Ropsten, Goerli, PoA-Core, xDAI, Sokol, and Kovan in addition to mainnet. Once a subgraph is…
Hi! My name is Lark Davis!
I’m a cryptocurrency investor with years of experience and I’ve been making consistent profits in the crypto space.
I’m passionate about helping others do the same, so I run multiple educational channels on crypto investing.
