Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions nginx.conf
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down Expand Up @@ -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;
Expand Down Expand Up @@ -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;
Expand Down
10 changes: 6 additions & 4 deletions website/route-lockfile.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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/
Expand All @@ -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/
Expand Down
28 changes: 28 additions & 0 deletions website/src/components/HashRedirect.tsx
Original file line number Diff line number Diff line change
@@ -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<string, string>
}

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
}
1 change: 1 addition & 0 deletions website/src/components/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down
2 changes: 2 additions & 0 deletions website/src/layout/Layout.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ import {
CodeBlock,
CodeBlockTabs,
DocSearch,
HashRedirect,
Heading,
Image,
NavigationGroup,
Expand Down Expand Up @@ -616,6 +617,7 @@ export default function Layout({ pageOpts, children }: NextraThemeLayoutProps<Fr
pre: CodeBlock,
CodeBlock,
CodeBlockTabs,
HashRedirect,
// TODO: Build and use `ExperimentalTable`
table: Table,
VideoEmbed,
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,7 @@ Query routing and paying for queries (covered in [Routing Queries to Indexers](/

On chains where indexing rewards are enabled, the built-in mechanism is curation. Indexing rewards are funded by new GRT issuance (currently at 2-3% annually) and distributed to Subgraphs in proportion to the curation signal on them. Signaling on a Subgraph therefore does two things: it tells Indexers the Subgraph is worth indexing, and it directs a share of indexing rewards to whoever indexes it. More signal means more Indexers are willing to allocate to and sync that Subgraph.

As of December 2022, curation on The Graph Network uses a flat bonding curve (see [GIP-0039: Curation v1.x](https://forum.thegraph.com/t/gip-0039-curation-v1-x/3613)). Under a flat curve, curation shares are minted at a constant price rather than along a rising curve, which means:

- **Predictable cost:** signaling a given amount of GRT gets an Operator a proportional, predictable share, without an early-curator price advantage that a rising curve would create.
- **Less speculative dynamics:** because shares are not cheaper for being early, curation behaves more like a straightforward signal of demand than a trading game.
- **Simple mental model for operators:** to attract indexing on a rewards-enabled chain, add signal proportional to how much indexing attention an Operator wants to attract, and expect a proportional response.

For a Gateway Operator, the practical move is to signal (or encourage their consumers to signal) on the Subgraphs an Operator needs served, often paired with the publication flow when a Subgraph is first published (see [Enabling Publication Flows](/gateways/subgraphs/consumer-side/publication-flows/)). A select amount of self-signal at publishing time is a common way to bootstrap indexing on a fresh Subgraph. As a rough guide to the quality of service each level of signal tends to attract. As of August 2026, the recommended signal is:

- **10,000 GRT:** typically attracts 5+ Indexers, the level to aim for when a Subgraph is serving production traffic and an Operator wants redundancy well beyond the three Indexers a Gateway selects per query.
- **5,000 GRT:** typically attracts 3+ Indexers, enough to cover a Gateway's per-query selection so that no single Indexer's outage leaves the Subgraph unserved.
- **1,000 GRT:** typically attracts 1-2 Indexers, a reasonable starting point for a fresh or low-volume Subgraph, but thin enough that availability depends on very few operators.
For a Gateway Operator, the practical move is to signal (or encourage their consumers to signal) on the Subgraphs an Operator needs served, often paired with the publication flow when a Subgraph is first published (see [Enabling Publication Flows](/gateways/subgraphs/consumer-side/publication-flows/)). A select amount of self-signal at publishing time is a common way to bootstrap indexing on a fresh Subgraph. Aim for enough signal to attract at least three Indexers, so a Gateway's per-query selection is covered and no single Indexer's outage leaves the Subgraph unserved. For recommended signal amounts and curation costs, see [How Much Signal to Add](/subgraphs/developing/curating/#how-much-signal-to-add).

## Chains without Indexing Rewards

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@ The mapping flow is worth understanding before modifying it. `handleSubmitQoSPay

### Step 5: Publish and Operate

Deploy to Subgraph Studio, test against live submissions, and publish to The Graph Network so consumers can query it through the normal path. Signal enough curation to attract Indexers; see [Incentivizing Syncs](/gateways/subgraphs/supply-side/incentivizing-syncs/) for the levels that tend to attract how many.
Deploy to Subgraph Studio, test against live submissions, and publish to The Graph Network so consumers can query it through the normal path. Signal enough curation to attract Indexers; see [How Much Signal to Add](/subgraphs/developing/curating/#how-much-signal-to-add) for the levels that tend to attract how many.

Ongoing operational concerns:

Expand Down
2 changes: 1 addition & 1 deletion website/src/pages/en/indexing/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Indexers are node operators in The Graph Network that stake Graph Tokens (GRT) i

GRT that is staked in the protocol is subject to a thawing period and can be slashed if Indexers are malicious and serve incorrect data to applications or if they index incorrectly. Indexers also earn rewards for delegated stake from Delegators, to contribute to the network.

Indexers select Subgraphs to index based on the Subgraph’s curation signal, where Curators stake GRT in order to indicate which Subgraphs are high-quality and should be prioritized. Consumers (eg. applications) can also set parameters for which Indexers process queries for their Subgraphs and set preferences for query fee pricing.
Indexers select Subgraphs to index based on the Subgraph’s [curation signal](/subgraphs/developing/curating/), where Curators deposit GRT in order to indicate which Subgraphs are high-quality and should be prioritized. Consumers (eg. applications) can also set parameters for which Indexers process queries for their Subgraphs and set preferences for query fee pricing.

## FAQ

Expand Down
2 changes: 1 addition & 1 deletion website/src/pages/en/resources/_meta-titles.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
"roles": "Additional Roles"
"delegating": "Delegating"
}
5 changes: 3 additions & 2 deletions website/src/pages/en/resources/_meta.js
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ import titles from './_meta-titles.json'
export default {
glossary: '',
tokenomics: '',
benefits: '',
roles: titles.roles ?? '',
'getting-grt': 'Getting GRT',
'bridging-grt': 'Bridging GRT',
delegating: titles.delegating ?? '',
}
51 changes: 51 additions & 0 deletions website/src/pages/en/resources/bridging-grt.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
title: Bridging GRT
---

The Graph Network launched on Ethereum Mainnet in 2020. To lower gas costs for everyone who uses the protocol, The Graph moved to Arbitrum One, an Ethereum Layer 2. Today all protocol activity happens on Arbitrum One, including staking, delegation, curation, indexing rewards, and Subgraph Studio billing.

GRT still exists on both networks. If you hold GRT on Ethereum Mainnet, you need to bridge it to Arbitrum One before you can use it on The Graph. This page applies to every role: Delegators, Indexers, Subgraph developers, and token holders.

## GRT on Arbitrum One vs. Ethereum Mainnet

| | Arbitrum One | Ethereum Mainnet |
| --- | --- | --- |
| Used by The Graph protocol | Yes | No |
| Pay for queries in Subgraph Studio | Yes | Studio can bridge it for you during deposit (see below) |
| Stake, delegate, or curate | Yes | No |
| Gas paid in | ETH on Arbitrum One | ETH on Ethereum Mainnet |
| GRT token contract | [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) | [0xc944E90C64B2c07662A292be6244BDf05Cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) |

> 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.
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading
Loading