The Graph Protocol Smart Contracts are a set of Solidity contracts that exist on the Ethereum Blockchain. The contracts enable an open and permissionless decentralized network that coordinates Graph Nodes to Index any subgraph that is added to the network. Graph Nodes then provide queries to users for those Subgraphs. Users pay for queries with the Graph Token (GRT).
The protocol allows Indexers to Stake, Delegators to Delegate, and Curators to Signal on Subgraphs. The Signal informs Indexers which Subgraphs they should index.
You can learn more by heading to the documentation, or checking out some of the blog posts on the protocol.
The contracts are upgradable, following the Open Zeppelin Proxy Upgrade Pattern. Each contract will be explained in brief detail below.
Curation
Allows Curators to Signal GRT towards a Subgraph Deployment they want indexed on The Graph. Curators are often Subgraph Developers, but anyone can participate. Curators also receive a portion of the query fees that are earned on the Subgraph. Signaled GRT goes into a bonding curve, which returns a Graph Curation Share (GCS) to the Curator.
Graph Name Service (GNS)
Wraps around the Curation contract to provide pooling of Curator Signaled tokens towards a single Subgraph. This allows an owner to deploy a Subgraph, and upgrade their Subgraph to a new version. The upgrade will move all Curator tokens to a new Subgraph Deployment with a new bonding curve.
Service Registry
Allows Indexers to tell the network the location of their node. This allows end users to choose a node close to themselves, lowering the latency for queries.
Dispute Manager
Provides a way for Indexers to be slashed or incorrect or malicious behaviour. There are two types of disputes: Query Disputes and Indexing Disputes.
Epoch Manager
Keeps track of protocol Epochs. Epochs are configured to be a certain block length, which is configurable by The Governor.
Controller
The Controller is a contract that has a registry of all protocol contract addresses. It also is the owner of all the contracts. The owner of the Controller is The Governor, which makes The Governor the address that can configure the whole protocol. The Governor is The Graph Council.
Rewards Manager
Tracks how inflationary GRT rewards should be handed out. It relies on the Curation contract and the Staking contract. Signaled GRT in Curation determine what percentage of inflationary tokens go towards each subgraph. Each Subgraph can have multiple Indexers Staked on it. Thus, the total rewards for the Subgraph are split up for each Indexer based on much they have Staked on that Subgraph.
Staking
The Staking contract allows Indexers to Stake on Subgraphs. Indexers Stake by creating Allocations on a Subgraph. It also allows Delegators to Delegate towards an Indexer. The contract also contains the slashing functionality.
Graph Token
An ERC-20 token (GRT) that is used as a work token to power the network incentives. The token is inflationary.
The NPM package contains contract interfaces and addresses for the testnet and mainnet. It also contains typechain generated objects to easily interact with the contracts. This allows for anyone to install the package in their repository and interact with the protocol. It is updated and released whenever a change to the contracts occurs.
yarn add @graphprotocol/contracts
The testnet runs on Goerli, while mainnet is on Ethereum Mainnet. The addresses for both of these can be found in ./addresses.json.
To setup the contracts locally, checkout the dev branch, then run:
yarn
yarn buildFor testing details see TESTING.md.
In order to run deployments, see DEPLOYMENT.md.
There are three ways to interact with the contracts through this repo:
The most straightforward way to interact with the contracts is through the hardhat console. We have extended the hardhat runtime environment to include all of the contracts. This makes it easy to run the console with autocomplete for all contracts and all functions. It is a quick and easy way to read and write to the contracts.
# A console to interact with testnet contracts
npx hardhat console --network goerli
There are hardhat tasks under the /tasks folder. Most tasks are for complex queries to get back data from the protocol.
There is a CLI that can be used to read or write to the contracts. It includes scripts to help with deployment.
When running the Hardhat console or tasks you can set what network and accounts to use when sending transactions.
Selecting a network requires just passing --network <name> when running Hardhat. It's important that the network exists in the Hardhat configuration file.
There is a special network called localhost that connects it to a node running on localhost.
The accounts used depends on a few environment variables:
- If MNEMONIC is set you will have available the set of addresses derived from the seed.
- If PRIVATE_KEY is set, just that account is imported. MNEMONIC always takes precedence over PRIVATE_KEY.
- If no MNEMONIC or PRIVATE_KEY is set it will use the remote accounts from the provider node.
- You can always get an account using
ethers.getSigner(<address>)
Considerations when forking a chain:
- When running on the
localhostnetwork it will use by default a deterministic seed for testing purposes. If you want to connect to a local node that is forking while retaining the capability to impersonate accounts or use local accounts you need to set the FORK=true environment variable.
Copyright © 2021 The Graph Foundation
Licensed under GPL license.