# Table of Contents - [Protocol Contracts | Docs | The Graph](#protocol-contracts-docs-the-graph) - [Hypergraph | Docs | The Graph](#hypergraph-docs-the-graph) - [The Graph's AI | Docs | The Graph](#the-graph-s-ai-docs-the-graph) - [Quick Start | Docs | The Graph](#quick-start-docs-the-graph) - [Substreams Quick Start | Docs | The Graph](#substreams-quick-start-docs-the-graph) - [Ethereum Mainnet | Docs | The Graph](#ethereum-mainnet-docs-the-graph) - [Glossary | Docs | The Graph](#glossary-docs-the-graph) - [Bitcoin Mainnet | Docs | The Graph](#bitcoin-mainnet-docs-the-graph) - [Graph Horizon Overview | Docs | The Graph](#graph-horizon-overview-docs-the-graph) - [Welcome to the Token API | Docs | The Graph](#welcome-to-the-token-api-docs-the-graph) - [Home | Docs | The Graph](#home-docs-the-graph) - [Indexing Overview | Docs | The Graph](#indexing-overview-docs-the-graph) - [BNB Smart Chain Mainnet | Docs | The Graph](#bnb-smart-chain-mainnet-docs-the-graph) - [Solana Mainnet | Docs | The Graph](#solana-mainnet-docs-the-graph) - [About The Graph | Docs | The Graph](#about-the-graph-docs-the-graph) - [Avalanche C-Chain | Docs | The Graph](#avalanche-c-chain-docs-the-graph) - [Stellar Mainnet | Docs | The Graph](#stellar-mainnet-docs-the-graph) - [Litecoin Mainnet | Docs | The Graph](#litecoin-mainnet-docs-the-graph) - [Publishing a Substreams Package | Docs | The Graph](#publishing-a-substreams-package-docs-the-graph) - [Introduction to Substreams | Docs | The Graph](#introduction-to-substreams-docs-the-graph) - [Graph Horizon Migration Guide | Docs | The Graph](#graph-horizon-migration-guide-docs-the-graph) - [Sink your Substreams | Docs | The Graph](#sink-your-substreams-docs-the-graph) - [Polygon Mainnet | Docs | The Graph](#polygon-mainnet-docs-the-graph) - [Arbitrum One Mainnet | Docs | The Graph](#arbitrum-one-mainnet-docs-the-graph) - [Substreams Dev Container | Docs | The Graph](#substreams-dev-container-docs-the-graph) - [Oops! This page was lost in space... | Docs | The Graph](#oops-this-page-was-lost-in-space-docs-the-graph) - [Starknet Mainnet | Docs | The Graph](#starknet-mainnet-docs-the-graph) - [Hypergraph FAQ | Docs | The Graph](#hypergraph-faq-docs-the-graph) - [Telos Mainnet | Docs | The Graph](#telos-mainnet-docs-the-graph) - [Celo Mainnet | Docs | The Graph](#celo-mainnet-docs-the-graph) - [OP Mainnet | Docs | The Graph](#op-mainnet-docs-the-graph) - [Near Mainnet | Docs | The Graph](#near-mainnet-docs-the-graph) - [Base Chain | Docs | The Graph](#base-chain-docs-the-graph) - [What changes with Graph Horizon? | Docs | The Graph](#what-changes-with-graph-horizon-docs-the-graph) - [WAX Mainnet | Docs | The Graph](#wax-mainnet-docs-the-graph) - [Vaulta Mainnet | Docs | The Graph](#vaulta-mainnet-docs-the-graph) - [Sonic Mainnet | Docs | The Graph](#sonic-mainnet-docs-the-graph) - [ApeChain Mainnet | Docs | The Graph](#apechain-mainnet-docs-the-graph) - [Arbitrum Nova Mainnet | Docs | The Graph](#arbitrum-nova-mainnet-docs-the-graph) - [Blast Mainnet | Docs | The Graph](#blast-mainnet-docs-the-graph) - [Injective Mainnet | Docs | The Graph](#injective-mainnet-docs-the-graph) - [Token Holders | Docs | The Graph](#token-holders-docs-the-graph) - [svmBNB Mainnet | Docs | The Graph](#svmbnb-mainnet-docs-the-graph) - [Chiliz Mainnet | Docs | The Graph](#chiliz-mainnet-docs-the-graph) - [Boba Network | Docs | The Graph](#boba-network-docs-the-graph) - [Botanix Mainnet | Docs | The Graph](#botanix-mainnet-docs-the-graph) - [Injective EVM Mainnet | Docs | The Graph](#injective-evm-mainnet-docs-the-graph) - [HyperEVM Mainnet | Docs | The Graph](#hyperevm-mainnet-docs-the-graph) - [Berachain Mainnet | Docs | The Graph](#berachain-mainnet-docs-the-graph) - [zkSync Mainnet | Docs | The Graph](#zksync-mainnet-docs-the-graph) - [Unichain Mainnet | Docs | The Graph](#unichain-mainnet-docs-the-graph) - [Abstract Mainnet | Docs | The Graph](#abstract-mainnet-docs-the-graph) - [Autonomys Mainnet | Docs | The Graph](#autonomys-mainnet-docs-the-graph) - [Monad Mainnet | Docs | The Graph](#monad-mainnet-docs-the-graph) - [Fantom Opera Mainnet | Docs | The Graph](#fantom-opera-mainnet-docs-the-graph) - [Moonriver Mainnet | Docs | The Graph](#moonriver-mainnet-docs-the-graph) - [Moonbeam Mainnet | Docs | The Graph](#moonbeam-mainnet-docs-the-graph) - [opBNB Mainnet | Docs | The Graph](#opbnb-mainnet-docs-the-graph) - [Cronos EVM Chain Mainnet | Docs | The Graph](#cronos-evm-chain-mainnet-docs-the-graph) - [MegaETH Mainnet | Docs | The Graph](#megaeth-mainnet-docs-the-graph) - [Soneium Mainnet | Docs | The Graph](#soneium-mainnet-docs-the-graph) - [Katana Mainnet | Docs | The Graph](#katana-mainnet-docs-the-graph) - [World Chain Mainnet | Docs | The Graph](#world-chain-mainnet-docs-the-graph) - [TRON Mainnet | Docs | The Graph](#tron-mainnet-docs-the-graph) - [Metis Andromeda Mainnet | Docs | The Graph](#metis-andromeda-mainnet-docs-the-graph) - [Corn Maizenet | Docs | The Graph](#corn-maizenet-docs-the-graph) - [Hemi Mainnet | Docs | The Graph](#hemi-mainnet-docs-the-graph) - [Kaia Mainnet | Docs | The Graph](#kaia-mainnet-docs-the-graph) - [Linea Mainnet | Docs | The Graph](#linea-mainnet-docs-the-graph) - [Lumia Mainnet | Docs | The Graph](#lumia-mainnet-docs-the-graph) - [Neo X Mainnet | Docs | The Graph](#neo-x-mainnet-docs-the-graph) - [Stable | Docs | The Graph](#stable-docs-the-graph) - [Etherlink Mainnet | Docs | The Graph](#etherlink-mainnet-docs-the-graph) - [Gnosis Mainnet | Docs | The Graph](#gnosis-mainnet-docs-the-graph) - [Edge & Node Upgrade Indexer | Docs | The Graph](#edge-node-upgrade-indexer-docs-the-graph) - [Firehose | Docs | The Graph](#firehose-docs-the-graph) - [Hashkey Chain Mainnet | Docs | The Graph](#hashkey-chain-mainnet-docs-the-graph) - [Peaq Network | Docs | The Graph](#peaq-network-docs-the-graph) - [Ronin Mainnet | Docs | The Graph](#ronin-mainnet-docs-the-graph) - [Tempo Mainnet | Docs | The Graph](#tempo-mainnet-docs-the-graph) - [Viction Mainnet | Docs | The Graph](#viction-mainnet-docs-the-graph) - [Vana Mainnet | Docs | The Graph](#vana-mainnet-docs-the-graph) - [TRON EVM Mainnet | Docs | The Graph](#tron-evm-mainnet-docs-the-graph) --- # Protocol Contracts | Docs | The Graph Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository⁠](https://github.com/graphprotocol/contracts) to learn more. Arbitrum One[](https://thegraph.com/docs/en/contracts/#arbitrum-one) --------------------------------------------------------------------- This is the principal deployment of The Graph Network. | Contract | Address | | --- | --- | | GraphProxyAdmin | [0x2983936aC20202a6555993448E0d5654AC8Ca5fd⁠](https://arbiscan.io/address/0x2983936aC20202a6555993448E0d5654AC8Ca5fd) | | BancorFormula | [0xA489FDc65229D6225014C0b357BCD19af6f00eE9⁠](https://arbiscan.io/address/0xA489FDc65229D6225014C0b357BCD19af6f00eE9) | | Controller | [0x0a8491544221dd212964fbb96487467291b2C97e⁠](https://arbiscan.io/address/0x0a8491544221dd212964fbb96487467291b2C97e) | | EpochManager | [0x5A843145c43d328B9bB7a4401d94918f131bB281⁠](https://arbiscan.io/address/0x5A843145c43d328B9bB7a4401d94918f131bB281) | | L2GraphToken | [0x9623063377AD1B27544C965cCd7342f7EA7e88C7⁠](https://arbiscan.io/address/0x9623063377AD1B27544C965cCd7342f7EA7e88C7) | | GraphCurationToken | [0x47a0d56ea574419B524285d52fFe7198297D209c⁠](https://arbiscan.io/address/0x47a0d56ea574419B524285d52fFe7198297D209c) | | ServiceRegistry | [0x072884c745c0A23144753335776c99BE22588f8A⁠](https://arbiscan.io/address/0x072884c745c0A23144753335776c99BE22588f8A) | | L2Curation | [0x22d78fb4bc72e191C765807f8891B5e1785C8014⁠](https://arbiscan.io/address/0x22d78fb4bc72e191C765807f8891B5e1785C8014) | | SubgraphNFTDescriptor | [0x96cce9b6489744630A058324FB22e7CD02815ebe⁠](https://arbiscan.io/address/0x96cce9b6489744630A058324FB22e7CD02815ebe) | | SubgraphNFT | [0x3FbD54f0cc17b7aE649008dEEA12ed7D2622B23f⁠](https://arbiscan.io/address/0x3FbD54f0cc17b7aE649008dEEA12ed7D2622B23f) | | L2GNS | [0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec⁠](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec) | | L2Staking | [0x00669A4CF01450B64E8A2A20E9b1FCB71E61eF03⁠](https://arbiscan.io/address/0x00669A4CF01450B64E8A2A20E9b1FCB71E61eF03) | | RewardsManager | [0x971B9d3d0Ae3ECa029CAB5eA1fB0F72c85e6a525⁠](https://arbiscan.io/address/0x971B9d3d0Ae3ECa029CAB5eA1fB0F72c85e6a525) | | DisputeManager | [0x0Ab2B043138352413Bb02e67E626a70320E3BD46⁠](https://arbiscan.io/address/0x0Ab2B043138352413Bb02e67E626a70320E3BD46) | | AllocationExchange | [0x993F00C98D1678371a7b261Ed0E0D4b6F42d9aEE⁠](https://arbiscan.io/address/0x993F00C98D1678371a7b261Ed0E0D4b6F42d9aEE) | | L2GraphTokenGateway | [0x65E1a5e8946e7E87d9774f5288f41c30a99fD302⁠](https://arbiscan.io/address/0x65E1a5e8946e7E87d9774f5288f41c30a99fD302) | | EthereumDIDRegistry | [0xa9AEb1c6f14f4244547B9a0946C485DA99047638⁠](https://arbiscan.io/address/0xa9AEb1c6f14f4244547B9a0946C485DA99047638) | | IEthereumDIDRegistry | [0xa9AEb1c6f14f4244547B9a0946C485DA99047638⁠](https://arbiscan.io/address/0xa9AEb1c6f14f4244547B9a0946C485DA99047638) | | StakingExtension | [0x3bE385576d7C282070Ad91BF94366de9f9ba3571⁠](https://arbiscan.io/address/0x3bE385576d7C282070Ad91BF94366de9f9ba3571) | | SubgraphAvailabilityManager | [0x1cB555359319A94280aCf85372Ac2323AaE2f5fd⁠](https://arbiscan.io/address/0x1cB555359319A94280aCf85372Ac2323AaE2f5fd) | Ethereum Mainnet[](https://thegraph.com/docs/en/contracts/#ethereum-mainnet) ----------------------------------------------------------------------------- This was the original deployment of The Graph Network. [Learn more](https://thegraph.com/docs/en/archived/arbitrum/arbitrum-faq/) about The Graph’s scaling with Arbitrum. | Contract | Address | | --- | --- | | IENS | [0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e⁠](https://etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e) | | IEthereumDIDRegistry | [0xdCa7EF03e98e0DC2B855bE647C39ABe984fcF21B⁠](https://etherscan.io/address/0xdCa7EF03e98e0DC2B855bE647C39ABe984fcF21B) | | GraphProxyAdmin | [0xF3B000a6749259539aF4E49f24EEc74Ea0e71430⁠](https://etherscan.io/address/0xF3B000a6749259539aF4E49f24EEc74Ea0e71430) | | BancorFormula | [0xd0C61e8F15d9deF697E1100663eD7dA74d3727dC⁠](https://etherscan.io/address/0xd0C61e8F15d9deF697E1100663eD7dA74d3727dC) | | Controller | [0x24CCD4D3Ac8529fF08c58F74ff6755036E616117⁠](https://etherscan.io/address/0x24CCD4D3Ac8529fF08c58F74ff6755036E616117) | | EpochManager | [0x64F990Bf16552A693dCB043BB7bf3866c5E05DdB⁠](https://etherscan.io/address/0x64F990Bf16552A693dCB043BB7bf3866c5E05DdB) | | GraphToken | [0xc944E90C64B2c07662A292be6244BDf05Cda44a7⁠](https://etherscan.io/address/0xc944E90C64B2c07662A292be6244BDf05Cda44a7) | | ServiceRegistry | [0xaD0C9DaCf1e515615b0581c8D7E295E296Ec26E6⁠](https://etherscan.io/address/0xaD0C9DaCf1e515615b0581c8D7E295E296Ec26E6) | | GraphCurationToken | [0xb2E26f17Aea8eFA534e15Bde5C79c25D0C3dfa2e⁠](https://etherscan.io/address/0xb2E26f17Aea8eFA534e15Bde5C79c25D0C3dfa2e) | | Curation | [0x8FE00a685Bcb3B2cc296ff6FfEaB10acA4CE1538⁠](https://etherscan.io/address/0x8FE00a685Bcb3B2cc296ff6FfEaB10acA4CE1538) | | L1GNS | [0xaDcA0dd4729c8BA3aCf3E99F3A9f471EF37b6825⁠](https://etherscan.io/address/0xaDcA0dd4729c8BA3aCf3E99F3A9f471EF37b6825) | | L1Staking | [0xF55041E37E12cD407ad00CE2910B8269B01263b9⁠](https://etherscan.io/address/0xF55041E37E12cD407ad00CE2910B8269B01263b9) | | RewardsManager | [0x9Ac758AB77733b4150A901ebd659cbF8cB93ED66⁠](https://etherscan.io/address/0x9Ac758AB77733b4150A901ebd659cbF8cB93ED66) | | DisputeManager | [0x97307b963662cCA2f7eD50e38dCC555dfFc4FB0b⁠](https://etherscan.io/address/0x97307b963662cCA2f7eD50e38dCC555dfFc4FB0b) | | AllocationExchange | [0x4a53cf3b3EdA545dc61dee0cA21eA8996C94385f⁠](https://etherscan.io/address/0x4a53cf3b3EdA545dc61dee0cA21eA8996C94385f) | | SubgraphNFTDescriptor | [0x8F0B7e136891e8Bad6aa4Abcb64EeeFE29dC2Af0⁠](https://etherscan.io/address/0x8F0B7e136891e8Bad6aa4Abcb64EeeFE29dC2Af0) | | SubgraphNFT | [0x24e36639b3A3aaA9c928a8A6f12d34F942f1ab67⁠](https://etherscan.io/address/0x24e36639b3A3aaA9c928a8A6f12d34F942f1ab67) | | BridgeEscrow | [0x36aFF7001294daE4C2ED4fDEfC478a00De77F090⁠](https://etherscan.io/address/0x36aFF7001294daE4C2ED4fDEfC478a00De77F090) | | L1GraphTokenGateway | [0x01cDC91B0A9bA741903aA3699BF4CE31d6C5cC06⁠](https://etherscan.io/address/0x01cDC91B0A9bA741903aA3699BF4CE31d6C5cC06) | | StakingExtension | [0xA479c00cDa8C07bce458D7a826C7b091672EB92C⁠](https://etherscan.io/address/0xA479c00cDa8C07bce458D7a826C7b091672EB92C) | Arbitrum Sepolia[](https://thegraph.com/docs/en/contracts/#arbitrum-sepolia) ----------------------------------------------------------------------------- This is the primary testnet for The Graph Network. Testnet is predominantly used by core developers and ecosystem participants for testing purposes. There are no guarantees of service or availability on The Graph’s testnets. | Contract | Address | | --- | --- | | GraphProxyAdmin | [0x7474a6cc5fAeDEc620Db0fa8E4da6eD58477042C⁠](https://sepolia.arbiscan.io/address/0x7474a6cc5fAeDEc620Db0fa8E4da6eD58477042C) | | Controller | [0x9DB3ee191681f092607035d9BDA6e59FbEaCa695⁠](https://sepolia.arbiscan.io/address/0x9DB3ee191681f092607035d9BDA6e59FbEaCa695) | | EpochManager | [0x88b3C7f37253bAA1A9b95feAd69bD5320585826D⁠](https://sepolia.arbiscan.io/address/0x88b3C7f37253bAA1A9b95feAd69bD5320585826D) | | L2GraphToken | [0xf8c05dCF59E8B28BFD5eed176C562bEbcfc7Ac04⁠](https://sepolia.arbiscan.io/address/0xf8c05dCF59E8B28BFD5eed176C562bEbcfc7Ac04) | | GraphCurationToken | [0x00FBd5D46FFAc54862c1Dd27BE08924BB17f5CDa⁠](https://sepolia.arbiscan.io/address/0x00FBd5D46FFAc54862c1Dd27BE08924BB17f5CDa) | | ServiceRegistry | [0x888541878CbDDEd880Cd58c728f1Af5C47343F86⁠](https://sepolia.arbiscan.io/address/0x888541878CbDDEd880Cd58c728f1Af5C47343F86) | | L2Curation | [0xDe761f075200E75485F4358978FB4d1dC8644FD5⁠](https://sepolia.arbiscan.io/address/0xDe761f075200E75485F4358978FB4d1dC8644FD5) | | SubgraphNFTDescriptor | [0x4032F7B6b27FfC9862106f826379DaB1716C71d7⁠](https://sepolia.arbiscan.io/address/0x4032F7B6b27FfC9862106f826379DaB1716C71d7) | | SubgraphNFT | [0xF21Df5BbA7EB9b54D8F60C560aFb9bA63e6aED1A⁠](https://sepolia.arbiscan.io/address/0xF21Df5BbA7EB9b54D8F60C560aFb9bA63e6aED1A) | | L2GNS | [0x3133948342F35b8699d8F94aeE064AbB76eDe965⁠](https://sepolia.arbiscan.io/address/0x3133948342F35b8699d8F94aeE064AbB76eDe965) | | StakingExtension | [0x05709dd705A5674346B7206a2bC657C8bAb3301B⁠](https://sepolia.arbiscan.io/address/0x05709dd705A5674346B7206a2bC657C8bAb3301B) | | L2Staking | [0x865365C425f3A593Ffe698D9c4E6707D14d51e08⁠](https://sepolia.arbiscan.io/address/0x865365C425f3A593Ffe698D9c4E6707D14d51e08) | | RewardsManager | [0x1F49caE7669086c8ba53CC35d1E9f80176d67E79⁠](https://sepolia.arbiscan.io/address/0x1F49caE7669086c8ba53CC35d1E9f80176d67E79) | | DisputeManager | [0x7C9B82717f9433932507dF6EdA93A9678b258698⁠](https://sepolia.arbiscan.io/address/0x7C9B82717f9433932507dF6EdA93A9678b258698) | | AllocationExchange | [0x9BD4FBDa981D628AbA16F261f810dD59E5bAf9eA⁠](https://sepolia.arbiscan.io/address/0x9BD4FBDa981D628AbA16F261f810dD59E5bAf9eA) | | L2GraphTokenGateway | [0xB24Ce0f8c18c4DdDa584A7EeC132F49C966813bb⁠](https://sepolia.arbiscan.io/address/0xB24Ce0f8c18c4DdDa584A7EeC132F49C966813bb) | | EthereumDIDRegistry | [0xF5f4cA61481558709AFa94AdEDa7B5F180f4AD59⁠](https://sepolia.arbiscan.io/address/0xF5f4cA61481558709AFa94AdEDa7B5F180f4AD59) | | SubgraphAvailabilityManager | [0x71D9aE967d1f31fbbD1817150902de78f8f2f73E⁠](https://sepolia.arbiscan.io/address/0x71D9aE967d1f31fbbD1817150902de78f8f2f73E) | Sepolia[](https://thegraph.com/docs/en/contracts/#sepolia) ----------------------------------------------------------- | Contract | Address | | --- | --- | | GraphProxyAdmin | [0xe2011488ea6B02692Ee58717698aecDdfBf4756F⁠](https://sepolia.etherscan.io/address/0xe2011488ea6B02692Ee58717698aecDdfBf4756F) | | BancorFormula | [0x56b9f17D3Ca520b229F56D13a988dFAE9924C91E⁠](https://sepolia.etherscan.io/address/0x56b9f17D3Ca520b229F56D13a988dFAE9924C91E) | | Controller | [0xf53B3910ecaeED1Aac4Bb5Ba9840d25E36e52b7C⁠](https://sepolia.etherscan.io/address/0xf53B3910ecaeED1Aac4Bb5Ba9840d25E36e52b7C) | | EpochManager | [0x3C39036a76104D7c6D3eF13a21477C0fE23A3Aa2⁠](https://sepolia.etherscan.io/address/0x3C39036a76104D7c6D3eF13a21477C0fE23A3Aa2) | | GraphToken | [0xCA59cCeb39bE1808d7aA607153f4A5062daF3a83⁠](https://sepolia.etherscan.io/address/0xCA59cCeb39bE1808d7aA607153f4A5062daF3a83) | | GraphCurationToken | [0xE04cE530c532538F1F63cA911849925425C2A1Aa⁠](https://sepolia.etherscan.io/address/0xE04cE530c532538F1F63cA911849925425C2A1Aa) | | ServiceRegistry | [0x0Ee47634c94E6606f67301b3A868319073CB0FC2⁠](https://sepolia.etherscan.io/address/0x0Ee47634c94E6606f67301b3A868319073CB0FC2) | | Curation | [0x77A6e5F2f13218B33A97Aec56d591dB18D60FFb1⁠](https://sepolia.etherscan.io/address/0x77A6e5F2f13218B33A97Aec56d591dB18D60FFb1) | | SubgraphNFTDescriptor | [0xC9b2011A082d75c01C5C3eEA132f29ebaD182BD5⁠](https://sepolia.etherscan.io/address/0xC9b2011A082d75c01C5C3eEA132f29ebaD182BD5) | | SubgraphNFT | [0x120005c38D2624Ef70185fEf3a051Dd57b27a491⁠](https://sepolia.etherscan.io/address/0x120005c38D2624Ef70185fEf3a051Dd57b27a491) | | L1GNS | [0x5461D48556B94e7fdD8ED5A8f865Ba4F1A3b5454⁠](https://sepolia.etherscan.io/address/0x5461D48556B94e7fdD8ED5A8f865Ba4F1A3b5454) | | StakingExtension | [0x3fF97b5bdC1D46B0bbD1a3166F232683470a0ce3⁠](https://sepolia.etherscan.io/address/0x3fF97b5bdC1D46B0bbD1a3166F232683470a0ce3) | | L1Staking | [0x14e9B07Dc56A0B03ac8A58453B5cCCB289d6ec90⁠](https://sepolia.etherscan.io/address/0x14e9B07Dc56A0B03ac8A58453B5cCCB289d6ec90) | | RewardsManager | [0x175f483AfAB4Fc52A6E07F9e9d46C90eB95941b5⁠](https://sepolia.etherscan.io/address/0x175f483AfAB4Fc52A6E07F9e9d46C90eB95941b5) | | DisputeManager | [0x1Da0DF3435cde4199650D35690E3B0885dfc38B1⁠](https://sepolia.etherscan.io/address/0x1Da0DF3435cde4199650D35690E3B0885dfc38B1) | | AllocationExchange | [0xd49670f70f68F7dc62c8B287F6388d250C5487E2⁠](https://sepolia.etherscan.io/address/0xd49670f70f68F7dc62c8B287F6388d250C5487E2) | | L1GraphTokenGateway | [0x549DCB0b510Ee7C8d6E8e346ab9aC75E22DD78B3⁠](https://sepolia.etherscan.io/address/0x549DCB0b510Ee7C8d6E8e346ab9aC75E22DD78B3) | | BridgeEscrow | [0x428Ab6E9EeF41Dc5098a34a6993Cdd5Be5BA24a6⁠](https://sepolia.etherscan.io/address/0x428Ab6E9EeF41Dc5098a34a6993Cdd5Be5BA24a6) | | EthereumDIDRegistry | [0xDe57D27e530c99bDa15Fe231B8C632E4a37E7343⁠](https://sepolia.etherscan.io/address/0xDe57D27e530c99bDa15Fe231B8C632E4a37E7343) | --- # Hypergraph | Docs | The Graph Hypergraph Overview[](https://thegraph.com/docs/en/hypergraph/overview/#overview) ----------------------------------------------------------------------- [Hypergraph⁠](https://docs.hypergraph.thegraph.com/) is a TypeScript-first framework for building local-first applications that sync encrypted data to a shared knowledge graph. Instead of relying on traditional backend infrastructure, it shifts control to the client and puts data where it belongs: with the user. At its core, Hypergraph is powered by two innovations: 1. Client-side architecture that keeps users in control of their data while apps remain real-time, private, and interoperable by default. 2. The [GRC-20](https://thegraph.com/blog/grc20-knowledge-graph/) standard which enables truly composable knowledge graphs. With Hypergraph, developers can build collaborative apps that feel seamless, secure, and user-owned while focusing purely on client-side logic. It offers end-to-end encryption, a GRC-20 Knowledge Graph SDK, JSON-LD storage, conflict-free sync with CRDTs, and Spaces for organizing people and data with fine-grained access. For more specifics check out, [key features⁠](https://docs.hypergraph.thegraph.com/docs/key-features) . Core Concepts[](https://thegraph.com/docs/en/hypergraph/overview/#core-concepts) --------------------------------------------------------------------------------- ### Knowledge Graphs[](https://thegraph.com/docs/en/hypergraph/overview/#knowledge-graphs) Unlike traditional databases that store data in rows and columns, knowledge graphs represent information as connected networks. This structure makes complex queries natural and efficient, while allowing the data model to evolve organically without schema migrations. #### Example Use Case[](https://thegraph.com/docs/en/hypergraph/overview/#example-use-case) In a social app, a traditional database might require complex joins to answer a query like: `"Posts by photographers that my friends liked"` In a knowledge graph, relationships are the data: 1Teresa --> profession --> Photography2Teresa --> owns --> Fujifilm X1003Teresa --> posted --> Street Photo4Alex --> friend_of --> Teresa5Alex --> liked --> Street Photo This model makes queries natural and efficient, while allowing the schema to evolve organically. ### The Hypergraph Advantage[](https://thegraph.com/docs/en/hypergraph/overview/#the-hypergraph-advantage) * **Private by default**: Personal data is encrypted on the device. * **Peer-to-peer**: No central server required. Collaboration is direct. * **Real-time**: Changes synchronize instantly across devices. * **Interoperable**: Data is usable across applications that support the protocol. Hypergraph serializes all data using the [GRC-20 standard](https://thegraph.com/blog/grc20-knowledge-graph/) . Hypergraph handles serialization, encryption, and networking behind the scenes, while developers interact with simple SDK calls. ### Spaces[](https://thegraph.com/docs/en/hypergraph/overview/#spaces) A Space is the fundamental unit of collaboration. It groups people and data, similar to a folder, Slack channel, or shared document. Each Space maps one-to-one with an Automerge document, enabling conflict-free offline editing. Membership and roles are tracked in an append-only Space Event Log, supporting common operations like creating a Space, updating roles, inviting members, or removing members. ### Identities[](https://thegraph.com/docs/en/hypergraph/overview/#identities) Each user controls a cryptographic **Identity** used for authentication, encryption, and signing events. Identities are stored locally, enabling multi-device logins without a backend. ### Inboxes[](https://thegraph.com/docs/en/hypergraph/overview/#inboxes) An Inbox is a lightweight queue for delivering updates or direct messages. * **Account Inboxes**: Belong to a single user. * **Space Inboxes**: Broadcast messages to all members. Inboxes can be public or private, with authentication policies controlling who can send messages. ### Events and CRDTs[](https://thegraph.com/docs/en/hypergraph/overview/#events-and-crdts) Hypergraph uses CRDTs (Conflict-Free Replicated Data Types) to manage updates across peers. * Updates are signed, encrypted, and broadcast to peers. * Conflicts resolve automatically without manual intervention. * Large logs are periodically compacted into snapshots for efficiency. ### Security Model[](https://thegraph.com/docs/en/hypergraph/overview/#security-model) Hypergraph is designed with security as a core principle: * End-to-end encryption ensures data privacy. * Digital signatures verify the authenticity of events. * Outdated or invalid updates are automatically rejected. * Keys are rotated when membership changes to prevent unauthorized access. Exploring Spaces[](https://thegraph.com/docs/en/hypergraph/overview/#exploring-spaces) --------------------------------------------------------------------------------------- Spaces can be browsed using [Geo Browser’s Testnet⁠](https://testnet.geobrowser.io/root) by entering a Space ID. Access is restricted by each Space’s privacy rules. Getting Started[](https://thegraph.com/docs/en/hypergraph/overview/#getting-started) ------------------------------------------------------------------------------------- * [Quickstart Guide⁠](https://docs.hypergraph.thegraph.com/docs/quickstart) * [Core Concepts⁠](https://docs.hypergraph.thegraph.com/docs/core-concepts#why-does-grc-20-exist) * [AI Usage⁠](https://docs.hypergraph.thegraph.com/docs/ai-usage) * [API Reference⁠](https://docs.hypergraph.thegraph.com/docs/api-reference/hypergraph/) * [Troubleshooting Guide⁠](https://docs.hypergraph.thegraph.com/docs/troubleshooting) For all Hypergraph documentation check out the [Hypergraph Docs⁠](https://docs.hypergraph.thegraph.com/docs/quickstart) and the [Hypergraph GitHub Repo⁠](https://github.com/graphprotocol/hypergraph) . --- # The Graph's AI | Docs | The Graph AI Suite Build with speed and scale faster with The Graph’s AI. Using AI on The Graph[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#using-ai-on-the-graph) ------------------------------------------------------------------------------------------------------ Instead of relying on static datasets or centralized APIs, you can now use our AI-native tooling, [Subgraph MCP](https://thegraph.com/docs/en/ai-suite/subgraph-mcp/introduction/) and [Token API MCP](https://thegraph.com/docs/en/ai-suite/token-api-mcp/introduction/) . ### Why Use Onchain Data with AI?[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#why-use-onchain-data-with-ai) Using onchain data with AI unlocks powerful new ways to interact with and understand blockchain ecosystems. * **AI for Developers**: You can use AI to interact directly with The Graph’s data through your agents or build AI-powered applications on top of it. This streamlines development and opens up more intuitive, dynamic use cases. AI for Developers[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#ai-for-developers) ---------------------------------------------------------------------------------------------- ### Enable Natural Language Access to Onchain Data[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#enable-natural-language-access-to-onchain-data) [Model Context Protocol⁠](https://modelcontextprotocol.io/introduction) (MCP) servers connect to Claude, Cline, and Cursor. They enable models to understand, query, and interact with structured onchain data using natural language. MCPs remove the need to write low-level queries or interact with APIs directly. ### Subgraph MCP[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#subgraph-mcp) The [Subgraph MCP](https://thegraph.com/docs/en/ai-suite/subgraph-mcp/introduction/) server connects models to Subgraphs on The Graph Network. It allows language models to explore Subgraph schemas, execute GraphQL queries, find relevant Subgraphs by keyword or contract, and surface usage metrics using natural language. ### Token API MCP[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#token-api-mcp) The [Token API MCP](https://thegraph.com/docs/en/ai-suite/token-api-mcp/introduction/) MCP server enables models to access onchain token data. It supports querying token metadata, wallet balances, transfer history, and top token holders through simple prompts. #### Benefits of Using Subgraph and Token API MCPs[](https://thegraph.com/docs/en/ai-suite/ai-introduction/#benefits-of-using-subgraph-and-token-api-mcps) * Query Subgraphs and token data using natural language * Access GraphQL schemas and token metadata without manual queries * Find Subgraphs by keyword or contract and check 30-day usage * Retrieve real-time data from The Graph and onchain token sources * Get wallet balances, transfer history, and top token holders --- # Quick Start | Docs | The Graph Subgraphs Create, deploy, and query a [Subgraph](https://thegraph.com/docs/en/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. By the end, you’ll have: * Initialized a Subgraph from a smart contract * Deployed it to Subgraph Studio for testing * Published to The Graph Network for decentralized indexing using Studio or CLI Prerequisites[](https://thegraph.com/docs/en/subgraphs/quick-start/#prerequisites) ----------------------------------------------------------------------------------- * A crypto wallet * A deployed smart contract on a [supported network](https://thegraph.com/docs/en/supported-networks/) * [Node.js⁠](https://nodejs.org/) & a package manager of your choice (`npm`, `yarn` or `pnpm`) How to Build a Subgraph[](https://thegraph.com/docs/en/subgraphs/quick-start/#how-to-build-a-subgraph) ------------------------------------------------------------------------------------------------------- ### 1\. Create a Subgraph in Subgraph Studio[](https://thegraph.com/docs/en/subgraphs/quick-start/#1-create-a-subgraph-in-subgraph-studio) 1. Go to [Subgraph Studio](https://thegraph.com/studio/) 2. Connect your wallet 3. Click “Create a Subgraph” 4. Name it in Title Case: “Subgraph Name Chain Name” ### 2\. Install the Graph CLI[](https://thegraph.com/docs/en/subgraphs/quick-start/#2-install-the-graph-cli) On your local machine, run one of the following commands: Using [npm⁠](https://www.npmjs.com/) : 1npm install -g @graphprotocol/graph-cli@latest Using [yarn⁠](https://yarnpkg.com/) : 1yarn global add @graphprotocol/graph-cli Verify install: 1graph --version ### 3\. Initialize your Subgraph[](https://thegraph.com/docs/en/subgraphs/quick-start/#3-initialize-your-subgraph) You can find commands for your specific Subgraph in [Subgraph Studio](https://thegraph.com/studio/) . Initialize your Subgraph from an existing contract: 1graph init When you initialize your Subgraph, the CLI will ask you for the following information: * **Protocol**: Choose the protocol your Subgraph will be indexing data from. * **Subgraph slug**: Create a name for your Subgraph. Your Subgraph slug is an identifier for your Subgraph. * **Directory**: Choose a directory to create your Subgraph in. * **Ethereum network** (optional): You may need to specify which EVM-compatible network your Subgraph will be indexing data from. * **Contract address**: Locate the smart contract address you’d like to query data from. * **ABI**: If the ABI is not auto-populated, you will need to input it manually as a JSON file. * **Start Block**: You should input the start block where the contract was deployed to optimize Subgraph indexing of blockchain data. * **Contract Name**: Input the name of your contract. * **Index contract events as entities**: It is suggested that you set this to true, as it will automatically add mappings to your Subgraph for every emitted event. * **Add another contract** (optional): You can add another contract. See the following screenshot for an example of what to expect when initializing your Subgraph: ![](https://thegraph.com/docs/_next/static/media/CLI-Example.5af03107.png) Subgraph command ### 4\. Edit your Subgraph[](https://thegraph.com/docs/en/subgraphs/quick-start/#4-edit-your-subgraph) When making changes to the Subgraph, you will primarily work with three files: * Manifest (`subgraph.yaml`): Defines what data sources your Subgraph will index. * Schema (`schema.graphql`): Defines what data you wish to retrieve from the Subgraph. * AssemblyScript Mappings (`mapping.ts`): Translates data from your data sources to the entities defined in the schema. For a detailed breakdown on how to write your Subgraph, refer to [Creating a Subgraph](https://thegraph.com/docs/en/subgraphs/developing/creating/starting-your-subgraph/) . Path 1: Studio Approach[](https://thegraph.com/docs/en/subgraphs/quick-start/#path-1-studio-approach) ------------------------------------------------------------------------------------------------------ ### 5\. Build your Subgraph[](https://thegraph.com/docs/en/subgraphs/quick-start/#5-build-your-subgraph) Run the following: 1graph codegen && graph build ### 6\. Deploy your Subgraph to Subgraph Studio[](https://thegraph.com/docs/en/subgraphs/quick-start/#6-deploy-your-subgraph-to-subgraph-studio) When you **deploy** a Subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/) , where you can test, stage and review it. A deployed Subgraph’s indexing is performed by the [Upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/) , which is a single Indexer owned and operated by Edge & Node. A **deployed** Subgraph is free to use, rate-limited, not visible to the public, and meant to be used for development, staging, and testing purposes. You do not need to use Subgraph Studio to publish your Subgraph to The Graph Network. Studio is only required for testing and staging your Subgraph prior to publishing. 1. Get your deploy key from the Subgraph page in Studio ![](https://thegraph.com/docs/_next/static/media/subgraph-studio-deploy-key.29531055.jpg) Deploy key 2. Authenticate: 1graph auth 3. Deploy: 1graph deploy ### 7\. Review in Studio[](https://thegraph.com/docs/en/subgraphs/quick-start/#7-review-in-studio) Use the Studio to: * Run a sample query. * Analyze your Subgraph in the dashboard to check information. * Check the logs on the dashboard to see if there are any errors with your Subgraph. The logs of an operational Subgraph will look like this: ![](https://thegraph.com/docs/_next/static/media/subgraph-logs-image.52c55bda.png) Subgraph logs ### 8\. Publish to The Graph Network[](https://thegraph.com/docs/en/subgraphs/quick-start/#8-publish-to-the-graph-network) When your Subgraph is ready for a production environment, you can publish it to the decentralized network. Publishing is an onchain action that does the following: * It makes your Subgraph available to be indexed by the decentralized [Indexers](https://thegraph.com/docs/en/indexing/overview/) on The Graph Network. * It removes rate limits and makes your Subgraph publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/) . * It makes your Subgraph available for [Curators](https://thegraph.com/docs/en/resources/roles/curating/) to add curation signal. 1. Click **Publish** in Studio 2. Select network 3. (Recommended) Add curation during the same transaction to save on gas costs: ![](https://thegraph.com/docs/_next/static/media/studio-publish-modal.4bb2696b.png) Subgraph publish ![](https://thegraph.com/docs/_next/static/media/publish-sub-transfer.b27f6161.png) Publish a Subgraph on Subgraph Studio Curation with 3,000+ GRT is recommended to incentivize indexing. Path 2: CLI Approach[](https://thegraph.com/docs/en/subgraphs/quick-start/#path-2-cli-approach) ------------------------------------------------------------------------------------------------ 1. Open the `graph-cli`. 2. Run the following commands to build and publish your Subgraph: `graph codegen && graph build` then `graph publish`. 3. A browser window will prompt you to connect your wallet, add metadata, and publish your Subgraph to the network of your choice. ![](https://thegraph.com/docs/_next/static/media/cli-ui.ea276deb.png) cli-ui ### Custom Options[](https://thegraph.com/docs/en/subgraphs/quick-start/#custom-options) You can customize the deployment by uploading to a specific IPFS node and using additional flags: 1USAGE2 $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id ] [-i ] [--ipfs-hash ] [--webapp-url3 ]45FLAGS6 -h, --help Show CLI help.7 -i, --ipfs= [default: https://ipfs.thegraph.com/api/v0] Upload build results to an IPFS node.8 --ipfs-hash= IPFS hash of the subgraph manifest to deploy.9 --protocol-network=