From 0236d8ff6b685f2e48fb53cb33ef21b93475415e Mon Sep 17 00:00:00 2001 From: Brandon Kramer Date: Thu, 19 Nov 2026 16:50:58 +0000 Subject: [PATCH] Consolidate curation docs, add Getting GRT and Bridging GRT pages - Add Resources > Getting GRT (Coinbase, Binance, Uniswap, ETH for gas) and Resources > Bridging GRT, moved out of the Subgraph Studio billing page - Clean up Studio billing page with Arbitrum One context; add client-side HashRedirect component for #getting-grt, #getting-ether and #grt-on-arbitrum-or-ethereum - Move curation to Subgraphs > Developing > Curating ("Subgraph Curation") as the single source of truth: signal table (500/1k/3k/10k GRT), 3% curation tax, flat bonding curve, no tax on withdrawals - Remove duplicated/conflicting curation numbers across the docs and link to the curation page instead - Match Graph Horizon: no delegation tax, 28-day undelegation period - Clarify that publishing does not require signal - Move Delegating to the top level of Resources (remove Additional Roles) - Move "The Graph Network vs. Self Hosting" to Guides & Best Practices - Rename Developer FAQ title/sections, Overview/Quick Start titles and Cana CLI nav label - Add nginx redirects for all moved pages and update route lockfile Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01HpT75s8N1pkWJQzEydBAKq --- nginx.conf | 17 +- website/route-lockfile.txt | 10 +- website/src/components/HashRedirect.tsx | 28 ++++ website/src/components/index.ts | 1 + website/src/layout/Layout.tsx | 2 + .../supply-side/incentivizing-syncs.mdx | 12 +- .../subgraphs/supply-side/tracking-qos.mdx | 2 +- website/src/pages/en/indexing/overview.mdx | 2 +- .../src/pages/en/resources/_meta-titles.json | 2 +- website/src/pages/en/resources/_meta.js | 5 +- .../src/pages/en/resources/bridging-grt.mdx | 51 ++++++ .../resources/{roles => }/delegating/_meta.js | 0 .../{roles => }/delegating/delegating.mdx | 0 .../{roles => }/delegating/undelegating.mdx | 2 +- .../src/pages/en/resources/getting-grt.mdx | 135 ++++++++++++++++ website/src/pages/en/resources/glossary.mdx | 6 +- website/src/pages/en/resources/roles/_meta.js | 4 - .../src/pages/en/resources/roles/curating.mdx | 89 ----------- website/src/pages/en/resources/tokenomics.mdx | 8 +- .../en/subgraphs/best-practices/_meta.js | 1 + .../best-practices}/benefits.mdx | 6 +- .../en/subgraphs/best-practices/overview.mdx | 2 +- .../best-practices/transfer-to-the-graph.mdx | 4 +- .../pages/en/subgraphs/developing/_meta.js | 1 + .../developing/creating/install-the-cli.mdx | 2 +- .../en/subgraphs/developing/curating.mdx | 107 +++++++++++++ .../publishing-a-subgraph.mdx | 28 +--- .../using-subgraph-studio.mdx | 4 +- .../en/subgraphs/developing/developer-faq.mdx | 22 ++- .../managing/deleting-a-subgraph.mdx | 2 +- .../subgraphs/existing-subgraphs/explorer.mdx | 12 +- website/src/pages/en/subgraphs/overview.mdx | 13 +- .../subgraph-studio/introduction.mdx | 151 ++++-------------- .../providers/subgraph-studio/studio-faq.mdx | 12 ++ .../subgraph-studio/upgrade-indexer.mdx | 4 +- .../src/pages/en/subgraphs/quick-start.mdx | 7 +- .../src/pages/en/subgraphs/tooling/_meta.js | 2 +- .../customContent/_subgraph-community.mdx | 4 +- 38 files changed, 443 insertions(+), 317 deletions(-) create mode 100644 website/src/components/HashRedirect.tsx create mode 100644 website/src/pages/en/resources/bridging-grt.mdx rename website/src/pages/en/resources/{roles => }/delegating/_meta.js (100%) rename website/src/pages/en/resources/{roles => }/delegating/delegating.mdx (100%) rename website/src/pages/en/resources/{roles => }/delegating/undelegating.mdx (97%) create mode 100644 website/src/pages/en/resources/getting-grt.mdx delete mode 100644 website/src/pages/en/resources/roles/_meta.js delete mode 100644 website/src/pages/en/resources/roles/curating.mdx rename website/src/pages/en/{resources => subgraphs/best-practices}/benefits.mdx (92%) create mode 100644 website/src/pages/en/subgraphs/developing/curating.mdx diff --git a/nginx.conf b/nginx.conf index 55811434791b..4e83c831d7b2 100644 --- a/nginx.conf +++ b/nginx.conf @@ -81,8 +81,8 @@ http { rewrite ^/docs/en/subgraphs/cookbook/timeseries/$ $scheme://$http_host/docs/en/subgraphs/best-practices/timeseries/ permanent; rewrite ^/docs/en/cookbook/transfer-to-the-graph/$ $scheme://$http_host/docs/en/subgraphs/best-practices/transfer-to-the-graph/ permanent; rewrite ^/docs/en/subgraphs/cookbook/near/$ $scheme://$http_host/docs/en/supported-networks/ permanent; - rewrite ^/docs/en/curating/$ $scheme://$http_host/docs/en/resources/roles/curating/ permanent; - rewrite ^/docs/en/delegating/$ $scheme://$http_host/docs/en/resources/roles/delegating/delegating/ permanent; + rewrite ^/docs/en/curating/$ $scheme://$http_host/docs/en/subgraphs/developing/curating/ permanent; + rewrite ^/docs/en/delegating/$ $scheme://$http_host/docs/en/resources/delegating/delegating/ permanent; rewrite ^/docs/en/deploying/deploy-using-subgraph-studio/$ $scheme://$http_host/docs/en/subgraphs/developing/deploying-publishing/using-subgraph-studio/ permanent; rewrite ^/docs/en/deploying/deploying-a-subgraph-to-studio/$ $scheme://$http_host/docs/en/subgraphs/developing/deploying-publishing/using-subgraph-studio/ permanent; rewrite ^/docs/en/deploying/multiple-networks/$ $scheme://$http_host/docs/en/subgraphs/developing/deploying-publishing/multiple-networks/ permanent; @@ -114,10 +114,10 @@ http { rewrite ^/docs/en/managing/delete-a-subgraph/$ $scheme://$http_host/docs/en/subgraphs/developing/managing/deleting-a-subgraph/ permanent; rewrite ^/docs/en/managing/deprecate-a-subgraph/$ $scheme://$http_host/docs/en/subgraphs/developing/managing/deleting-a-subgraph/ permanent; rewrite ^/docs/en/managing/transfer-a-subgraph/$ $scheme://$http_host/docs/en/subgraphs/developing/managing/transferring-a-subgraph/ permanent; - rewrite ^/docs/en/network/benefits/$ $scheme://$http_host/docs/en/resources/benefits/ permanent; + rewrite ^/docs/en/network/benefits/$ $scheme://$http_host/docs/en/subgraphs/best-practices/benefits/ permanent; rewrite ^/docs/en/network/contracts/$ $scheme://$http_host/docs/en/contracts/ permanent; - rewrite ^/docs/en/network/curating/$ $scheme://$http_host/docs/en/resources/roles/curating/ permanent; - rewrite ^/docs/en/network/delegating/$ $scheme://$http_host/docs/en/resources/roles/delegating/delegating/ permanent; + rewrite ^/docs/en/network/curating/$ $scheme://$http_host/docs/en/subgraphs/developing/curating/ permanent; + rewrite ^/docs/en/network/delegating/$ $scheme://$http_host/docs/en/resources/delegating/delegating/ permanent; rewrite ^/docs/en/network/developing/$ $scheme://$http_host/docs/en/subgraphs/developing/introduction/ permanent; rewrite ^/docs/en/network/explorer/$ $scheme://$http_host/docs/en/subgraphs/existing-subgraphs/explorer/ permanent; rewrite ^/docs/en/network/indexing/$ $scheme://$http_host/docs/en/indexing/overview/ permanent; @@ -245,6 +245,13 @@ http { rewrite ^/docs/en/querying/graph-client/$ $scheme://$http_host/docs/en/subgraphs/querying/graph-client/README/ redirect; rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/subgraphs/developing/creating/graph-ts/README/ redirect; # --- subgraphs section reorg (subgraph-reorg) --- + rewrite ^/docs/en/resources/roles/$ $scheme://$http_host/docs/en/resources/delegating/delegating/ permanent; + rewrite ^/docs/en/resources/roles/delegating/$ $scheme://$http_host/docs/en/resources/delegating/delegating/ permanent; + rewrite ^/docs/en/resources/roles/delegating/delegating/$ $scheme://$http_host/docs/en/resources/delegating/delegating/ permanent; + rewrite ^/docs/en/resources/roles/delegating/undelegating/$ $scheme://$http_host/docs/en/resources/delegating/undelegating/ permanent; + rewrite ^/docs/en/subgraphs/developing/managing/curating/$ $scheme://$http_host/docs/en/subgraphs/developing/curating/ permanent; + rewrite ^/docs/en/resources/benefits/$ $scheme://$http_host/docs/en/subgraphs/best-practices/benefits/ permanent; + rewrite ^/docs/en/resources/roles/curating/$ $scheme://$http_host/docs/en/subgraphs/developing/curating/ permanent; rewrite ^/docs/en/subgraphs/billing/$ $scheme://$http_host/docs/en/subgraphs/providers/subgraph-studio/introduction/ permanent; rewrite ^/docs/en/subgraphs/upgrade-indexer/$ $scheme://$http_host/docs/en/subgraphs/providers/subgraph-studio/upgrade-indexer/ permanent; rewrite ^/docs/en/subgraphs/fair-use-policy/$ $scheme://$http_host/docs/en/subgraphs/providers/subgraph-studio/fair-use-policy/ permanent; diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index ef7631def74a..b0c681f49687 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -15,13 +15,14 @@ /en/indexing/tooling/firehose/ /en/indexing/tooling/graph-node/ /en/indexing/tooling/graphcast/ -/en/resources/benefits/ +/en/resources/bridging-grt/ +/en/resources/delegating/delegating/ +/en/resources/delegating/undelegating/ +/en/resources/getting-grt/ /en/resources/glossary/ -/en/resources/roles/curating/ -/en/resources/roles/delegating/delegating/ -/en/resources/roles/delegating/undelegating/ /en/resources/tokenomics/ /en/subgraphs/best-practices/avoid-eth-calls/ +/en/subgraphs/best-practices/benefits/ /en/subgraphs/best-practices/derivedfrom/ /en/subgraphs/best-practices/enums/ /en/subgraphs/best-practices/grafting/ @@ -44,6 +45,7 @@ /en/subgraphs/developing/creating/ql-schema/ /en/subgraphs/developing/creating/starting-your-subgraph/ /en/subgraphs/developing/creating/subgraph-manifest/ +/en/subgraphs/developing/curating/ /en/subgraphs/developing/deploying-publishing/multiple-networks/ /en/subgraphs/developing/deploying-publishing/publishing-a-subgraph/ /en/subgraphs/developing/deploying-publishing/using-subgraph-studio/ diff --git a/website/src/components/HashRedirect.tsx b/website/src/components/HashRedirect.tsx new file mode 100644 index 000000000000..45715e892540 --- /dev/null +++ b/website/src/components/HashRedirect.tsx @@ -0,0 +1,28 @@ +import { useEffect } from 'react' + +interface HashRedirectProps { + /** + * Map of URL fragments (without the leading `#`) to destination paths. + * Destinations are locale-relative (e.g. `/resources/getting-grt/`) and may include their own fragment. + * Fragments never reach the server, so these redirects can't live in `nginx.conf`. + */ + redirects: Record +} + +export const HashRedirect = ({ redirects }: HashRedirectProps) => { + useEffect(() => { + const redirect = () => { + const hash = decodeURIComponent(window.location.hash.replace(/^#/, '')) + const destination = hash ? redirects[hash] : undefined + if (!destination) return + const basePath = process.env.BASE_PATH ?? '' + const [locale] = window.location.pathname.substring(basePath.length).split('/').filter(Boolean) + window.location.replace(`${basePath}/${locale ?? 'en'}${destination}`) + } + redirect() + window.addEventListener('hashchange', redirect) + return () => window.removeEventListener('hashchange', redirect) + }, [redirects]) + + return null +} diff --git a/website/src/components/index.ts b/website/src/components/index.ts index 6b48b4900732..64ec47d494e8 100644 --- a/website/src/components/index.ts +++ b/website/src/components/index.ts @@ -2,6 +2,7 @@ export * from './Callout' export * from './Card' export * from './CodeBlock' export * from './DocSearch' +export * from './HashRedirect' export * from './Heading' export * from './Image' export * from './Navigation' diff --git a/website/src/layout/Layout.tsx b/website/src/layout/Layout.tsx index c6a2bc029609..850825a5082e 100644 --- a/website/src/layout/Layout.tsx +++ b/website/src/layout/Layout.tsx @@ -55,6 +55,7 @@ import { CodeBlock, CodeBlockTabs, DocSearch, + HashRedirect, Heading, Image, NavigationGroup, @@ -616,6 +617,7 @@ export default function Layout({ pageOpts, children }: NextraThemeLayoutProps If you don't have any GRT yet, see [Getting GRT](/resources/getting-grt/). Some exchanges let you withdraw GRT directly to Arbitrum One, which means you won't need to bridge at all. + +## How to Bridge GRT from Ethereum to Arbitrum One + +You will need ETH on Ethereum Mainnet to pay gas for the bridging transaction, and ETH on Arbitrum One to use your GRT once it arrives. See [Getting Ether](/resources/getting-grt/#getting-ether). + +Choose one of these options: + +- **The Arbitrum Bridge:** The official bridge at [bridge.arbitrum.io](https://bridge.arbitrum.io/?l2ChainId=42161). Connect your wallet, choose Ethereum as the source and Arbitrum One as the destination, select GRT, enter an amount, and confirm. Deposits typically arrive on Arbitrum One within about 15 minutes. +- **A third-party bridge or aggregator:** Services such as [TransferTo](https://transferto.xyz/swap) can route GRT between networks. Check fees and the destination token contract before you confirm. +- **Subgraph Studio (billing only):** When you add GRT to your Subgraph Studio billing balance, you can deposit GRT from Ethereum Mainnet and Studio bridges it to Arbitrum One for you. It takes about 15-20 minutes to process. This option funds your billing balance only, not your wallet. See [Adding GRT using a wallet](/subgraphs/providers/subgraph-studio/introduction/#adding-grt-using-a-wallet). + +Once the bridge completes, add the Arbitrum One GRT contract address above to your wallet to see your balance. + +## How to Bridge GRT from Arbitrum One back to Ethereum + +You can move GRT back to Ethereum Mainnet with the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) by choosing Arbitrum One as the source and Ethereum as the destination. + +> Withdrawals from Arbitrum One to Ethereum Mainnet through the official bridge have a challenge period of about 7 days. After it ends, you must submit a final claim transaction on Ethereum Mainnet, which costs ETH gas. + +## Bridging FAQs + +### Do I need to bridge GRT to use The Graph? + +Only if your GRT is on Ethereum Mainnet. Delegating, staking, curating, and paying for queries all happen on Arbitrum One. + +### Can I pay for Subgraph Studio queries with GRT on Ethereum? + +Yes. Subgraph Studio accepts GRT from Ethereum Mainnet as a deposit and bridges it to Arbitrum One for you. Your billing balance itself is always held on Arbitrum One, and withdrawals from it are sent to your wallet on Arbitrum One. + +### Why can't I see my GRT after bridging? + +Make sure your wallet is connected to Arbitrum One and that you've added the Arbitrum One GRT token contract (`0x9623063377AD1B27544C965cCd7342f7EA7e88C7`). If the transaction is recent, give the bridge time to finish. diff --git a/website/src/pages/en/resources/roles/delegating/_meta.js b/website/src/pages/en/resources/delegating/_meta.js similarity index 100% rename from website/src/pages/en/resources/roles/delegating/_meta.js rename to website/src/pages/en/resources/delegating/_meta.js diff --git a/website/src/pages/en/resources/roles/delegating/delegating.mdx b/website/src/pages/en/resources/delegating/delegating.mdx similarity index 100% rename from website/src/pages/en/resources/roles/delegating/delegating.mdx rename to website/src/pages/en/resources/delegating/delegating.mdx diff --git a/website/src/pages/en/resources/roles/delegating/undelegating.mdx b/website/src/pages/en/resources/delegating/undelegating.mdx similarity index 97% rename from website/src/pages/en/resources/roles/delegating/undelegating.mdx rename to website/src/pages/en/resources/delegating/undelegating.mdx index a698ef23575f..3ea693b1bb48 100644 --- a/website/src/pages/en/resources/roles/delegating/undelegating.mdx +++ b/website/src/pages/en/resources/delegating/undelegating.mdx @@ -51,4 +51,4 @@ Learn how to withdraw your delegated tokens through [Graph Explorer](https://the ## Additional Resources -To delegate successfully, review the [delegating documentation](/resources/roles/delegating/delegating/) and check out the delegate section in Graph Explorer. +To delegate successfully, review the [delegating documentation](/resources/delegating/delegating/) and check out the delegate section in Graph Explorer. diff --git a/website/src/pages/en/resources/getting-grt.mdx b/website/src/pages/en/resources/getting-grt.mdx new file mode 100644 index 000000000000..64e80eb3b5ce --- /dev/null +++ b/website/src/pages/en/resources/getting-grt.mdx @@ -0,0 +1,135 @@ +--- +title: Getting GRT +--- + +GRT is the native token of The Graph protocol. Every role in the network uses it: + +- **Subgraph developers and data consumers** pay for queries with GRT through [Subgraph Studio billing](/subgraphs/providers/subgraph-studio/introduction/) and add GRT as [curation signal](/subgraphs/developing/curating/) to attract Indexers. +- **Delegators** [delegate GRT](/resources/delegating/delegating/) to Indexers to earn a share of their rewards. +- **Indexers** stake GRT to [operate on the network](/indexing/overview/). +- **Token holders** hold, transfer, or put GRT to work in any of the roles above. + +This page shows how to get GRT from a centralized exchange (Coinbase or Binance) or a decentralized exchange (Uniswap), and how to get the ETH you need to pay gas. + +## Before You Start: Use Arbitrum One + +The Graph protocol runs on Arbitrum One. Staking, delegation, curation, and Subgraph Studio billing all require GRT on Arbitrum One, and you will need a small amount of ETH on Arbitrum One to pay gas. + +| Network | GRT token contract | +| --- | --- | +| Arbitrum One | [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) | +| Ethereum Mainnet | [0xc944E90C64B2c07662A292be6244BDf05Cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) | + +> Always check the contract address before you swap or add GRT to your wallet. If your GRT ends up on Ethereum Mainnet, you can move it to Arbitrum One by following [Bridging GRT](/resources/bridging-grt/). + +## Getting GRT + +### Coinbase + +Coinbase is a centralized exchange. Follow these steps to buy GRT on Coinbase. + +1. Go to [Coinbase](https://www.coinbase.com/) and create an account. +2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. +3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page. +4. Select the currency you want to purchase. Select GRT. +5. Select the payment method. Select your preferred payment method. +6. Select the amount of GRT you want to purchase. +7. Review your purchase. Review your purchase and click "Buy GRT". +8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT. +9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/). + - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page. + - Click on the "Send" button next to the GRT account. + - Enter the amount of GRT you want to send and the wallet address you want to send it to. + - If Coinbase offers Arbitrum One as the network for your GRT transfer, select it. Otherwise, the GRT will arrive on Ethereum Mainnet and you will need to [bridge it to Arbitrum One](/resources/bridging-grt/). + - Click "Continue" and confirm your transaction. + - Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet. + +You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency). + +### Binance + +Binance is a centralized exchange. Follow these steps to buy GRT on Binance. + +1. Go to [Binance](https://www.binance.com/en) and create an account. +2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. +3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner. +4. You will be taken to a page where you can select the currency you want to purchase. Select GRT. +5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more. +6. Select the amount of GRT you want to purchase. +7. Review your purchase and click "Buy GRT". +8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet. +9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/). + - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist. + - Click on the "wallet" button, click withdraw, and select GRT. + - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to. + - If Binance offers Arbitrum One as the withdrawal network for GRT, select it. Otherwise, the GRT will arrive on Ethereum Mainnet and you will need to [bridge it to Arbitrum One](/resources/bridging-grt/). + - Click "Continue" and confirm your transaction. + +You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582). + +### Uniswap + +This is how you can swap for GRT on Uniswap directly on Arbitrum One. You will need ETH on Arbitrum One in your wallet to swap and to pay gas (see [Getting ETH](#getting-ether)). + +1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet. +2. Select the token you want to swap from. Select ETH. +3. Select the token you want to swap to. Select GRT. + - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) +4. Enter the amount of ETH you want to swap. +5. Click "Swap". +6. Confirm the transaction in your wallet and you wait for the transaction to process. + +You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-). + +## Getting Ether + +ETH pays the transaction fees (gas) for every onchain action on The Graph, such as swapping for GRT, delegating, signaling, publishing a Subgraph, or adding GRT to your billing balance. Because The Graph runs on Arbitrum One, you need ETH on Arbitrum One, not only on Ethereum Mainnet. + +### Coinbase (ETH) + +Follow these steps to buy ETH on Coinbase. + +1. Go to [Coinbase](https://www.coinbase.com/) and create an account. +2. Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. +3. Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page. +4. Select the currency you want to purchase. Select ETH. +5. Select your preferred payment method. +6. Enter the amount of ETH you want to purchase. +7. Review your purchase and click "Buy ETH". +8. Confirm your purchase and you will have successfully purchased ETH. +9. You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/). + - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page. + - Click on the "Send" button next to the ETH account. + - Enter the amount of ETH you want to send and the wallet address you want to send it to. + - Ensure that you are sending to your Ethereum wallet address on Arbitrum One. + - Click "Continue" and confirm your transaction. + +You can learn more about getting ETH on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency). + +### Binance (ETH) + +Follow these steps to buy ETH on Binance. + +1. Go to [Binance](https://www.binance.com/en) and create an account. +2. Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. +3. Once you have verified your identity, purchase ETH by clicking on the "Buy Now" button on the homepage banner. +4. Select the currency you want to purchase. Select ETH. +5. Select your preferred payment method. +6. Enter the amount of ETH you want to purchase. +7. Review your purchase and click "Buy ETH". +8. Confirm your purchase and you will see your ETH in your Binance Spot Wallet. +9. You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/). + - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist. + - Click on the "wallet" button, click withdraw, and select ETH. + - Enter the amount of ETH you want to send and the whitelisted wallet address you want to send it to. + - Ensure that you are sending to your Ethereum wallet address on Arbitrum One. + - Click "Continue" and confirm your transaction. + +You can learn more about getting ETH on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582). + +## Next Steps + +- [Bridge GRT](/resources/bridging-grt/) from Ethereum Mainnet to Arbitrum One. +- [Add GRT to your Subgraph Studio billing balance](/subgraphs/providers/subgraph-studio/introduction/#query-payments-with-grt). +- [Delegate GRT](/resources/delegating/delegating/) to an Indexer. +- [Add curation signal](/subgraphs/developing/curating/) to your Subgraph. diff --git a/website/src/pages/en/resources/glossary.mdx b/website/src/pages/en/resources/glossary.mdx index 31402db1084a..e204006aacbe 100644 --- a/website/src/pages/en/resources/glossary.mdx +++ b/website/src/pages/en/resources/glossary.mdx @@ -27,11 +27,11 @@ title: Glossary - **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in Subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing Subgraphs. -- **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned. +- **Delegation Tax**: A 0.5% fee that Delegators previously paid when delegating GRT to Indexers. It was removed under [Graph Horizon](/graph-horizon/what-changes/), so delegating no longer incurs a protocol fee. -- **Curator**: Network participants that identify high-quality Subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a Subgraph, 10% is distributed to the Curators of that Subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a Subgraph. +- **Curator**: Network participants that identify high-quality Subgraphs, and signal GRT on them in exchange for curation shares. Curators earn a share of the Subgraph's query fees, and more signal generally attracts more Indexers. See [Curating](/subgraphs/developing/curating/). -- **Curation Tax**: A 1% fee paid by Curators when they signal GRT on Subgraphs. The GRT used to pay the fee is burned. +- **Curation Tax**: A fee paid by Curators when they signal GRT on Subgraphs, including when signal migrates to a new Subgraph version. The GRT used to pay the fee is burned. See [Curation Costs](/subgraphs/developing/curating/#curation-costs) for the current rate. - **Data Consumer**: Any application or user that queries a Subgraph. diff --git a/website/src/pages/en/resources/roles/_meta.js b/website/src/pages/en/resources/roles/_meta.js deleted file mode 100644 index 4a246af1e616..000000000000 --- a/website/src/pages/en/resources/roles/_meta.js +++ /dev/null @@ -1,4 +0,0 @@ -export default { - delegating: 'Delegating', - curating: '', -} diff --git a/website/src/pages/en/resources/roles/curating.mdx b/website/src/pages/en/resources/roles/curating.mdx deleted file mode 100644 index 7f9743a4db94..000000000000 --- a/website/src/pages/en/resources/roles/curating.mdx +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Curating ---- - -Curators are critical to The Graph's decentralized economy. They use their knowledge of the web3 ecosystem to assess and signal on the Subgraphs that should be indexed by The Graph Network. Through Graph Explorer, Curators view network data to make signaling decisions. In turn, The Graph Network rewards Curators who signal on good quality Subgraphs with a share of the query fees those Subgraphs generate. The amount of GRT signaled is one of the key considerations for indexers when determining which Subgraphs to index. - -## What Does Signaling Mean for The Graph Network? - -Before consumers can query a Subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality Subgraphs, they need to know what Subgraphs to index. When Curators signal on a Subgraph, it lets Indexers know that a Subgraph is in demand and of sufficient quality that it should be indexed. - -Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a Subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the Subgraph, entitling them to a portion of future query fees that the Subgraph drives. - -Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to Subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality Subgraph because there will be fewer queries to process or fewer Indexers to process them. - -The Upgrade Indexer ensures the indexing of all Subgraphs, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. - -When signaling, Curators can decide to signal on a specific version of the Subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. - -If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the Subgraphs you need assistance with. - -Indexers can find Subgraphs to index based on curation signals they see in Graph Explorer (screenshot below). - -![Explorer Subgraphs](/img/explorer-subgraphs.png) - -## How to Signal - -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain Subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/existing-subgraphs/explorer/) - -A curator can choose to signal on a specific Subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that Subgraph. Both are valid strategies and come with their own pros and cons. - -Signaling on a specific version is especially useful when one Subgraph is used by multiple dapps. One dapp might need to regularly update the Subgraph with new features. Another dapp might prefer to use an older, well-tested Subgraph version. Upon initial curation, a 1% standard tax is incurred. - -Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares. - -> **Note**: The first address to signal a particular Subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy. - -## Withdrawing your GRT - -Curators have the option to withdraw their signaled GRT at any time. - -Unlike the process of delegating, if you decide to withdraw your signaled GRT you will not have to wait for a cooldown period and will receive the entire amount (minus the 1% curation tax). - -Once a curator withdraws their signal, indexers may choose to keep indexing the Subgraph, even if there's currently no active GRT signaled. - -However, it is recommended that curators leave their signaled GRT in place not only to receive a portion of the query fees, but also to ensure reliability and uptime of the Subgraph. - -## Risks - -1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. -2. Curation Fee - when a curator signals GRT on a Subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their Subgraph or if a Subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/delegating/). -4. A Subgraph can fail due to a bug. A failed Subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - - If you are subscribed to the newest version of a Subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - - If you have signaled on a specific Subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new Subgraph version, thus incurring a 1% curation tax. - -## Curation FAQs - -### 1. What % of query fees do Curators earn? - -By signalling on a Subgraph, you will earn a share of all the query fees that the Subgraph generates. 10% of all query fees go to the Curators pro-rata to their curation shares. This 10% is subject to governance. - -### 2. How do I decide which Subgraphs are high quality to signal on? - -Finding high-quality Subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy Subgraphs that are driving query volume. A trustworthy Subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected Subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a Subgraph’s architecture or code in order to assess if a Subgraph is valuable. As a result: - -- Curators can use their understanding of a network to try and predict how an individual Subgraph may generate a higher or lower query volume in the future -- Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the Subgraph developer is can help determine whether or not a Subgraph is worth signalling on. - -### 3. What’s the cost of updating a Subgraph? - -Migrating your curation shares to a new Subgraph version incurs a curation tax of 1%. Curators can choose to subscribe to the newest version of a Subgraph. When curator shares get auto-migrated to a new version, Curators will also pay half curation tax, ie. 0.5%, because upgrading Subgraphs is an onchain action that costs gas. - -### 4. How often can I update my Subgraph? - -It’s suggested that you don’t update your Subgraphs too frequently. See the question above for more details. - -### 5. Can I sell my curation shares? - -Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed). - -As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax). - -### 6. Am I eligible for a curation grant? - -Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com. - -Still confused? Check out our Curation video guide below: - - diff --git a/website/src/pages/en/resources/tokenomics.mdx b/website/src/pages/en/resources/tokenomics.mdx index b748f80dd6e0..45892a862bed 100644 --- a/website/src/pages/en/resources/tokenomics.mdx +++ b/website/src/pages/en/resources/tokenomics.mdx @@ -40,7 +40,7 @@ Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in Su For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually. -There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days. +Under [Graph Horizon](/graph-horizon/what-changes/), there is no delegation tax, so Delegators can delegate without paying a protocol fee on their GRT. If a Delegator chooses to withdraw their delegated GRT, they must wait for the 28-day undelegation period. Learn more about [delegating](/resources/delegating/delegating/). If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice. @@ -48,9 +48,7 @@ If you're reading this, you're capable of becoming a Delegator right now by head Curators identify high-quality Subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the Subgraph. While any independent network participant can be a Curator, typically Subgraph developers are among the first Curators for their own Subgraphs because they want to ensure their Subgraph is indexed. -Subgraph developers are encouraged to curate their Subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation. - -Curators pay a 1% curation tax when they curate a new Subgraph. This curation tax is burned, decreasing the supply of GRT. +Curators pay a curation tax when they signal on a Subgraph. This tax is burned, decreasing the supply of GRT. For current signal recommendations and tax rates, see [Curating](/subgraphs/developing/curating/). ## Developers @@ -92,7 +90,7 @@ The amount of rewards an Indexer receives can vary based on the Indexer's self-s The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on Subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network. -The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a Subgraph, and a 1% of query fees for blockchain data. +The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include the [curation tax](/subgraphs/developing/curating/#curation-costs) when Curators signal on a Subgraph and 1% of query fees for blockchain data. The 0.5% delegation tax that was previously burned was removed under Graph Horizon. ![Total burned GRT](/img/total-burned-grt.jpeg) diff --git a/website/src/pages/en/subgraphs/best-practices/_meta.js b/website/src/pages/en/subgraphs/best-practices/_meta.js index 76467bdb8f08..4242ccae8683 100644 --- a/website/src/pages/en/subgraphs/best-practices/_meta.js +++ b/website/src/pages/en/subgraphs/best-practices/_meta.js @@ -10,5 +10,6 @@ export default { 'subgraph-debug-forking': 'Debug with Subgraph Forking', grafting: 'Grafting', 'subgraph-composition': 'Subgraph Composition', + benefits: 'The Graph Network vs. Self Hosting', 'transfer-to-the-graph': 'Transfer to The Graph', } diff --git a/website/src/pages/en/resources/benefits.mdx b/website/src/pages/en/subgraphs/best-practices/benefits.mdx similarity index 92% rename from website/src/pages/en/resources/benefits.mdx rename to website/src/pages/en/subgraphs/best-practices/benefits.mdx index 10885bd1b54a..505674898db5 100644 --- a/website/src/pages/en/resources/benefits.mdx +++ b/website/src/pages/en/subgraphs/best-practices/benefits.mdx @@ -1,5 +1,5 @@ --- -title: The Graph vs. Self Hosting +title: The Graph Network vs. Self Hosting socialImage: https://thegraph.com/docs/img/seo/benefits.jpg --- @@ -25,7 +25,7 @@ No contracts. No monthly fees. Only pay for the queries you use—with an averag Query costs may vary; the quoted cost is the average at time of publication (March 2024). -## Low Volume User (less than 100,000 queries per month) +## Low Volume User (\<100,000 queries per month) | Cost Comparison | Self Hosted | The Graph Network | | :-: | :-: | :-: | @@ -77,7 +77,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar Estimated costs are only for Ethereum Mainnet Subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their Subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on Arbitrum are substantially lower than Ethereum mainnet. -Curating signal on a Subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a Subgraph, and later withdrawn—with potential to earn returns in the process). +Curation signal on a Subgraph is an optional, mostly recoverable cost: signal can be withdrawn at any time, minus the curation tax paid on deposit, with potential to earn query fees in the process. See [Curation Costs](/subgraphs/developing/curating/#curation-costs). ## No Setup Costs & Greater Operational Efficiency diff --git a/website/src/pages/en/subgraphs/best-practices/overview.mdx b/website/src/pages/en/subgraphs/best-practices/overview.mdx index ebcb0588afdc..9cd6d6c901c7 100644 --- a/website/src/pages/en/subgraphs/best-practices/overview.mdx +++ b/website/src/pages/en/subgraphs/best-practices/overview.mdx @@ -303,7 +303,7 @@ indexerHints: | Slow from the start, even with light handlers | `startBlock` too early, or a block handler with no filter | Set the deployment block; add a `polling` filter | | Slow on every Subgraph on the same chain | RPC or provider latency | Use a faster endpoint (self-hosted) or check provider status | | First sync slow, later syncs faster | Cold environment: no shared block or call cache yet | Expected. Judge speed on a warm re-sync | -| Published on The Graph Network but not syncing at all | No Indexer has picked up the Subgraph | Add curation signal to attract Indexers | +| Published on The Graph Network but not syncing at all | No Indexer has picked up the Subgraph | [Add curation signal](/subgraphs/developing/curating/#how-much-signal-to-add) to attract Indexers | ### Iterate Faster During Development diff --git a/website/src/pages/en/subgraphs/best-practices/transfer-to-the-graph.mdx b/website/src/pages/en/subgraphs/best-practices/transfer-to-the-graph.mdx index da1ad6d92d6f..950fad7c9fdb 100644 --- a/website/src/pages/en/subgraphs/best-practices/transfer-to-the-graph.mdx +++ b/website/src/pages/en/subgraphs/best-practices/transfer-to-the-graph.mdx @@ -70,7 +70,7 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> Add curation signal when you publish so that Indexers pick up your Subgraph: at least 1,000 GRT on networks with indexing rewards, or 500 GRT on community-supported networks. To learn more, see [Curating](/resources/roles/curating/). +> Add curation signal when you publish so that Indexers pick up your Subgraph. See [how much signal to add](/subgraphs/developing/curating/#how-much-signal-to-add). To learn more, see [Curating](/subgraphs/developing/curating/). You can start [querying](/subgraphs/querying/introduction/) any Subgraph by sending a GraphQL query into the Subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. @@ -101,5 +101,5 @@ Once you upgrade, you can access and manage your Subgraphs in [Subgraph Studio]( ## Learn More - To create and publish a new Subgraph, check out the [Quick Start](/subgraphs/quick-start/). -- To learn more about attracting Indexers with signal, see [Curating](/resources/roles/curating/). +- To learn more about attracting Indexers with signal, see [Curating](/subgraphs/developing/curating/). - [Guides & Best Practices overview](/subgraphs/best-practices/overview/): the checklist to run on your Subgraph after you transfer it, and how this page fits with the rest of the section. diff --git a/website/src/pages/en/subgraphs/developing/_meta.js b/website/src/pages/en/subgraphs/developing/_meta.js index 99e41e791623..47b583fb2f43 100644 --- a/website/src/pages/en/subgraphs/developing/_meta.js +++ b/website/src/pages/en/subgraphs/developing/_meta.js @@ -4,6 +4,7 @@ export default { introduction: '', creating: titles.creating ?? '', 'deploying-publishing': titles['deploying-publishing'] ?? '', + curating: 'Curating', managing: titles.managing ?? '', 'developer-faq': 'Developer FAQ', } diff --git a/website/src/pages/en/subgraphs/developing/creating/install-the-cli.mdx b/website/src/pages/en/subgraphs/developing/creating/install-the-cli.mdx index 8f313d2540ac..b470032a0c9c 100644 --- a/website/src/pages/en/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/src/pages/en/subgraphs/developing/creating/install-the-cli.mdx @@ -2,7 +2,7 @@ title: Install the Graph CLI --- -> In order to use your Subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/providers/subgraph-studio/studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your Subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). +> In order to use your Subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/providers/subgraph-studio/studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). To attract Indexers, add curation signal to your Subgraph once it's published. See [how much signal to add](/subgraphs/developing/curating/#how-much-signal-to-add). ## Overview diff --git a/website/src/pages/en/subgraphs/developing/curating.mdx b/website/src/pages/en/subgraphs/developing/curating.mdx new file mode 100644 index 000000000000..7822fe9647b1 --- /dev/null +++ b/website/src/pages/en/subgraphs/developing/curating.mdx @@ -0,0 +1,107 @@ +--- +title: Subgraph Curation +--- + +Curation is how a published Subgraph attracts Indexers on The Graph Network. When you curate, you deposit GRT as **signal** on a Subgraph. Signal tells Indexers that the Subgraph is worth indexing, and on networks with indexing rewards it directs a share of those rewards to the Indexers that serve it. + +Anyone can curate. Most of the time, the first Curator is the Subgraph's own developer, who adds signal when publishing so that Indexers pick the Subgraph up. Third-party Curators can also signal on Subgraphs they expect to drive query volume. + +## How Signal Attracts Indexers + +Before anyone can query a Subgraph on The Graph Network, an Indexer has to sync it. Indexers decide what to sync based largely on curation signal, which they can see in [Graph Explorer](/subgraphs/existing-subgraphs/explorer/). + +- **Networks with indexing rewards:** Indexing rewards, funded by GRT issuance, are distributed to Subgraphs in proportion to their signal. More signal means more rewards for the Indexers that serve your Subgraph, which attracts more of them. To check if a network has indexing rewards, check the [Supported Networks](/supported-networks/) page. +- **Select community-supported networks:** On some networks without indexing rewards, community Indexers have committed to sync every published Subgraph above a set signal threshold. For example, InfraDAO supports published Subgraphs with 500+ GRT in signal on select chains. +- **Other networks without indexing rewards:** Signal does not attract Indexers, because there are no rewards to direct. Check your Subgraph's [indexing reward eligibility](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) and network support before you add signal. + +## How Much Signal to Add + +Use this table to choose a signal amount for your Subgraph. More signal attracts more Indexers, which gives your Subgraph better redundancy and quality of service. These amounts are guidelines, not guarantees. The number of Indexers your Subgraph attracts also depends on query volume and overall network activity. + +| Signal | When to use it | What to expect | +| --- | --- | --- | +| **500 GRT** | Select community-supported networks | Meets the community Indexer threshold on networks that offer it | +| **1,000 GRT** | Minimum for networks with indexing rewards | Attracts 1-2 Indexers, a starting point for new or low-volume Subgraphs | +| **3,000 GRT** | Minimum for 3+ Indexers | Covers the three Indexers a Gateway selects per query, so one outage doesn't leave your Subgraph unserved | +| **10,000 GRT** | Production Subgraphs | Robust multi-Indexer support with redundancy well beyond three Indexers | + +## How to Add Signal + +### When You Publish + +Subgraph Studio lets you add signal in the same transaction that publishes your Subgraph, which saves gas. See [Publishing a Subgraph](/subgraphs/developing/deploying-publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph). + +### From Graph Explorer + +You can signal on any published Subgraph, including your own, from its page in [Graph Explorer](https://thegraph.com/explorer?chain=arbitrum-one). Curation happens on Arbitrum One, so you need GRT and a small amount of ETH on Arbitrum One. See [Getting GRT](/resources/getting-grt/) and [Bridging GRT](/resources/bridging-grt/). + +![Signal from Explorer](/img/signal-from-explorer.png) + +### Auto-Migrate vs. a Specific Version + +When you signal, choose how your signal behaves when the developer publishes a new version: + +- **Auto-migrate:** Your signal moves to the newest version each time the developer publishes one. This keeps your signal on the version Indexers are serving. The curation tax applies to signal each time it migrates. +- **Specific version:** Your signal stays on the version you chose. This is useful when several dapps rely on one Subgraph and some prefer an older, well-tested version. To move to a newer version later, withdraw and signal again, which incurs the curation tax on the new deposit. + +## Curation Costs + +Curation actions come with a tax that happens each time signal is added to a Subgraph. Removal of signal is not taxed. Because migrations are taxed, publish new versions only when you need to. Frequent updates cost both the developer and Curators who use auto-migrate. + +| Action | Cost | +| --- | --- | +| Signal on a Subgraph (initial or added signal) | 3% curation tax, burned | +| Signal migrates to a new version (auto-migrate) | 3% curation tax on the migrated signal, burned. When publishing a new version, the Subgraph owner funds part of the tax on auto-migrating signal | +| Withdraw signal | No tax, only gas | + +## Curation Rewards + +Curators mint curation shares, called Graph Curation Shares (GCS), when they signal. Curators earn a share of the query fees their Subgraph generates: 10% of query fees go to Curators, pro-rata to their curation shares. This percentage is subject to governance. + +Curation on Arbitrum One uses a flat bonding curve ([GIP-0039](https://forum.thegraph.com/t/gip-0039-curation-v1-x/3613)). Shares are minted at a constant price, so there is no advantage to signaling early, and you get back the GRT you deposited, minus the curation tax, when you withdraw. + +## Withdrawing Signal + +You can withdraw your signal at any time from your profile in Graph Explorer. Unlike undelegating, there is no waiting period, and no tax is charged on withdrawals. After you withdraw, Indexers may keep indexing the Subgraph, but with less signal there is less incentive for them to do so. + +If a Subgraph is deleted, Curators can still withdraw their GRT, but GRT is not automatically returned to the Curator's wallet. See [Deleting a Subgraph](/subgraphs/developing/managing/deleting-a-subgraph/). + +## Curation Risks + +1. **Curation tax:** Every deposit and migration burns 3% of the signal, so moving signal often reduces your GRT. +2. **Query fees can be low:** The query market is still young, and returns from query fees may be lower than you expect. +3. **Subgraphs can fail:** A Subgraph can fail due to a bug, and a failed Subgraph does not accrue query fees. + - If you signal with auto-migrate, your signal moves to the fixed version when the developer publishes it, which incurs the curation tax. + - If you signal on a specific version, you need to withdraw and signal on the new version yourself, which incurs the curation tax on the new deposit. + +Curators cannot be slashed. For a network role with a different risk profile, see [Delegating](/resources/delegating/delegating/). + +## Curation FAQs + +**1. What % of query fees do Curators earn?** + +10% of a Subgraph's query fees go to its Curators, pro-rata to their curation shares. This percentage is subject to governance. + +**2. How do I decide which Subgraphs to signal on?** + +Look for trustworthy Subgraphs that drive, or are likely to drive, query volume. A trustworthy Subgraph is complete, accurate, and supports a dapp's data needs. A poorly architected Subgraph may need to be republished or may fail, so review its code and architecture. Graph Explorer metrics such as past query volume and the identity of the Subgraph developer can also help. + +**3. What does it cost when a Subgraph is updated?** + +If your signal auto-migrates, the 3% curation tax applies to the migrated signal, and the Subgraph owner funds part of it. If your signal is on a specific version, nothing happens until you choose to move it. See [Curation Costs](#curation-costs). + +**4. How often should I update my Subgraph?** + +As rarely as you can. Each new version taxes auto-migrating signal, which costs both you and your Curators. + +**5. Can I sell my curation shares?** + +No. Curation shares can't be bought or sold like other ERC20 tokens. They can only be minted (when you signal) or burned (when you withdraw). When you withdraw on Arbitrum One, you get back the GRT you deposited, minus the curation tax. + +**6. Why isn't my Subgraph being indexed after I added signal?** + +Check that your Subgraph is eligible for indexing rewards or is on a community-supported network, and that you've added enough signal for that network (see [How Much Signal to Add](#how-much-signal-to-add)). Signal on networks without indexing rewards or community support does not attract Indexers. + +**7. Am I eligible for a curation grant?** + +Curation grants are decided case by case. If you need help with curation, send a request to support@thegraph.zendesk.com and include the Subgraphs you need help with. diff --git a/website/src/pages/en/subgraphs/developing/deploying-publishing/publishing-a-subgraph.mdx b/website/src/pages/en/subgraphs/developing/deploying-publishing/publishing-a-subgraph.mdx index 15cadc052cb2..2a906601eb8b 100644 --- a/website/src/pages/en/subgraphs/developing/deploying-publishing/publishing-a-subgraph.mdx +++ b/website/src/pages/en/subgraphs/developing/deploying-publishing/publishing-a-subgraph.mdx @@ -7,7 +7,7 @@ Once you have [deployed your Subgraph to Subgraph Studio](/deploying/deploying-a When you publish a Subgraph to the decentralized network, you make it available for: -- [Curators](/resources/roles/curating/) to begin attracting Indexers to sync and serve queries. +- [Curators](/subgraphs/developing/curating/) to begin attracting Indexers to sync and serve queries. - [Indexers](/indexing/overview/) to begin indexing it. Check out the list of [supported networks](/supported-networks/). @@ -62,32 +62,10 @@ FLAGS ## Adding signal to your Subgraph -Developers can add GRT signal to their Subgraphs to incentivize Indexers to query the Subgraph. - -- If a Subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled. - -- You can check indexing reward eligibility based on Subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). - -- Specific supported networks can be checked [here](/supported-networks/). - -> Adding signal to a Subgraph which is not eligible for rewards will not attract additional Indexers. - -> If your Subgraph is eligible for rewards, it is recommended that you curate your own Subgraph with at least 3,000 GRT in order to attract additional indexers to index your Subgraph. - -The Upgrade Indexer ensures the indexing of all Subgraphs. However, signaling GRT on a particular Subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. - -When signaling, Curators can decide to signal on a specific version of the Subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. - -Indexers can find Subgraphs to index based on curation signals they see in Graph Explorer. - -![Explorer Subgraphs](/img/explorer-subgraphs.png) +Add GRT signal to your Subgraph to incentivize Indexers to index it. Before you add signal, see [Curating](/subgraphs/developing/curating/) for how much to add on your network, which networks signal works on, and what it costs. Subgraph Studio enables you to add signal to your Subgraph by adding GRT to your Subgraph's curation pool in the same transaction it is published. ![Curation Pool](/img/curate-own-subgraph-tx.png) -Alternatively, you can add GRT signal to a published Subgraph from Graph Explorer. - -![Signal from Explorer](/img/signal-from-explorer.png) - -Learn more about [Curating](/resources/roles/curating/) on The Graph Network. +You can also add signal to a published Subgraph later from [Graph Explorer](/subgraphs/developing/curating/#from-graph-explorer). diff --git a/website/src/pages/en/subgraphs/developing/deploying-publishing/using-subgraph-studio.mdx b/website/src/pages/en/subgraphs/developing/deploying-publishing/using-subgraph-studio.mdx index 0a36420cc10c..a3a3c61140e4 100644 --- a/website/src/pages/en/subgraphs/developing/deploying-publishing/using-subgraph-studio.mdx +++ b/website/src/pages/en/subgraphs/developing/deploying-publishing/using-subgraph-studio.mdx @@ -125,7 +125,9 @@ If you want to update your Subgraph, you can do the following: You can also update your Subgraph's metadata without publishing a new version. You can update your Subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an onchain transaction will be generated that updates Subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a Subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your Subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). +> Note: There are costs associated with publishing a new version of a Subgraph to the network. In addition to the transaction fees, if Curators have auto-migrating signal on your Subgraph, you must also fund part of the curation tax on that signal. See [Curation Costs](/subgraphs/developing/curating/#curation-costs). + +> You can publish a new Subgraph, or a new version of one, without any curation signal. However, Indexers may not sync your Subgraph without signal telling them it's worth indexing. See [How Much Signal to Add](/subgraphs/developing/curating/#how-much-signal-to-add). ## Automatic Archiving of Subgraph Versions diff --git a/website/src/pages/en/subgraphs/developing/developer-faq.mdx b/website/src/pages/en/subgraphs/developing/developer-faq.mdx index e45141294523..2f784f75b3a8 100644 --- a/website/src/pages/en/subgraphs/developing/developer-faq.mdx +++ b/website/src/pages/en/subgraphs/developing/developer-faq.mdx @@ -1,11 +1,11 @@ --- -title: Developer FAQ +title: Subgraph Developer FAQ sidebarTitle: FAQ --- This page summarizes some of the most common questions for developers building on The Graph. -## Subgraph Related +## Subgraph FAQ ### 1. What is a Subgraph? @@ -83,7 +83,7 @@ If only one entity is created during the event and if there's nothing better ava Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your Subgraph. -## Network Related +## The Graph Network FAQ ### 16. What networks are supported by The Graph? @@ -104,7 +104,7 @@ dataSource.address() Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network. -## Indexing & Querying Related +## Subgraph Indexing & Querying FAQs ### 19. Is it possible to specify what block to start indexing on? @@ -134,13 +134,23 @@ someCollection(first: 1000, skip: ) { ... } Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and Subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients. +## GRT FAQs + +### 24. How do I get GRT? + +You can buy GRT on centralized exchanges like Coinbase and Binance, or swap for it on Uniswap on Arbitrum One. See [Getting GRT](/resources/getting-grt/) for step-by-step instructions, including how to get ETH for gas. + +### 25. My GRT is on Ethereum Mainnet. How do I use it on The Graph? + +The Graph protocol runs on Arbitrum One, so you need to bridge your GRT from Ethereum Mainnet to Arbitrum One. See [Bridging GRT](/resources/bridging-grt/). If you only need to fund your Subgraph Studio billing balance, Studio can bridge Ethereum GRT for you during deposit. + ## Miscellaneous -### 24. Is it possible to use Apollo Federation on top of graph-node? +### 26. Is it possible to use Apollo Federation on top of graph-node? Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service. -### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories? +### 27. I want to contribute or add a GitHub issue. Where can I find the open source repositories? - [graph-node](https://github.com/graphprotocol/graph-node) - [graph-tooling](https://github.com/graphprotocol/graph-tooling) diff --git a/website/src/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx b/website/src/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx index b06ef48c83a5..382b9a17d7eb 100644 --- a/website/src/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx +++ b/website/src/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx @@ -24,5 +24,5 @@ Delete your Subgraph using [Subgraph Studio](https://thegraph.com/studio/). - Once you delete a Subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal. - Curators will not be able to signal on the Subgraph anymore. -- Curators that already signaled on the Subgraph can withdraw their signal at an average share price. +- Curators that already signaled on the Subgraph can withdraw their signaled GRT. See [Withdrawing Signal](/subgraphs/developing/curating/#withdrawing-signal). - Deleted Subgraphs will show an error message. diff --git a/website/src/pages/en/subgraphs/existing-subgraphs/explorer.mdx b/website/src/pages/en/subgraphs/existing-subgraphs/explorer.mdx index 6000bd877ee0..8bc5ac5d068b 100644 --- a/website/src/pages/en/subgraphs/existing-subgraphs/explorer.mdx +++ b/website/src/pages/en/subgraphs/existing-subgraphs/explorer.mdx @@ -110,11 +110,7 @@ To learn more about how to become an Indexer, you can take a look at the [offici #### Curators -Curators analyze Subgraphs to identify which Subgraphs are of the highest quality. Once a Curator has found a potentially high-quality Subgraph, they can curate it by signaling on its bonding curve. In doing so, Curators let Indexers know which Subgraphs are high quality and should be indexed. - -- Curators can be community members, data consumers, or even Subgraph developers who signal on their own Subgraphs by depositing GRT tokens into a bonding curve. - - By depositing GRT, Curators mint curation shares of a Subgraph. As a result, they can earn a portion of the query fees generated by the Subgraph they have signaled on. - - The bonding curve incentivizes Curators to curate the highest quality data sources. +Curators signal GRT on Subgraphs to let Indexers know which ones should be indexed. Curators can be community members, data consumers, or Subgraph developers signaling on their own Subgraphs. To learn how curation works, including costs and rewards, see [Curating](/subgraphs/developing/curating/). In the Curators table listed below you can see: @@ -124,8 +120,6 @@ In the Curators table listed below you can see: ![Curators Table](/img/explorer-curators.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). - #### Delegators Delegators play a key role in maintaining the security and decentralization of The Graph Network. They participate in the network by delegating (i.e., “staking”) GRT tokens to one or multiple indexers. @@ -145,7 +139,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/delegating/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ### Step 4. Analyze Network Performance @@ -228,7 +222,7 @@ Track your Indexer performance with visual charts and key metrics, including: #### Delegating Tab -> To learn more about the benefits of delegating, check out [delegating](/resources/roles/delegating/delegating/). +> To learn more about the benefits of delegating, check out [delegating](/resources/delegating/delegating/). The Delegators tab displays your active and historical delegations, along with the metrics for the Indexers you've delegated to. diff --git a/website/src/pages/en/subgraphs/overview.mdx b/website/src/pages/en/subgraphs/overview.mdx index 389d7ba4e12b..0cca64c82cea 100644 --- a/website/src/pages/en/subgraphs/overview.mdx +++ b/website/src/pages/en/subgraphs/overview.mdx @@ -1,5 +1,5 @@ --- -title: Subgraphs +title: Subgraphs Overview sidebarTitle: Overview --- @@ -62,12 +62,7 @@ When you're happy with your Subgraph, you can [publish it](/subgraphs/developing ### Add Curation Signal for Indexing -Published Subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your Subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. - -#### What is signal? - -- Signal is locked GRT associated with a given Subgraph. It indicates to Indexers that a given Subgraph will receive query volume and it contributes to the indexing rewards available for processing it. -- Third-party Curators may also signal on a given Subgraph, if they deem the Subgraph likely to drive query volume. +Signal is GRT deposited on a Subgraph to tell Indexers it's worth indexing. Published Subgraphs are unlikely to be picked up by Indexers without it. Learn [how much signal to add](/subgraphs/developing/curating/#how-much-signal-to-add). ### Querying & Application Development @@ -79,9 +74,9 @@ Learn more about [querying Subgraphs](/subgraphs/querying/introduction/). To update your Subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your Subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing. -- If you selected "auto-migrate" when you applied the signal, updating the Subgraph will migrate any signal to the new version and incur a migration tax. +- If you selected "auto-migrate" when you applied the signal, updating the Subgraph will migrate any signal to the new version and incur the [curation tax](/subgraphs/developing/curating/#curation-costs) on the migrated signal. - This signal migration should prompt Indexers to start indexing the new version of the Subgraph, so it should soon become available for querying. ### Deleting & Transferring Subgraphs -If you no longer need a published Subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a Subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). +If you no longer need a published Subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. When a Subgraph is deleted, [Curators](/subgraphs/developing/curating/) can withdraw their signaled GRT. diff --git a/website/src/pages/en/subgraphs/providers/subgraph-studio/introduction.mdx b/website/src/pages/en/subgraphs/providers/subgraph-studio/introduction.mdx index 6c7968c32190..f8c723dc0dda 100644 --- a/website/src/pages/en/subgraphs/providers/subgraph-studio/introduction.mdx +++ b/website/src/pages/en/subgraphs/providers/subgraph-studio/introduction.mdx @@ -3,6 +3,14 @@ title: Subgraph Studio sidebarTitle: Overview --- + + ## Querying Plans There are two plans to use when querying Subgraphs on The Graph Network. @@ -32,24 +40,14 @@ Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph - Keep track of your balances based on how much GRT you have added to your account balance, how much you have removed, and your invoices. - Automatically pay invoices based on query fees generated, as long as there is enough GRT in your account balance. -### GRT on Arbitrum or Ethereum - -The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One. - -To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this: - -- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges: +### Your GRT Must Be on Arbitrum One -- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) -- [TransferTo](https://transferto.xyz/swap) +The Graph protocol started on Ethereum Mainnet and now runs on Arbitrum One, so Subgraph Studio's billing contract holds your balance on Arbitrum One. Before you add GRT to your billing balance, make sure you have: -- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap. +- **GRT:** GRT on Arbitrum One is the simplest option. Studio also accepts GRT from Ethereum Mainnet and bridges it to Arbitrum One for you during deposit, which takes about 15-20 minutes. +- **ETH on Arbitrum One:** You need a small amount of ETH on Arbitrum One to pay gas for the deposit transaction. -- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange. - -> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt). - -Once you bridge GRT, you can add it to your billing balance. +> Don't have GRT or ETH yet? See [Getting GRT](/resources/getting-grt/). To move GRT you already hold on Ethereum Mainnet into your wallet on Arbitrum One, see [Bridging GRT](/resources/bridging-grt/). ### Adding GRT using a wallet @@ -57,7 +55,7 @@ Once you bridge GRT, you can add it to your billing balance. 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. - - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page. + - For suggestions on the number of queries you may use, see [How many queries will I need?](#how-many-queries-will-i-need). 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network. 6. Select the number of months you would like to prepay. - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time. @@ -83,120 +81,17 @@ Once you bridge GRT, you can add it to your billing balance. 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. - - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page. + - For suggestions on the number of queries you may use, see [How many queries will I need?](#how-many-queries-will-i-need). 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network. 6. Select the number of months you would like to prepay. - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time. -7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet. +7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. +8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet. - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas. -8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs. +9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs. - Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance. -## Getting GRT - -This section will show you how to get GRT to pay for query fees. - -### Coinbase - -This will be a step by step guide for purchasing GRT on Coinbase. - -1. Go to [Coinbase](https://www.coinbase.com/) and create an account. -2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. -3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page. -4. Select the currency you want to purchase. Select GRT. -5. Select the payment method. Select your preferred payment method. -6. Select the amount of GRT you want to purchase. -7. Review your purchase. Review your purchase and click "Buy GRT". -8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT. -9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/). - - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page. - - Click on the "Send" button next to the GRT account. - - Enter the amount of GRT you want to send and the wallet address you want to send it to. - - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet. - -You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency). - -### Binance - -This will be a step by step guide for purchasing GRT on Binance. - -1. Go to [Binance](https://www.binance.com/en) and create an account. -2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. -3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner. -4. You will be taken to a page where you can select the currency you want to purchase. Select GRT. -5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more. -6. Select the amount of GRT you want to purchase. -7. Review your purchase and click "Buy GRT". -8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet. -9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/). - - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist. - - Click on the "wallet" button, click withdraw, and select GRT. - - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to. - - Click "Continue" and confirm your transaction. - -You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582). - -### Uniswap - -This is how you can purchase GRT on Uniswap. - -1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet. -2. Select the token you want to swap from. Select ETH. -3. Select the token you want to swap to. Select GRT. - - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) -4. Enter the amount of ETH you want to swap. -5. Click "Swap". -6. Confirm the transaction in your wallet and you wait for the transaction to process. - -You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-). - -## Getting Ether - -This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts. - -### Coinbase - -This will be a step by step guide for purchasing ETH on Coinbase. - -1. Go to [Coinbase](https://www.coinbase.com/) and create an account. -2. Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. -3. Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page. -4. Select the currency you want to purchase. Select ETH. -5. Select your preferred payment method. -6. Enter the amount of ETH you want to purchase. -7. Review your purchase and click "Buy ETH". -8. Confirm your purchase and you will have successfully purchased ETH. -9. You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/). - - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page. - - Click on the "Send" button next to the ETH account. - - Enter the amount of ETH you want to send and the wallet address you want to send it to. - - Ensure that you are sending to your Ethereum wallet address on Arbitrum One. - - Click "Continue" and confirm your transaction. - -You can learn more about getting ETH on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency). - -### Binance - -This will be a step by step guide for purchasing ETH on Binance. - -1. Go to [Binance](https://www.binance.com/en) and create an account. -2. Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges. -3. Once you have verified your identity, purchase ETH by clicking on the "Buy Now" button on the homepage banner. -4. Select the currency you want to purchase. Select ETH. -5. Select your preferred payment method. -6. Enter the amount of ETH you want to purchase. -7. Review your purchase and click "Buy ETH". -8. Confirm your purchase and you will see your ETH in your Binance Spot Wallet. -9. You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/). - - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist. - - Click on the "wallet" button, click withdraw, and select ETH. - - Enter the amount of ETH you want to send and the whitelisted wallet address you want to send it to. - - Ensure that you are sending to your Ethereum wallet address on Arbitrum One. - - Click "Continue" and confirm your transaction. - -You can learn more about getting ETH on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582). - ## Billing FAQs ### How many queries will I need? @@ -207,9 +102,17 @@ We recommend you overestimate the number of queries you will need so that you do Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage. +### Where can I get GRT to pay for queries? + +You can buy GRT on centralized exchanges like Coinbase and Binance, or swap for it on Uniswap on Arbitrum One. See [Getting GRT](/resources/getting-grt/) for step-by-step instructions, including how to get the ETH you need for gas. + +### Does my GRT need to be on Arbitrum One? + +Your billing balance is held on Arbitrum One. You can deposit GRT from Arbitrum One directly, or deposit GRT from Ethereum Mainnet and Subgraph Studio will bridge it for you. To move GRT in your own wallet between networks, see [Bridging GRT](/resources/bridging-grt/). + ### Can I withdraw GRT from my billing balance? -Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161). +Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. Withdrawals are sent to your wallet on Arbitrum One. If you'd like to move that GRT back to Ethereum Mainnet, see [Bridging GRT](/resources/bridging-grt/#how-to-bridge-grt-from-arbitrum-one-back-to-ethereum). ### What happens when my billing balance runs out? Will I get a warning? diff --git a/website/src/pages/en/subgraphs/providers/subgraph-studio/studio-faq.mdx b/website/src/pages/en/subgraphs/providers/subgraph-studio/studio-faq.mdx index 885cef30ada7..12a2328db2ff 100644 --- a/website/src/pages/en/subgraphs/providers/subgraph-studio/studio-faq.mdx +++ b/website/src/pages/en/subgraphs/providers/subgraph-studio/studio-faq.mdx @@ -30,3 +30,15 @@ Note that you will no longer be able to see or edit the Subgraph in Studio once You can find the query URL of each Subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the Subgraph you’re interested in. You can then replace the `` placeholder with the API key you wish to leverage in Subgraph Studio. Remember that you can create an API key and query any Subgraph published to the network, even if you build a Subgraph yourself. These queries via the new API key, are paid queries as any other on the network. + +## 7. How do I get GRT to pay for queries? + +You can buy GRT on centralized exchanges like Coinbase and Binance, or swap for it on Uniswap on Arbitrum One. See [Getting GRT](/resources/getting-grt/). To pay with a credit card instead, see [Query Payments with credit card](/subgraphs/providers/subgraph-studio/introduction/#query-payments-with-credit-card). + +## 8. Does my GRT need to be on Arbitrum One? + +Your billing balance is held on Arbitrum One, and you need ETH on Arbitrum One to pay gas. Subgraph Studio accepts GRT deposits from Arbitrum One or Ethereum Mainnet and bridges Ethereum GRT for you. To move GRT in your own wallet from Ethereum Mainnet to Arbitrum One, see [Bridging GRT](/resources/bridging-grt/). + +## 9. Why isn't my published Subgraph being indexed? + +Published Subgraphs need curation signal to attract Indexers. See [Curating](/subgraphs/developing/curating/) for how much signal to add on each type of network. diff --git a/website/src/pages/en/subgraphs/providers/subgraph-studio/upgrade-indexer.mdx b/website/src/pages/en/subgraphs/providers/subgraph-studio/upgrade-indexer.mdx index 036c4bc1936a..ff14731b05e2 100644 --- a/website/src/pages/en/subgraphs/providers/subgraph-studio/upgrade-indexer.mdx +++ b/website/src/pages/en/subgraphs/providers/subgraph-studio/upgrade-indexer.mdx @@ -15,9 +15,9 @@ Originally designed as a transitional support, its primary purpose was to facili ### What it does **not** do -- Does not permanently index Subgraphs. Subgraph owners should curate Subgraphs to use independent Indexers long term. +- Does not permanently index Subgraphs. Subgraph owners should [add curation signal](/subgraphs/developing/curating/#how-much-signal-to-add) to use independent Indexers long term. - Does not compete for rewards. The Upgrade Indexer's participation on the Graph Network does not dilute rewards for other Indexers. -- Doesn't support Time Travel Queries (TTQ). All Subgraphs on the Upgrade Indexer are auto-pruned. If TTQs are needed on a Subgraph, [curation signal can be added](/subgraphs/developing/deploying-publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) to attract Indexers that will support this feature. +- Doesn't support Time Travel Queries (TTQ). All Subgraphs on the Upgrade Indexer are auto-pruned. If TTQs are needed on a Subgraph, [curation signal can be added](/subgraphs/developing/curating/) to attract Indexers that will support this feature. ### Conclusion diff --git a/website/src/pages/en/subgraphs/quick-start.mdx b/website/src/pages/en/subgraphs/quick-start.mdx index 8e2c64574e41..f093991cecb2 100644 --- a/website/src/pages/en/subgraphs/quick-start.mdx +++ b/website/src/pages/en/subgraphs/quick-start.mdx @@ -1,5 +1,6 @@ --- -title: Quick Start +title: Subgraphs Quick Start +sidebarTitle: Quick Start --- Create, deploy, and query a [Subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph Network. @@ -133,7 +134,7 @@ When your Subgraph is ready for a production environment, you can publish it to - It makes your Subgraph available to be indexed by the decentralized [Indexers](/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](/resources/roles/curating/) to add curation signal. +- It makes your Subgraph available for [Curators](/subgraphs/developing/curating/) to add curation signal. 1. Click **Publish** in Studio 2. Select network @@ -141,7 +142,7 @@ When your Subgraph is ready for a production environment, you can publish it to ![Publish a Subgraph on Subgraph Studio](/img/publish-sub-transfer.png) -> Curation with 3,000+ GRT is recommended to incentivize indexing. +> Add curation signal so Indexers pick up your Subgraph. See [how much signal to add](/subgraphs/developing/curating/#how-much-signal-to-add). ## Path 2: CLI Approach diff --git a/website/src/pages/en/subgraphs/tooling/_meta.js b/website/src/pages/en/subgraphs/tooling/_meta.js index b3f12a1e7bd1..c1494edd5c02 100644 --- a/website/src/pages/en/subgraphs/tooling/_meta.js +++ b/website/src/pages/en/subgraphs/tooling/_meta.js @@ -3,7 +3,7 @@ import titles from './_meta-titles.json' export default { 'subgraph-mcp': titles['subgraph-mcp'] ?? '', skills: 'SKILLs', - 'contract-analyzer': 'Smart Contract Analysis with Cana CLI', + 'contract-analyzer': 'Smart Contract Analysis', 'subgraph-uncrashable': 'Subgraph Uncrashable', 'subgraph-linter': 'Subgraph Linter', 'unit-testing-framework': 'Matchstick Unit Testing', diff --git a/website/src/supportedNetworks/customContent/_subgraph-community.mdx b/website/src/supportedNetworks/customContent/_subgraph-community.mdx index 895164c142b4..fe89262c6faf 100644 --- a/website/src/supportedNetworks/customContent/_subgraph-community.mdx +++ b/website/src/supportedNetworks/customContent/_subgraph-community.mdx @@ -167,13 +167,13 @@ Query your Subgraph at `http://localhost:8000/subgraphs/name/subgraph-0/` until Publishing a Subgraph is an on-chain action that: -- makes it available for [Curators](/resources/roles/curating/) to add signal that attracts Indexers, +- makes it available for [Curators](/subgraphs/developing/curating/) to add signal that attracts Indexers, - makes your Subgraph available for decentralized [Indexers](/indexing/overview/) to index, - and makes it publicly searchable and queryable in [Graph Explorer](https://thegraph.com/explorer/). To publish, open your Subgraph in the [Subgraph Studio](https://thegraph.com/studio/) dashboard and click **Publish**. Connect your wallet, add metadata (name, description, image), and confirm the transaction. Publishing happens on Arbitrum One, where The Graph's protocol contracts live, not on {props.chainName}. For details, see [Publishing a Subgraph](/subgraphs/developing/deploying-publishing/publishing-a-subgraph/), which also covers publishing from the CLI with `graph publish`. -> [!TIP] During the publish transaction, you can add GRT in curation signal to save on gas fees. Signal tells Indexers that your Subgraph is worth indexing. Any Subgraph with GRT or more signal ; without signal, no Indexer is incentivized to pick up your Subgraph. +> [!TIP] During the publish transaction, you can add GRT in curation signal to save on gas fees. [Signal](/subgraphs/developing/curating/) tells Indexers that your Subgraph is worth indexing. Any Subgraph with GRT or more signal ; without signal, no Indexer is incentivized to pick up your Subgraph. #### Step 5: Query your Subgraph