diff --git a/website/src/pages/ar/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ar/ai-suite/graph-assistant/faq.mdx index 8addf9935524..fddfa82ba974 100644 --- a/website/src/pages/ar/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ar/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? @@ -23,4 +23,4 @@ Yes, 10 questions per hour. 5. What if the Assistant can't interpret my question? -When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. +When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum One?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. diff --git a/website/src/pages/ar/ai-suite/graph-assistant/how-to-guide.mdx b/website/src/pages/ar/ai-suite/graph-assistant/how-to-guide.mdx index 463130894ad8..de53e29c3308 100644 --- a/website/src/pages/ar/ai-suite/graph-assistant/how-to-guide.mdx +++ b/website/src/pages/ar/ai-suite/graph-assistant/how-to-guide.mdx @@ -51,6 +51,6 @@ You don't need to write queries or understand a Subgraph's schema, you simply as **Cross-Chain Comparison** - “Show me the 7-day trading volume of XYZ on Ethereum vs. Polygon.” -- “How many XYZ swaps occurred on Arbitrum yesterday?” +- “How many XYZ swaps occurred on Arbitrum One yesterday?” To get started follow the [quickstart](/ai-suite/graph-assistant/quick-start/) and explore its capabilities. diff --git a/website/src/pages/ar/archived/_meta-titles.json b/website/src/pages/ar/archived/_meta-titles.json index 9501304a4305..1292b0582b34 100644 --- a/website/src/pages/ar/archived/_meta-titles.json +++ b/website/src/pages/ar/archived/_meta-titles.json @@ -1,3 +1,3 @@ { - "arbitrum": "Scaling with Arbitrum" + "arbitrum": "Scaling with Arbitrum One" } diff --git a/website/src/pages/ar/archived/arbitrum-faq.mdx b/website/src/pages/ar/archived/arbitrum-faq.mdx new file mode 100644 index 000000000000..29481ead71f1 --- /dev/null +++ b/website/src/pages/ar/archived/arbitrum-faq.mdx @@ -0,0 +1,79 @@ +--- +title: Arbitrum One FAQ +--- + +Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum One Billing FAQs. + +## Why did The Graph implement an L2 Solution? + +By scaling The Graph on L2, network participants can now benefit from: + +- Upwards of 26x savings on gas fees + +- سرعة أكبر في المعاملات + +- Security inherited from Ethereum + +Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of Subgraphs. Developers can deploy and update Subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of Subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas. + +The Graph community decided to move forward with Arbitrum One last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion. + +## What do I need to do to use The Graph on L2? + +The Graph’s billing system accepts GRT on Arbitrum One, and users will need ETH on Arbitrum One to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One. + +Consequently, to pay for queries, you need GRT on Arbitrum One. Here are a few different ways to achieve this: + +- If you already have GRT on Ethereum, you can bridge it to Arbitrum One. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges: + - [The Arbitrum One Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) + - [TransferTo](https://transferto.xyz/swap) + +- If you have other assets on Arbitrum One, you can swap them for GRT through a swapping protocol like Uniswap. + +- Alternatively, you can acquire GRT directly on Arbitrum One through a decentralized exchange. + +Once you have GRT on Arbitrum One, you can add it to your billing balance. + +To take advantage of using The Graph on L2, use this dropdown switcher to toggle between chains. + +![Dropdown switcher to toggle Arbitrum One](/img/arbitrum-screenshot-toggle.png) + +## As a Subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? + +Network participants must move to Arbitrum One to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. + +All indexing rewards are now entirely on Arbitrum One. + +## Were there any risks associated with scaling the network to L2? + +All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf). + +Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20). + +## Are existing Subgraphs on Ethereum working? + +All Subgraphs are now on Arbitrum One. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your Subgraphs operate seamlessly. + +## Does GRT have a new smart contract deployed on Arbitrum One? + +Yes, GRT has an additional [smart contract on Arbitrum One](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational. + +## Billing on Arbitrum One FAQs + +## What do I need to do about the GRT in my billing balance? + +Nothing! Your GRT has been securely migrated to Arbitrum One and is being used to pay for queries as you read this. + +## How do I know my funds have migrated securely to Arbitrum One? + +All GRT billing balances have already been successfully migrated to Arbitrum One. You can view the billing contract on Arbitrum One [here](https://arbiscan.io/address/0x1B07D3344188908Fb6DEcEac381f3eE63C48477a). + +## How do I know the Arbitrum One bridge is secure? + +The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the-graph-l2-bridge-contest) to ensure safety and security for all users. + +## What do I need to do if I'm adding fresh GRT from my Ethereum mainnet wallet? + +Adding GRT to your Arbitrum One billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum One and fill your API keys in one transaction. + +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/src/pages/ar/archived/arbitrum/arbitrum-faq.mdx b/website/src/pages/ar/archived/arbitrum/arbitrum-faq.mdx index 3ba1bf36fb9d..29481ead71f1 100644 --- a/website/src/pages/ar/archived/arbitrum/arbitrum-faq.mdx +++ b/website/src/pages/ar/archived/arbitrum/arbitrum-faq.mdx @@ -1,8 +1,8 @@ --- -title: Arbitrum FAQ +title: Arbitrum One FAQ --- -Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs. +Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum One Billing FAQs. ## Why did The Graph implement an L2 Solution? @@ -16,33 +16,33 @@ By scaling The Graph on L2, network participants can now benefit from: Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of Subgraphs. Developers can deploy and update Subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of Subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas. -The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion. +The Graph community decided to move forward with Arbitrum One last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion. ## What do I need to do to use The Graph on L2? -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. +The Graph’s billing system accepts GRT on Arbitrum One, and users will need ETH on Arbitrum One to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One. -Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this: +Consequently, to pay for queries, you need GRT on Arbitrum One. 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: - - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) +- If you already have GRT on Ethereum, you can bridge it to Arbitrum One. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges: + - [The Arbitrum One Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) - [TransferTo](https://transferto.xyz/swap) -- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap. +- If you have other assets on Arbitrum One, you can swap them for GRT through a swapping protocol like Uniswap. -- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange. +- Alternatively, you can acquire GRT directly on Arbitrum One through a decentralized exchange. -Once you have GRT on Arbitrum, you can add it to your billing balance. +Once you have GRT on Arbitrum One, you can add it to your billing balance. To take advantage of using The Graph on L2, use this dropdown switcher to toggle between chains. -![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png) +![Dropdown switcher to toggle Arbitrum One](/img/arbitrum-screenshot-toggle.png) ## As a Subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum One to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. -All indexing rewards are now entirely on Arbitrum. +All indexing rewards are now entirely on Arbitrum One. ## Were there any risks associated with scaling the network to L2? @@ -52,28 +52,28 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing Subgraphs on Ethereum working? -All Subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your Subgraphs operate seamlessly. +All Subgraphs are now on Arbitrum One. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your Subgraphs operate seamlessly. -## Does GRT have a new smart contract deployed on Arbitrum? +## Does GRT have a new smart contract deployed on Arbitrum One? -Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational. +Yes, GRT has an additional [smart contract on Arbitrum One](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational. -## Billing on Arbitrum FAQs +## Billing on Arbitrum One FAQs ## What do I need to do about the GRT in my billing balance? -Nothing! Your GRT has been securely migrated to Arbitrum and is being used to pay for queries as you read this. +Nothing! Your GRT has been securely migrated to Arbitrum One and is being used to pay for queries as you read this. -## How do I know my funds have migrated securely to Arbitrum? +## How do I know my funds have migrated securely to Arbitrum One? -All GRT billing balances have already been successfully migrated to Arbitrum. You can view the billing contract on Arbitrum [here](https://arbiscan.io/address/0x1B07D3344188908Fb6DEcEac381f3eE63C48477a). +All GRT billing balances have already been successfully migrated to Arbitrum One. You can view the billing contract on Arbitrum One [here](https://arbiscan.io/address/0x1B07D3344188908Fb6DEcEac381f3eE63C48477a). -## How do I know the Arbitrum bridge is secure? +## How do I know the Arbitrum One bridge is secure? The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the-graph-l2-bridge-contest) to ensure safety and security for all users. ## What do I need to do if I'm adding fresh GRT from my Ethereum mainnet wallet? -Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. +Adding GRT to your Arbitrum One billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum One and fill your API keys in one transaction. Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx index 965c96f7355a..c18517ae2441 100644 --- a/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,19 +14,19 @@ These tools will require you to follow a specific set of steps depending on what ### هل يمكنني استخدام نفس المحفظة التي استخدمها في Ethereum mainnet؟ -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum One wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. -Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. +Wallets on EVM blockchains like Ethereum and Arbitrum One are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum One without having to do anything else. -The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum, it won't exist with the same address on Arbitrum. A new multisig must be created first on Arbitrum, and may get a different address. +The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum, it won't exist with the same address on Arbitrum One. A new multisig must be created first on Arbitrum One, and may get a different address. ### What happens if I don’t finish my transfer in 7 days? -The L2 Transfer Tools use Arbitrum’s native mechanism to send messages from L1 to L2. This mechanism is called a “retryable ticket” and is used by all native token bridges, including the Arbitrum GRT bridge. You can read more about retryable tickets in the [Arbitrum docs](https://docs.arbitrum.io/arbos/l1-to-l2-messaging). +The L2 Transfer Tools use Arbitrum One’s native mechanism to send messages from L1 to L2. This mechanism is called a “retryable ticket” and is used by all native token bridges, including the Arbitrum One GRT bridge. You can read more about retryable tickets in the [Arbitrum One docs](https://docs.arbitrum.io/arbos/l1-to-l2-messaging). -When you transfer your assets (Subgraph, stake, delegation or curation) to L2, a message is sent through the Arbitrum GRT bridge which creates a retryable ticket in L2. The transfer tool includes some ETH value in the transaction, that is used to 1) pay to create the ticket and 2) pay for the gas to execute the ticket in L2. However, because gas prices might vary in the time until the ticket is ready to execute in L2, it is possible that this auto-execution attempt fails. When that happens, the Arbitrum bridge will keep the retryable ticket alive for up to 7 days, and anyone can retry “redeeming” the ticket (which requires a wallet with some ETH bridged to Arbitrum). +When you transfer your assets (Subgraph, stake, delegation or curation) to L2, a message is sent through the Arbitrum One GRT bridge which creates a retryable ticket in L2. The transfer tool includes some ETH value in the transaction, that is used to 1) pay to create the ticket and 2) pay for the gas to execute the ticket in L2. However, because gas prices might vary in the time until the ticket is ready to execute in L2, it is possible that this auto-execution attempt fails. When that happens, the Arbitrum One bridge will keep the retryable ticket alive for up to 7 days, and anyone can retry “redeeming” the ticket (which requires a wallet with some ETH bridged to Arbitrum One). -This is what we call the “Confirm” step in all the transfer tools - it will run automatically in most cases, as the auto-execution is most often successful, but it is important that you check back to make sure it went through. If it doesn’t succeed and there are no successful retries in 7 days, the Arbitrum bridge will discard the ticket, and your assets (Subgraph, stake, delegation or curation) will be lost and can’t be recovered. The Graph core devs have a monitoring system in place to detect these situations and try to redeem the tickets before it’s too late, but it is ultimately your responsibility to ensure your transfer is completed in time. If you’re having trouble confirming your transaction, please reach out using [this form](https://noteforms.com/forms/notionform-l2-transfer-tooling-issues-0ogqfu?notionforms=1&utm_source=notionforms) and core devs will be there help you. +This is what we call the “Confirm” step in all the transfer tools - it will run automatically in most cases, as the auto-execution is most often successful, but it is important that you check back to make sure it went through. If it doesn’t succeed and there are no successful retries in 7 days, the Arbitrum One bridge will discard the ticket, and your assets (Subgraph, stake, delegation or curation) will be lost and can’t be recovered. The Graph core devs have a monitoring system in place to detect these situations and try to redeem the tickets before it’s too late, but it is ultimately your responsibility to ensure your transfer is completed in time. If you’re having trouble confirming your transaction, please reach out using [this form](https://noteforms.com/forms/notionform-l2-transfer-tooling-issues-0ogqfu?notionforms=1&utm_source=notionforms) and core devs will be there help you. ### I started my delegation/stake/curation transfer and I'm not sure if it made it through to L2, how can I confirm that it was transferred correctly? @@ -46,13 +46,13 @@ To transfer your Subgraph, you will need to complete the following steps: 2. انتظر 20 دقيقة للتأكيد -3. Confirm Subgraph transfer on Arbitrum\* +3. Confirm Subgraph transfer on Arbitrum One\* -4. Finish publishing Subgraph on Arbitrum +4. Finish publishing Subgraph on Arbitrum One 5. جدث عنوان URL للاستعلام (مستحسن) -\*Note that you must confirm the transfer within 7 days otherwise your Subgraph may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). +\*Note that you must confirm the transfer within 7 days otherwise your Subgraph may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum One. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). ### من أين يجب أن أبدأ التحويل ؟ @@ -60,7 +60,7 @@ You can initiate your transfer from the [Subgraph Studio](https://thegraph.com/s ### How long do I need to wait until my Subgraph is transferred -يستغرق وقت النقل حوالي 20 دقيقة. يعمل جسر Arbitrum في الخلفية لإكمال نقل الجسر تلقائيًا. في بعض الحالات ، قد ترتفع تكاليف الغاز وستحتاج إلى تأكيد المعاملة مرة أخرى. +يستغرق وقت النقل حوالي 20 دقيقة. يعمل جسر Arbitrum One في الخلفية لإكمال نقل الجسر تلقائيًا. في بعض الحالات ، قد ترتفع تكاليف الغاز وستحتاج إلى تأكيد المعاملة مرة أخرى. ### Will my Subgraph still be discoverable after I transfer it to L2? @@ -70,11 +70,11 @@ Your Subgraph will only be discoverable on the network it is published to. For e To take advantage of the Subgraph transfer tool, your Subgraph must be already published to Ethereum mainnet and must have some curation signal owned by the wallet that owns the Subgraph. If your Subgraph is not published, it is recommended you simply publish directly on Arbitrum One - the associated gas fees will be considerably lower. If you want to transfer a published Subgraph but the owner account hasn't curated any signal on it, you can signal a small amount (e.g. 1 GRT) from that account; make sure to choose "auto-migrating" signal. -### What happens to the Ethereum mainnet version of my Subgraph after I transfer to Arbitrum? +### What happens to the Ethereum mainnet version of my Subgraph after I transfer to Arbitrum One? -After transferring your Subgraph to Arbitrum, the Ethereum mainnet version will be deprecated. We recommend you update your query URL within 48 hours. However, there is a grace period in place that keeps your mainnet URL functioning so that any third-party dapp support can be updated. +After transferring your Subgraph to Arbitrum One, the Ethereum mainnet version will be deprecated. We recommend you update your query URL within 48 hours. However, there is a grace period in place that keeps your mainnet URL functioning so that any third-party dapp support can be updated. -### بعد النقل ، هل أحتاج أيضًا إلى إعادة النشر على Arbitrum؟ +### بعد النقل ، هل أحتاج أيضًا إلى إعادة النشر على Arbitrum One بعد فترة النقل البالغة 20 دقيقة ، ستحتاج إلى تأكيد النقل لإكمال النقل ، أداة النقل ستوجهك للقيام بذلك. سيستمر دعم L1 endpoint الخاص بك خلال فترة النقل وفترة السماح. من المستحسن أن تقوم بتحديثه عندما يكون ذلك مناسبًا لك. @@ -82,7 +82,7 @@ After transferring your Subgraph to Arbitrum, the Ethereum mainnet version will It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### هل يتم نشر وتخطيط الإصدار بنفس الطريقة في الـ L2 كما هو الحال في شبكة Ethereum Ethereum mainnet؟ +### هل يتم نشر وتخطيط الإصدار بنفس الطريقة في الـ L2 كما هو الحال في شبكة Ethereum Mainnet؟ Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. @@ -110,21 +110,21 @@ Once transferred, your Ethereum mainnet version of this Subgraph will be depreca 1. ابدأ نقل التفويض على شبكة Ethereum mainnet 2. انتظر 20 دقيقة للتأكيد -3. قم بتأكيد نقل التفويض على Arbitrum +3. قم بتأكيد نقل التفويض على Arbitrum One -\*\*\*\*You must confirm the transaction to complete the delegation transfer on Arbitrum. This step must be completed within 7 days or the delegation could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). +\*\*\*\*You must confirm the transaction to complete the delegation transfer on Arbitrum One. This step must be completed within 7 days or the delegation could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum One. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). ### ماذا يحدث لمكافآتي إذا بدأت عملية تحويل وكان لا يزال التخصيص مفتوحا على Ethereum mainnet؟ -If the Indexer to whom you're delegating is still operating on L1, when you transfer to Arbitrum you will forfeit any delegation rewards from open allocations on Ethereum mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer. +If the Indexer to whom you're delegating is still operating on L1, when you transfer to Arbitrum One you will forfeit any delegation rewards from open allocations on Ethereum mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer. ### ماذا يحدث إذا كان المفهرس الذي أفوضه حاليًا غير موجود في Arbitrum One؟ -لن يتم تمكين أداة النقل L2 إلا إذا قام المفهرس الذي فوضته بتحويل حصته إلى Arbitrum. +لن يتم تمكين أداة النقل L2 إلا إذا قام المفهرس الذي فوضته بتحويل حصته إلى Arbitrum One. ### هل يملك المفوضين خيارا للتفويض إلى مفهرس آخر؟ -If you wish to delegate to another Indexer, you can transfer to the same Indexer on Arbitrum, then undelegate and wait for the thawing period. After this, you can select another active Indexer to delegate to. +If you wish to delegate to another Indexer, you can transfer to the same Indexer on Arbitrum One, then undelegate and wait for the thawing period. After this, you can select another active Indexer to delegate to. ### ماذا لو لم أتمكن من العثور على المفهرس الذي قمت بالتوفيض إليه في L2؟ @@ -150,9 +150,9 @@ A 20-minute confirmation is required for delegation transfer. Please note that a Yes! The process is a bit different because vesting contracts can't forward the ETH needed to pay for the L2 gas, so you need to deposit it beforehand. If your vesting contract is not fully vested, you will also have to first initialize a counterpart vesting contract on L2 and will only be able to transfer the delegation to this L2 vesting contract. The UI on Explorer can guide you through this process when you've connected to Explorer using the vesting lock wallet. -### Does my Arbitrum vesting contract allow releasing GRT just like on mainnet? +### Does my Arbitrum One vesting contract allow releasing GRT just like on mainnet? -No, the vesting contract that is created on Arbitrum will not allow releasing any GRT until the end of the vesting timeline, i.e. until your contract is fully vested. This is to prevent double spending, as otherwise it would be possible to release the same amounts on both layers. +No, the vesting contract that is created on Arbitrum One will not allow releasing any GRT until the end of the vesting timeline, i.e. until your contract is fully vested. This is to prevent double spending, as otherwise it would be possible to release the same amounts on both layers. If you'd like to release GRT from the vesting contract, you can transfer them back to the L1 vesting contract using Explorer: in your Arbitrum One profile, you will see a banner saying you can transfer GRT back to the mainnet vesting contract. This requires a transaction on Arbitrum One, waiting 7 days, and a final transaction on mainnet, as it uses the same native bridging mechanism from the GRT bridge. @@ -182,7 +182,7 @@ Eventually, if the Council keeps approving the indexing rewards increases in L2, If you can contact the Indexer, you can encourage them to use the L2 Transfer Tools so that Delegators can transfer delegations to their L2 Indexer address. ​ -### My Indexer is also on Arbitrum, but I don't see a button to transfer the delegation in my profile. Why is that? +### My Indexer is also on Arbitrum One, but I don't see a button to transfer the delegation in my profile. Why is that? ​It is possible that the Indexer has set up operations on L2, but hasn't used the L2 transfer tools to transfer stake. The L1 smart contracts will therefore not know about the Indexer's L2 address. If you can contact the Indexer, you can encourage them to use the transfer tool so that Delegators can transfer delegations to their L2 Indexer address. ​ @@ -224,7 +224,7 @@ When a Subgraph is deprecated you have the option to withdraw your signal. Simil ## Indexer Stake(حصة المفهرس) -### كيف يمكنني تحويل حصتي إلى Arbitrum؟ +### كيف يمكنني تحويل حصتي إلى Arbitrum One > Disclaimer: If you are currently unstaking any portion of your GRT on your Indexer, you will not be able to use L2 Transfer Tools. @@ -236,9 +236,9 @@ When a Subgraph is deprecated you have the option to withdraw your signal. Simil 2. انتظر 20 دقيقة للتأكيد -3. Confirm stake transfer on Arbitrum +3. Confirm stake transfer on Arbitrum One -\*Note that you must confirm the transfer within 7 days otherwise your stake may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). +\*Note that you must confirm the transfer within 7 days otherwise your stake may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum One. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). ### هل سيتم تحويل حصتي بالكامل؟ @@ -248,9 +248,9 @@ When a Subgraph is deprecated you have the option to withdraw your signal. Simil ملاحظة: يجب أن تفي بالحد الأدنى من متطلبات الحصة على L2 في المرة الأولى التي تستخدم فيها أداة التحويل. يجب أن يرسل المفهرسون 100 ألف GRT كحد أدنى (عند استدعاء هذه الوظيفة في المرة الأولى). في حالة ترك جزء من الحصة على L1 ، يجب أن يكون أيضًا أكثر من 100 ألف GRT كحد أدنى وأن يكون كافيًا (جنبًا إلى جنب مع التفويضات) لتغطية مخصصاتك المفتوحة. -### كم من الوقت لدي لتأكيد تحويل حصتي إلى Arbitrum؟ +### كم من الوقت لدي لتأكيد تحويل حصتي إلى Arbitrum One -\ _ \ _ \ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة. +\ _ \ _ \ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum One. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة. ### ماذا لو كان لدي تخصيصات مفتوحة؟ @@ -264,13 +264,13 @@ When a Subgraph is deprecated you have the option to withdraw your signal. Simil ستستغرق أداة النقل L2 حوالي 20 دقيقة لإكمال تحويل حصتك. -### هل يجب أن أقوم بالفهرسة على Arbitrum قبل أن أنقل حصتي؟ +### هل يجب أن أقوم بالفهرسة على Arbitrum One قبل أن أنقل حصتي؟ You can effectively transfer your stake first before setting up indexing, but you will not be able to claim any rewards on L2 until you allocate to Subgraphs on L2, index them, and present POIs. ### هل يستطيع المفوضون نقل تفويضهم قبل نقل indexing stake الخاص بي؟ -لا ، لكي يقوم المفوضون بنقل GRT المفوضة إلى Arbitrum ، يجب أن يكون المفهرس الذي يتم التفويض إليه نشطًا في L2. +لا ، لكي يقوم المفوضون بنقل GRT المفوضة إلى Arbitrum One ، يجب أن يكون المفهرس الذي يتم التفويض إليه نشطًا في L2. ### Can I transfer my stake if I'm using a GRT vesting contract / token lock wallet? @@ -294,7 +294,7 @@ Yes! The process is a bit different, because vesting contracts can't forward the 2. انتظر 20 دقيقة للتأكيد -3. قم بالتأكيد على نقل الاستحقاق على Arbitrum +3. قم بالتأكيد على نقل الاستحقاق على Arbitrum One ### كيف يمكنني تحويل عقد الاستحقاق الخاص بي إذا كنت مخولًا جزئيًا فقط؟ @@ -337,11 +337,11 @@ Yes! The process is a bit different, because vesting contracts can't forward the إذا لم تقم بتحويل أي رصيد من عقود الاستحقاق إلى L2 ، وكان عقد الاستحقاق الخاص بك مخولًا بالكامل ، فلا يجب عليك تحويل عقد الاستحقاق الخاص بك إلى L2. بدلاً من ذلك ، يمكنك استخدام أدوات التحويل لتعيين عنوان محفظة L2 ، وتحويل حصتك أو تفويضك مباشرةً إلى هذه المحفظة العادية على L2. -### أنا أستخدم عقد الاستحقاق الخاص بي للقيام بالتخزين (staking) في mainnet. هل يمكنني تحويل حصتي إلى Arbitrum؟ +### أنا أستخدم عقد الاستحقاق الخاص بي للقيام بالتخزين (staking) في mainnet. هل يمكنني تحويل حصتي إلى Arbitrum One نعم ، ولكن إذا كان عقدك لا يزال مستحقًا ، فيمكنك فقط نقل الحصة بحيث تكون مملوكة لعقد الاستحقاق L2 الخاص بك. يجب أولاً تهيئة عقد L2 هذا عن طريق تحويل بعض رصيد GRT باستخدام أداة تحويل عقد الاستحقاق في Explorer. إذا كان عقدك مخولًا بالكامل ، فيمكنك تحويل حصتك إلى أي عنوان على L2 ، ولكن يجب عليك تعيينها مسبقًا وإيداع بعض ETH لأداة التحويل L2 لدفع ثمن غاز L2. -### أنا أستخدم عقد الاستحقاق الخاص بي للتفويض على mainnet. هل يمكنني نقل تفويضاتي إلى Arbitrum؟ +### أنا أستخدم عقد الاستحقاق الخاص بي للتفويض على mainnet. هل يمكنني نقل تفويضاتي إلى Arbitrum One نعم ، ولكن إذا كان عقدك لا يزال مستحقًا ، فيمكنك فقط نقل التفويض بحيث يكون مملوكًا لعقد الاستحقاق L2 الخاص بك. يجب أولاً تهيئة عقد L2 هذا عن طريق تحويل بعضا من رصيد GRT باستخدام أداة تحويل عقد الاستحقاق في Explorer. إذا كان عقدك مخولًا بالكامل ، فيمكنك نقل تفويضك إلى أي عنوان في L2 ، ولكن يجب عليك تعيينه مسبقًا وإيداع بعض ETH لأداة التحويل L2 لدفع ثمن غاز L2. @@ -349,7 +349,7 @@ Yes! The process is a bit different, because vesting contracts can't forward the نعم ، في المرة الأولى التي تقوم فيها بتحويل رصيد وإعداد عقد استحقاق L2 ، يمكنك تحديد مستفيد من L2. تأكد من أن هذا المستفيد عبارة عن محفظة يمكنها إجراء المعاملات على Arbitrum One ، يجب أن تكون EOA أو multisig تم نشرها على Arbitrum One. -إذا كان عقدك مخولًا بالكامل ، فلن تقوم بإعداد عقد استحقاق على L2 ؛ بدلاً من ذلك ، ستقوم بتعيين عنوان محفظة L2 وستكون هذه هي المحفظة المستلمة لحصتك أو تفويضك في Arbitrum. +إذا كان عقدك مخولًا بالكامل ، فلن تقوم بإعداد عقد استحقاق على L2 ؛ بدلاً من ذلك ، ستقوم بتعيين عنوان محفظة L2 وستكون هذه هي المحفظة المستلمة لحصتك أو تفويضك في Arbitrum One. ### عقدي مخول بالكامل. هل يمكنني نقل حصتي أو تفويضي إلى عنوان آخر ليس عقداً استحقاقيا على L2؟ @@ -377,11 +377,11 @@ Yes! The process is a bit different, because vesting contracts can't forward the \ \* إذا لزم الأمر -أنت تستخدم عنوان عقد. -\*\*\*\*You must confirm your transaction to complete the balance transfer on Arbitrum. This step must be completed within 7 days or the balance could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). +\*\*\*\*You must confirm your transaction to complete the balance transfer on Arbitrum One. This step must be completed within 7 days or the balance could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum One. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). ### My vesting contract shows 0 GRT so I cannot transfer it, why is this and how do I fix it? -​To initialize your L2 vesting contract, you need to transfer a nonzero amount of GRT to L2. This is required by the Arbitrum GRT bridge that is used by the L2 Transfer Tools. The GRT must come from the vesting contract's balance, so it does not include staked or delegated GRT. +​To initialize your L2 vesting contract, you need to transfer a nonzero amount of GRT to L2. This is required by the Arbitrum One GRT bridge that is used by the L2 Transfer Tools. The GRT must come from the vesting contract's balance, so it does not include staked or delegated GRT. If you've staked or delegated all your GRT from the vesting contract, you can manually send a small amount like 1 GRT to the vesting contract address from anywhere else (e.g. from another wallet, or an exchange). ​ @@ -411,4 +411,4 @@ You will see a banner on your profile prompting you to transfer your stake or de ### ماذا لو لم أرغب في نقل عقد الاستحقاق الخاص بي إلى L2؟ -يمكنك الاستمرار في التخزين / التفويض على L1. بمرور الوقت ، قد ترغب في التفكير في الانتقال إلى L2 لتمكين المكافآت هناك حيث يتوسع البروتوكول في Arbitrum. لاحظ أن أدوات التحويل هذه مخصصة لمنح العقود المسموح لها بالمشاركة والتفويض في البروتوكول. إذا كان عقدك لا يسمح بالتخزين أو التفويض ، أو كان قابلاً للإلغاء ، فلا توجد أداة نقل متاحة. ستظل قادرًا على سحب GRT من L1 عندما يكون ذلك متاحًا. +يمكنك الاستمرار في التخزين / التفويض على L1. بمرور الوقت ، قد ترغب في التفكير في الانتقال إلى L2 لتمكين المكافآت هناك حيث يتوسع البروتوكول في Arbitrum One. لاحظ أن أدوات التحويل هذه مخصصة لمنح العقود المسموح لها بالمشاركة والتفويض في البروتوكول. إذا كان عقدك لا يسمح بالتخزين أو التفويض ، أو كان قابلاً للإلغاء ، فلا توجد أداة نقل متاحة. ستظل قادرًا على سحب GRT من L1 عندما يكون ذلك متاحًا. diff --git a/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx index 5863ff2de0a2..5cc6908cb73c 100644 --- a/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/src/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -6,7 +6,7 @@ title: L2 Transfer Tools Guide Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. -## How to transfer your Subgraph to Arbitrum (L2) +## How to transfer your Subgraph to Arbitrum One (L2) @@ -18,7 +18,7 @@ When you publish or upgrade your Subgraph to The Graph Network, you're interacti ## Understanding what happens with signal, your L1 Subgraph and query URLs -Transferring a Subgraph to Arbitrum uses the Arbitrum GRT bridge, which in turn uses the native Arbitrum bridge, to send the Subgraph to L2. The "transfer" will deprecate the Subgraph on mainnet and send the information to re-create the Subgraph on L2 using the bridge. It will also include the Subgraph owner's signaled GRT, which must be more than zero for the bridge to accept the transfer. +Transferring a Subgraph to Arbitrum One uses the Arbitrum One GRT bridge, which in turn uses the native Arbitrum One bridge, to send the Subgraph to L2. The "transfer" will deprecate the Subgraph on mainnet and send the information to re-create the Subgraph on L2 using the bridge. It will also include the Subgraph owner's signaled GRT, which must be more than zero for the bridge to accept the transfer. When you choose to transfer the Subgraph, this will convert all of the Subgraph's curation signal to GRT. This is equivalent to "deprecating" the Subgraph on mainnet. The GRT corresponding to your curation will be sent to L2 together with the Subgraph, where they will be used to mint signal on your behalf. @@ -32,13 +32,13 @@ Queries to the L2 Subgraph will need to be done to a different URL (on `arbitrum When you published your Subgraph on mainnet, you used a connected wallet to create the Subgraph, and this wallet owns the NFT that represents this Subgraph and allows you to publish updates. -When transferring the Subgraph to Arbitrum, you can choose a different wallet that will own this Subgraph NFT on L2. +When transferring the Subgraph to Arbitrum One, you can choose a different wallet that will own this Subgraph NFT on L2. إذا كنت تستخدم محفظة "عادية" مثل MetaMask (حساب مملوك خارجيًا EOA ، محفظة ليست بعقد ذكي) ، فهذا اختياري ويوصى بالاحتفاظ بعنوان المالك نفسه كما في L1. If you're using a smart contract wallet, like a multisig (e.g. a Safe), then choosing a different L2 wallet address is mandatory, as it is most likely that this account only exists on mainnet and you will not be able to make transactions on Arbitrum using this wallet. If you want to keep using a smart contract wallet or multisig, create a new wallet on Arbitrum and use its address as the L2 owner of your Subgraph. -**It is very important to use a wallet address that you control, and that can make transactions on Arbitrum. Otherwise, the Subgraph will be lost and cannot be recovered.** +**It is very important to use a wallet address that you control, and that can make transactions on Arbitrum One. Otherwise, the Subgraph will be lost and cannot be recovered.** ## التحضير لعملية النقل: إنشاء جسر لـبعض ETH diff --git a/website/src/pages/ar/archived/arbitrum/tap.mdx b/website/src/pages/ar/archived/arbitrum/tap.mdx new file mode 100644 index 000000000000..0dac61949de9 --- /dev/null +++ b/website/src/pages/ar/archived/arbitrum/tap.mdx @@ -0,0 +1,189 @@ +--- +title: GraphTally Guide +--- + +Learn about The Graph’s new payment system, **GraphTally** [(previously Timeline Aggregation Protocol)](https://docs.rs/tap_core/latest/tap_core/index.html). This system provides fast, efficient microtransactions with minimized trust. + +## نظره عامة + +GraphTally is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features: + +- Efficiently handles micropayments. +- Adds a layer of consolidations to onchain transactions and costs. +- Allows Indexers control of receipts and payments, guaranteeing payment for queries. +- It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders. + +### Specifics + +GraphTally allows a sender to make multiple payments to a receiver, **Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process. + +For each query, the gateway will send you a `signed receipt` that is stored on your database. Then, these queries will be aggregated by a `tap-agent` through a request. Afterwards, you’ll receive a RAV. You can update a RAV by sending it with newer receipts and this will generate a new RAV with an increased value. + +### RAV Details + +- It’s money that is waiting to be sent to the blockchain. + +- It will continue to send requests to aggregate and ensure that the total value of non-aggregated receipts does not exceed the `amount willing to lose`. + +- Each RAV can be redeemed once in the contracts, which is why they are sent after the allocation is closed. + +### Redeeming RAV + +As long as you run `tap-agent` and `indexer-agent`, everything will be executed automatically. The following provides a detailed breakdown of the process: + +1. An Indexer closes allocation. + +2. ` period, tap-agent` takes all pending receipts for that specific allocation and requests an aggregation into a RAV, marking it as `last`. + +3. `indexer-agent` takes all the last RAVS and sends redeem requests to the blockchain, which will update the value of `redeem_at`. + +4. During the `` period, `indexer-agent` monitors if the blockchain has any reorganizations that revert the transaction. + - If it was reverted, the RAV is resent to the blockchain. If it was not reverted, it gets marked as `final`. + +## Blockchain Addresses + +### Contracts + +| Contract | Arbitrum One (42161) | Arbitrum Sepolia (421614) | +| ------------------- | -------------------------------------------- | -------------------------------------------- | +| TAP Verifier | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | +| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | +| Escrow | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | + +### Gateway + +| Component | Edge and Node Mainnet (Arbitrum One) | Edge and Node Testnet (Arbitrum Sepolia) | +| ---------- | --------------------------------------------- | --------------------------------------------- | +| Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | +| Signers | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | +| Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` | + +### Prerequisites + +In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query updates. You can use The Graph Network to query or host yourself on your `graph-node`. + +- [Graph TAP Arbitrum Sepolia Subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD) +- [Graph TAP Arbitrum One Subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1) + +> Note: `indexer-agent` does not currently handle the indexing of this Subgraph like it does for the network Subgraph deployment. As a result, you have to index it manually. + +## Migration Guide + +### Software versions + +The required software version can be found [here](https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md#latest-releases). + +### Steps + +1. **Indexer Agent** + - Follow the [same process](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components). + - Give the new argument `--tap-subgraph-endpoint` to activate the new GraphTally codepaths and enable redeeming of RAVs. + +2. **Indexer Service** + - Fully replace your current configuration with the [new Indexer Service rs](https://github.com/graphprotocol/indexer-rs). It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs). + - Like the older version, you can scale Indexer Service horizontally easily. It is still stateless. + +3. **TAP Agent** + - Run _one_ single instance of [TAP Agent](https://github.com/graphprotocol/indexer-rs) at all times. It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs). + +4. **Configure Indexer Service and TAP Agent** + + Configuration is a TOML file shared between `indexer-service` and `tap-agent`, supplied with the argument `--config /path/to/config.toml`. + + Check out the full [configuration](https://github.com/graphprotocol/indexer-rs/blob/main/config/maximal-config-example.toml) and the [default values](https://github.com/graphprotocol/indexer-rs/blob/main/config/default_values.toml) + +For minimal configuration, use the following template: + +```bash +# You will have to change *all* the values below to match your setup. +# +# Some of the config below are global graph network values, which you can find here: +# +# +# Pro tip: if you need to load some values from the environment into this config, you +# can overwrite with environment variables. For example, the following can be replaced +# by [PREFIX]_DATABASE_POSTGRESURL, where PREFIX can be `INDEXER_SERVICE` or `TAP_AGENT`: +# +# [database] +# postgres_url = "postgresql://indexer:${POSTGRES_PASSWORD}@postgres:5432/indexer_components_0" + +[indexer] +indexer_address = "0x1111111111111111111111111111111111111111" +operator_mnemonic = "celery smart tip orange scare van steel radio dragon joy alarm crane" + +[database] +# The URL of the Postgres database used for the indexer components. The same database +# that is used by the `indexer-agent`. It is expected that `indexer-agent` will create +# the necessary tables. +postgres_url = "postgres://postgres@postgres:5432/postgres" + +[graph_node] +# URL to your graph-node's query endpoint +query_url = "" +# URL to your graph-node's status endpoint +status_url = "" + +[subgraphs.network] +# Query URL for the Graph Network Subgraph. +query_url = "" +# Optional, deployment to look for in the local `graph-node`, if locally indexed. +# Locally indexing the Subgraph is recommended. +# NOTE: Use `query_url` or `deployment_id` only +deployment_id = "Qmaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" + +[subgraphs.escrow] +# Query URL for the Escrow Subgraph. +query_url = "" +# Optional, deployment to look for in the local `graph-node`, if locally indexed. +# Locally indexing the Subgraph is recommended. +# NOTE: Use `query_url` or `deployment_id` only +deployment_id = "Qmaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" + +[blockchain] +# The chain ID of the network that the graph network is running on +chain_id = 1337 +# Contract address of TAP's receipt aggregate voucher (RAV) verifier. +receipts_verifier_address = "0x2222222222222222222222222222222222222222" + +######################################## +# Specific configurations to tap-agent # +######################################## +[tap] +# This is the amount of fees you are willing to risk at any given time. For ex. +# if the sender stops supplying RAVs for long enough and the fees exceed this +# amount, the indexer-service will stop accepting queries from the sender +# until the fees are aggregated. +# NOTE: Use strings for decimal values to prevent rounding errors +# e.g: +# max_amount_willing_to_lose_grt = "0.1" +max_amount_willing_to_lose_grt = 20 + +[tap.sender_aggregator_endpoints] +# Key-Value of all senders and their aggregator endpoints +# This one below is for the E&N testnet gateway for example. +0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com" +``` + +Notes: + +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. + +**Log Level** + +- You can set the log level by using the `RUST_LOG` environment variable. +- It’s recommended that you set it to `RUST_LOG=indexer_tap_agent=debug,info`. + +## Monitoring + +### Metrics + +All components expose the port 7300 to be queried by prometheus. + +### Grafana Dashboard + +You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) and import. + +### Launchpad + +Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer) diff --git a/website/src/pages/ar/archived/sunrise.mdx b/website/src/pages/ar/archived/sunrise.mdx index 71262f22e7d8..fd2f29d3191d 100644 --- a/website/src/pages/ar/archived/sunrise.mdx +++ b/website/src/pages/ar/archived/sunrise.mdx @@ -21,9 +21,9 @@ During the upgrade process, owners of hosted service Subgraphs could upgrade the No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. -### Why were Subgraphs published to Arbitrum, did it start indexing a different network? +### Why were Subgraphs published to Arbitrum One, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new Subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that Subgraphs are published to, but Subgraphs can index any of the [supported networks](/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new Subgraphs are published to The Graph Network on Arbitrum One so that Indexers can support them. Arbitrum One is the network that Subgraphs are published to, but Subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer diff --git a/website/src/pages/ar/contracts.mdx b/website/src/pages/ar/contracts.mdx index 3938844149c1..785140c69ad5 100644 --- a/website/src/pages/ar/contracts.mdx +++ b/website/src/pages/ar/contracts.mdx @@ -6,7 +6,7 @@ import { ProtocolContractsTable } from '@/contracts' Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository](https://github.com/graphprotocol/contracts) to learn more. -## Arbitrum +## Arbitrum One This is the principal deployment of The Graph Network. @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum One. diff --git a/website/src/pages/ar/indexing/tap.mdx b/website/src/pages/ar/indexing/tap.mdx index 4a5ca8013ecc..0dac61949de9 100644 --- a/website/src/pages/ar/indexing/tap.mdx +++ b/website/src/pages/ar/indexing/tap.mdx @@ -44,7 +44,7 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed ### Contracts -| Contract | Arbitrum Mainnet (42161) | Arbitrum Sepolia (421614) | +| Contract | Arbitrum One (42161) | Arbitrum Sepolia (421614) | | ------------------- | -------------------------------------------- | -------------------------------------------- | | TAP Verifier | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | | AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | @@ -52,7 +52,7 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed ### Gateway -| Component | Edge and Node Mainnet (Arbitrum Mainnet) | Edge and Node Testnet (Arbitrum Sepolia) | +| Component | Edge and Node Mainnet (Arbitrum One) | Edge and Node Testnet (Arbitrum Sepolia) | | ---------- | --------------------------------------------- | --------------------------------------------- | | Sender | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467` | `0xC3dDf37906724732FfD748057FEBe23379b0710D` | | Signers | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211` | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE` | diff --git a/website/src/pages/ar/token-api/faq.mdx b/website/src/pages/ar/token-api/faq.mdx index 2e523e4e3776..dacb5ce0b255 100644 --- a/website/src/pages/ar/token-api/faq.mdx +++ b/website/src/pages/ar/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/cs/ai-suite/graph-assistant/faq.mdx b/website/src/pages/cs/ai-suite/graph-assistant/faq.mdx index 8addf9935524..fddfa82ba974 100644 --- a/website/src/pages/cs/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/cs/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? @@ -23,4 +23,4 @@ Yes, 10 questions per hour. 5. What if the Assistant can't interpret my question? -When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. +When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum One?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. diff --git a/website/src/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx index 439e83f3864b..68fab656be89 100644 --- a/website/src/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ Po uplynutí 20minutového okna pro převod budete muset převod potvrdit transa It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Je publikování a verzování na L2 stejné jako na mainnet Ethereum Ethereum? +### Je publikování a verzování na L2 stejné jako na Mainnet Ethereum? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/cs/contracts.mdx b/website/src/pages/cs/contracts.mdx index 3938844149c1..4ef3d6c31f5f 100644 --- a/website/src/pages/cs/contracts.mdx +++ b/website/src/pages/cs/contracts.mdx @@ -6,7 +6,7 @@ import { ProtocolContractsTable } from '@/contracts' Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository](https://github.com/graphprotocol/contracts) to learn more. -## Arbitrum +## Arbitrum One This is the principal deployment of The Graph Network. diff --git a/website/src/pages/cs/token-api/faq.mdx b/website/src/pages/cs/token-api/faq.mdx index e7e5881a7d8d..a405b76625cf 100644 --- a/website/src/pages/cs/token-api/faq.mdx +++ b/website/src/pages/cs/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/de/ai-suite/graph-assistant/faq.mdx b/website/src/pages/de/ai-suite/graph-assistant/faq.mdx index 8addf9935524..fddfa82ba974 100644 --- a/website/src/pages/de/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/de/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? @@ -23,4 +23,4 @@ Yes, 10 questions per hour. 5. What if the Assistant can't interpret my question? -When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. +When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum One?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. diff --git a/website/src/pages/de/token-api/faq.mdx b/website/src/pages/de/token-api/faq.mdx index 1546ba39c454..7f252b730ffe 100644 --- a/website/src/pages/de/token-api/faq.mdx +++ b/website/src/pages/de/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/en/ai-suite/graph-assistant/faq.mdx b/website/src/pages/en/ai-suite/graph-assistant/faq.mdx index 8addf9935524..223e1807dd89 100644 --- a/website/src/pages/en/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/en/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? @@ -23,4 +23,4 @@ Yes, 10 questions per hour. 5. What if the Assistant can't interpret my question? -When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum or XYZ on Arbitrum?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. +When the Assistant fails to parse your intent (for example, ambiguous token name, missing context, or an unsupported request), it will prompt you for clarification. For instance, it might ask, “Did you mean XYZ on Ethereum Mainnet or XYZ on Arbitrum One?” or “Please specify a date range for this query.” If you continue to see parsing errors, check that you're using correct token symbols or specifying networks and time frames clearly. diff --git a/website/src/pages/en/ai-suite/graph-assistant/how-to-guide.mdx b/website/src/pages/en/ai-suite/graph-assistant/how-to-guide.mdx index 463130894ad8..833dfc5d3bef 100644 --- a/website/src/pages/en/ai-suite/graph-assistant/how-to-guide.mdx +++ b/website/src/pages/en/ai-suite/graph-assistant/how-to-guide.mdx @@ -35,13 +35,13 @@ You don't need to write queries or understand a Subgraph's schema, you simply as **Token Insights** -- “What are the top 10 tokens by market cap on Ethereum right now?” +- “What are the top 10 tokens by market cap on Ethereum Mainnet right now?” - “How many XYZ did I receive between May 1 and May 15?” **Historical Data Retrieval** - “Fetch the token price history of XYZ for the last six months.” -- “What was the average gas price on Ethereum during April?” +- “What was the average gas price on Ethereum Mainnet during April?” **Portfolio Monitoring** @@ -50,7 +50,7 @@ You don't need to write queries or understand a Subgraph's schema, you simply as **Cross-Chain Comparison** -- “Show me the 7-day trading volume of XYZ on Ethereum vs. Polygon.” -- “How many XYZ swaps occurred on Arbitrum yesterday?” +- “Show me the 7-day trading volume of XYZ on Ethereum Mainnet vs. Polygon Mainnet.” +- “How many XYZ swaps occurred on Arbitrum One yesterday?” To get started follow the [quickstart](/ai-suite/graph-assistant/quick-start/) and explore its capabilities. diff --git a/website/src/pages/en/ai-suite/graph-assistant/quick-start.mdx b/website/src/pages/en/ai-suite/graph-assistant/quick-start.mdx index 13f8478b8d2b..b4a2e0388e7b 100644 --- a/website/src/pages/en/ai-suite/graph-assistant/quick-start.mdx +++ b/website/src/pages/en/ai-suite/graph-assistant/quick-start.mdx @@ -32,7 +32,7 @@ In the input bar, type a natural-language query (everyday language). Example: ```yaml -Show me the 24-hour trading volume of XYZ token on Ethereum +Show me the 24-hour trading volume of XYZ token on Ethereum Mainnet ``` > [!NOTE] Disclaimer: By using Graph Assistant, you acknowledge that your requests may be logged and used to improve the performance of the AI interface. Do not share sensitive, personal, or private information. diff --git a/website/src/pages/en/archived/arbitrum/arbitrum-faq.mdx b/website/src/pages/en/archived/arbitrum/arbitrum-faq.mdx index 09065157ef6b..1d4d957e102e 100644 --- a/website/src/pages/en/archived/arbitrum/arbitrum-faq.mdx +++ b/website/src/pages/en/archived/arbitrum/arbitrum-faq.mdx @@ -14,19 +14,19 @@ By scaling The Graph on L2, network participants can now benefit from: - Faster transaction speed -- Security inherited from Ethereum +- Security inherited from Ethereum Mainnet Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of Subgraphs. Developers can deploy and update Subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of Subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas. -The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion. +The Graph community decided to move forward with Arbitrum One last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion. ## What do I need to do to use The Graph on L2? -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. +The Graph’s billing system accepts GRT on Arbitrum One, and users will need ETH on Arbitrum One to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One. Consequently, 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: +- If you already have GRT on Ethereum Mainnet, you can bridge it to Arbitrum One. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges: - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161) - [TransferTo](https://transferto.xyz/swap) @@ -51,13 +51,13 @@ All smart contracts have been thoroughly [audited](https://github.com/graphproto Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20). -## Are existing Subgraphs on Ethereum working? +## Are existing Subgraphs on Ethereum Mainnet working? All Subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your Subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? -Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational. +Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum Mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational. ## Billing on Arbitrum FAQs @@ -73,7 +73,7 @@ All GRT billing balances have already been successfully migrated to Arbitrum. Yo The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the-graph-l2-bridge-contest) to ensure safety and security for all users. -## What do I need to do if I'm adding fresh GRT from my Ethereum mainnet wallet? +## What do I need to do if I'm adding fresh GRT from my Ethereum Mainnet wallet? Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. diff --git a/website/src/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx index e3ab8ea47d14..4a12ec8c7a3b 100644 --- a/website/src/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,17 +14,17 @@ For each network participant, a set of L2 Transfer Tools are available to make t These tools will require you to follow a specific set of steps depending on what your role is within The Graph and what you are transferring to L2. -### Can I use the same wallet I use on Ethereum mainnet? +### Can I use the same wallet I use on Ethereum Mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum Mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. -Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. +Wallets on EVM blockchains like Ethereum Mainnet and Arbitrum One are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum Mainnet will also work on Arbitrum One without having to do anything else. -The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum, it won't exist with the same address on Arbitrum. A new multisig must be created first on Arbitrum, and may get a different address. +The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum Mainnet, it won't exist with the same address on Arbitrum One. A new multisig must be created first on Arbitrum One, and may get a different address. ### What happens if I don’t finish my transfer in 7 days? -The L2 Transfer Tools use Arbitrum’s native mechanism to send messages from L1 to L2. This mechanism is called a “retryable ticket” and is used by all native token bridges, including the Arbitrum GRT bridge. You can read more about retryable tickets in the [Arbitrum docs](https://docs.arbitrum.io/arbos/l1-to-l2-messaging). +The L2 Transfer Tools use Arbitrum’s native mechanism to send messages from L1 to L2. This mechanism is called a “retryable ticket” and is used by all native token bridges, including the Arbitrum GRT bridge. You can read more about retryable tickets in the [Arbitrum One docs](https://docs.arbitrum.io/arbos/l1-to-l2-messaging). When you transfer your assets (Subgraph, stake, delegation or curation) to L2, a message is sent through the Arbitrum GRT bridge which creates a retryable ticket in L2. The transfer tool includes some ETH value in the transaction, that is used to 1) pay to create the ticket and 2) pay for the gas to execute the ticket in L2. However, because gas prices might vary in the time until the ticket is ready to execute in L2, it is possible that this auto-execution attempt fails. When that happens, the Arbitrum bridge will keep the retryable ticket alive for up to 7 days, and anyone can retry “redeeming” the ticket (which requires a wallet with some ETH bridged to Arbitrum). @@ -44,7 +44,7 @@ If you have the L1 transaction hash (which you can find by looking at the recent To transfer your Subgraph, you will need to complete the following steps: -1. Initiate the transfer on Ethereum mainnet +1. Initiate the transfer on Ethereum Mainnet 2. Wait 20 minutes for confirmation @@ -66,15 +66,15 @@ The transfer time takes approximately 20 minutes. The Arbitrum bridge is working ### Will my Subgraph still be discoverable after I transfer it to L2? -Your Subgraph will only be discoverable on the network it is published to. For example, if your Subgraph is on Arbitrum One, then you can only find it in Explorer on Arbitrum One and will not be able to find it on Ethereum. Please ensure that you have Arbitrum One selected in the network switcher at the top of the page to ensure you are on the correct network.  After the transfer, the L1 Subgraph will appear as deprecated. +Your Subgraph will only be discoverable on the network it is published to. For example, if your Subgraph is on Arbitrum One, then you can only find it in Explorer on Arbitrum One and will not be able to find it on Ethereum Mainnet. Please ensure that you have Arbitrum One selected in the network switcher at the top of the page to ensure you are on the correct network.  After the transfer, the L1 Subgraph will appear as deprecated. ### Does my Subgraph need to be published to transfer it? -To take advantage of the Subgraph transfer tool, your Subgraph must be already published to Ethereum mainnet and must have some curation signal owned by the wallet that owns the Subgraph. If your Subgraph is not published, it is recommended you simply publish directly on Arbitrum One - the associated gas fees will be considerably lower. If you want to transfer a published Subgraph but the owner account hasn't curated any signal on it, you can signal a small amount (e.g. 1 GRT) from that account; make sure to choose "auto-migrating" signal. +To take advantage of the Subgraph transfer tool, your Subgraph must be already published to Ethereum Mainnet and must have some curation signal owned by the wallet that owns the Subgraph. If your Subgraph is not published, it is recommended you simply publish directly on Arbitrum One - the associated gas fees will be considerably lower. If you want to transfer a published Subgraph but the owner account hasn't curated any signal on it, you can signal a small amount (e.g. 1 GRT) from that account; make sure to choose "auto-migrating" signal. -### What happens to the Ethereum mainnet version of my Subgraph after I transfer to Arbitrum? +### What happens to the Ethereum Mainnet version of my Subgraph after I transfer to Arbitrum? -After transferring your Subgraph to Arbitrum, the Ethereum mainnet version will be deprecated. We recommend you update your query URL within 48 hours. However, there is a grace period in place that keeps your mainnet URL functioning so that any third-party dapp support can be updated. +After transferring your Subgraph to Arbitrum, the Ethereum Mainnet version will be deprecated. We recommend you update your query URL within 48 hours. However, there is a grace period in place that keeps your mainnet URL functioning so that any third-party dapp support can be updated. ### After I transfer, do I also need to re-publish on Arbitrum? @@ -84,7 +84,7 @@ After the 20 minute transfer window, you will need to confirm the transfer with It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet? +### Is publishing and versioning the same on L2 as Ethereum Mainnet? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. @@ -94,13 +94,13 @@ If you've chosen auto-migrating signal, 100% of your own curation will move with Other Curators can choose whether to withdraw their fraction of GRT, or also transfer it to L2 to mint signal on the same Subgraph. -### Can I move my Subgraph back to Ethereum mainnet after I transfer? +### Can I move my Subgraph back to Ethereum Mainnet after I transfer? -Once transferred, your Ethereum mainnet version of this Subgraph will be deprecated. If you would like to move back to mainnet, you will need to redeploy and publish back to mainnet. However, transferring back to Ethereum mainnet is strongly discouraged as indexing rewards will eventually be distributed entirely on Arbitrum One. +Once transferred, your Ethereum Mainnet version of this Subgraph will be deprecated. If you would like to move back to mainnet, you will need to redeploy and publish back to mainnet. However, transferring back to Ethereum Mainnet is strongly discouraged as indexing rewards will eventually be distributed entirely on Arbitrum One. ### Why do I need bridged ETH to complete my transfer? -Gas fees on Arbitrum One are paid using bridged ETH (i.e. ETH that has been bridged to Arbitrum One). However, the gas fees are significantly lower when compared to Ethereum mainnet. +Gas fees on Arbitrum One are paid using bridged ETH (i.e. ETH that has been bridged to Arbitrum One). However, the gas fees are significantly lower when compared to Ethereum Mainnet. ## Delegation @@ -110,15 +110,15 @@ Gas fees on Arbitrum One are paid using bridged ETH (i.e. ETH that has been brid To transfer your delegation, you will need to complete the following steps: -1. Initiate delegation transfer on Ethereum mainnet +1. Initiate delegation transfer on Ethereum Mainnet 2. Wait 20 minutes for confirmation 3. Confirm delegation transfer on Arbitrum \*\*\*\*You must confirm the transaction to complete the delegation transfer on Arbitrum. This step must be completed within 7 days or the delegation could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol). -### What happens to my rewards if I initiate a transfer with an open allocation on Ethereum mainnet? +### What happens to my rewards if I initiate a transfer with an open allocation on Ethereum Mainnet? -If the Indexer to whom you're delegating has started transferring stake to L2 but is still operating on L1, when you transfer to Arbitrum you will forfeit any delegation rewards from open allocations on Ethereum mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer. Other than this, your unrealized rewards will be transferred to L2 with the delegation. +If the Indexer to whom you're delegating has started transferring stake to L2 but is still operating on L1, when you transfer to Arbitrum you will forfeit any delegation rewards from open allocations on Ethereum Mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer. Other than this, your unrealized rewards will be transferred to L2 with the delegation. If the Indexer has transferred all their stake to L2, they will not have open allocations on L1 and therefore all your rewards will be transferred to L2 with the delegation transfer. @@ -140,7 +140,7 @@ The L2 transfer tool will always move your delegation to the same Indexer you de ### Am I subject to the cooldown period or can I withdraw immediately after using the L2 delegation transfer tool? -The transfer tool allows you to immediately move to L2. If you would like to undelegate you will have to wait for the thawing period. However, if an Indexer has transferred all of their stake to L2, you can withdraw on Ethereum mainnet immediately. +The transfer tool allows you to immediately move to L2. If you would like to undelegate you will have to wait for the thawing period. However, if an Indexer has transferred all of their stake to L2, you can withdraw on Ethereum Mainnet immediately. ### Can my rewards be negatively impacted if I do not transfer my delegation? @@ -202,7 +202,7 @@ The tokens that are being undelegated are "locked" and therefore cannot be trans To transfer your curation, you will need to complete the following steps: -1. Initiate signal transfer on Ethereum mainnet +1. Initiate signal transfer on Ethereum Mainnet 2. Specify an L2 Curator address\* @@ -216,7 +216,7 @@ When viewing the Subgraph details page, a banner will notify you that this Subgr ### What if I do not wish to move my curation to L2? -When a Subgraph is deprecated you have the option to withdraw your signal. Similarly, if a Subgraph has moved to L2, you can choose to withdraw your signal in Ethereum mainnet or send the signal to L2. +When a Subgraph is deprecated you have the option to withdraw your signal. Similarly, if a Subgraph has moved to L2, you can choose to withdraw your signal in Ethereum Mainnet or send the signal to L2. ### How do I know my curation successfully transferred? @@ -236,7 +236,7 @@ There is no bulk transfer option at this time. To transfer your stake, you will need to complete the following steps: -1. Initiate stake transfer on Ethereum mainnet +1. Initiate stake transfer on Ethereum Mainnet 2. Wait 20 minutes for confirmation @@ -258,11 +258,11 @@ Note: You must meet the minimum stake requirements on L2 the first time you use ### What if I have open allocations? -If you are not sending all of your stake, the L2 transfer tool will validate that at least the minimum 100k GRT remains in Ethereum mainnet and your remaining stake and delegation is enough to cover any open allocations. You may need to close open allocations if your GRT balance does not cover the minimums + open allocations. +If you are not sending all of your stake, the L2 transfer tool will validate that at least the minimum 100k GRT remains in Ethereum Mainnet and your remaining stake and delegation is enough to cover any open allocations. You may need to close open allocations if your GRT balance does not cover the minimums + open allocations. -### Using the transfer tools, is it necessary to wait 28 days to unstake on Ethereum mainnet before transferring? +### Using the transfer tools, is it necessary to wait 28 days to unstake on Ethereum Mainnet before transferring? -No, you can transfer your stake to L2 immediately, there's no need to unstake and wait before using the transfer tool. The 28-day wait only applies if you'd like to withdraw the stake back to your wallet, on Ethereum mainnet or L2. +No, you can transfer your stake to L2 immediately, there's no need to unstake and wait before using the transfer tool. The 28-day wait only applies if you'd like to withdraw the stake back to your wallet, on Ethereum Mainnet or L2. ### How long will it take to transfer my stake? @@ -294,7 +294,7 @@ Yes! The process is a bit different, because vesting contracts can't forward the To transfer your vesting, you will need to complete the following steps: -1. Initiate the vesting transfer on Ethereum mainnet +1. Initiate the vesting transfer on Ethereum Mainnet 2. Wait 20 minutes for confirmation @@ -373,7 +373,7 @@ To transfer your vesting contract to L2, you will send any GRT balance to L2 usi 3. Give protocol access to the vesting contract (will allow your contract to interact with the transfer tool) -4. Specify an L2 beneficiary address\* and initiate the balance transfer on Ethereum mainnet +4. Specify an L2 beneficiary address\* and initiate the balance transfer on Ethereum Mainnet 5. Wait 20 minutes for confirmation diff --git a/website/src/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/src/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx index 5c8aa0b30a65..bd720aeb72ce 100644 --- a/website/src/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/src/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -14,9 +14,9 @@ Some frequent questions about these tools are answered in the [L2 Transfer Tools ## Benefits of transferring your Subgraphs -The Graph's community and core devs have [been preparing](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) to move to Arbitrum over the past year. Arbitrum, a layer 2 or "L2" blockchain, inherits the security from Ethereum but provides drastically lower gas fees. +The Graph's community and core devs have [been preparing](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) to move to Arbitrum over the past year. Arbitrum, a layer 2 or "L2" blockchain, inherits the security from Ethereum Mainnet but provides drastically lower gas fees. -When you publish or upgrade your Subgraph to The Graph Network, you're interacting with smart contracts on the protocol and this requires paying for gas using ETH. By moving your Subgraphs to Arbitrum, any future updates to your Subgraph will require much lower gas fees. The lower fees, and the fact that curation bonding curves on L2 are flat, also make it easier for other Curators to curate on your Subgraph, increasing the rewards for Indexers on your Subgraph. This lower-cost environment also makes it cheaper for Indexers to index and serve your Subgraph. Indexing rewards will be increasing on Arbitrum and decreasing on Ethereum mainnet over the coming months, so more and more Indexers will be transferring their stake and setting up their operations on L2. +When you publish or upgrade your Subgraph to The Graph Network, you're interacting with smart contracts on the protocol and this requires paying for gas using ETH. By moving your Subgraphs to Arbitrum, any future updates to your Subgraph will require much lower gas fees. The lower fees, and the fact that curation bonding curves on L2 are flat, also make it easier for other Curators to curate on your Subgraph, increasing the rewards for Indexers on your Subgraph. This lower-cost environment also makes it cheaper for Indexers to index and serve your Subgraph. Indexing rewards will be increasing on Arbitrum and decreasing on Ethereum Mainnet over the coming months, so more and more Indexers will be transferring their stake and setting up their operations on L2. ## Understanding what happens with signal, your L1 Subgraph and query URLs diff --git a/website/src/pages/en/archived/sunrise.mdx b/website/src/pages/en/archived/sunrise.mdx index 71262f22e7d8..058fef0f71ee 100644 --- a/website/src/pages/en/archived/sunrise.mdx +++ b/website/src/pages/en/archived/sunrise.mdx @@ -23,7 +23,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were Subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new Subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that Subgraphs are published to, but Subgraphs can index any of the [supported networks](/supported-networks/) +The Graph Network was initially deployed on Ethereum Mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new Subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that Subgraphs are published to, but Subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer diff --git a/website/src/pages/en/indexing/overview.mdx b/website/src/pages/en/indexing/overview.mdx index 2ff92033e2f9..01322f5d1747 100644 --- a/website/src/pages/en/indexing/overview.mdx +++ b/website/src/pages/en/indexing/overview.mdx @@ -295,7 +295,7 @@ Deploy all resources with `kubectl apply -k $dir`. ### Graph Node -[Graph Node](https://github.com/graphprotocol/graph-node) is an open source Rust implementation that event sources the Ethereum blockchain to deterministically update a data store that can be queried via the GraphQL endpoint. Developers use Subgraphs to define their schema, and a set of mappings for transforming the data sourced from the blockchain and the Graph Node handles syncing the entire chain, monitoring for new blocks, and serving it via a GraphQL endpoint. +[Graph Node](https://github.com/graphprotocol/graph-node) is an open source Rust implementation that event sources the Ethereum Mainnet blockchain to deterministically update a data store that can be queried via the GraphQL endpoint. Developers use Subgraphs to define their schema, and a set of mappings for transforming the data sourced from the blockchain and the Graph Node handles syncing the entire chain, monitoring for new blocks, and serving it via a GraphQL endpoint. #### Getting started from source diff --git a/website/src/pages/en/token-api/faq.mdx b/website/src/pages/en/token-api/faq.mdx index 10248a43c1e5..a18c80dc8315 100644 --- a/website/src/pages/en/token-api/faq.mdx +++ b/website/src/pages/en/token-api/faq.mdx @@ -9,7 +9,7 @@ Get fast answers to easily integrate and scale with The Graph's high-performance ### Which blockchains are supported by the Token API? -Currently, the Token API supports Ethereum, BNB Smart Chain (BSC), Polygon, Optimism, Base, Unichain, Avalanche, Arbitrum One, and Solana. A full list of supported networks can be found under the Token API column [here](/supported-networks/). +Currently, the Token API supports Ethereum Mainnet, BNB Smart Chain (BSC Mainnet), Polygon Mainnet, Optimism Mainnet, Base Mainnet, Unichain Mainnet, Avalanche C-Chain, Arbitrum One, and Solana Mainnet. A full list of supported networks can be found under the Token API column [here](/supported-networks/). ### Does the Token API support NFTs? @@ -53,9 +53,9 @@ The Graph ecosystem is actively determining the [roadmap](https://thegraph.com/b ### What DEXs are supported by the Token API? -DEXs listed below are grouped by network and ordered by most swaps. Only verified DEXs with more than 10K swaps in 2025 have been listed. For a more detailed and comprehensive list of supported DEXs, you can query the /dexes/evm and /dexes/svm endpoints. +DEXs listed below are grouped by network and ordered by most swaps. Only verified DEXs with more than 10K swaps in 2025 have been listed. For a more detailed and comprehensive list of supported DEXs, you can query the `/v1/dexes/evm`, `/v1/dexes/svm`, or `/v1/dexes/tvm endpoints`. -#### Solana +#### Solana Mainnet **Full support of DEX protocol** @@ -79,12 +79,12 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - Lifinity Swap V2 - SolFi - Obric V2 -- stabble Stable Swap +- Stabble Stable Swap - Phoenix - ZeroFi - Openbook V2 - Invariant Swap -- stabble Weighted Swap +- Stabble Weighted Swap - GoonFi - 1Dex Program - Fluxbeam Program @@ -131,7 +131,7 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - GooseFX SSL - Serum DEX V3 -#### Ethereum +#### Ethereum Mainnet - Uniswap V2 - Uniswap V3 @@ -178,7 +178,7 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - Integral - Trader Joe -#### Polygon +#### Polygon Mainnet - Quickswap V2 - Uniswap V3 @@ -196,13 +196,13 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - DooarSwap - Elk -#### Unichain +#### Unichain Mainnet - Uniswap V4 - Uniswap V3 - Uniswap V2 -#### BSC +#### BSC Mainnet - PancakeSwap V2 - PancakeSwap V3 @@ -210,7 +210,7 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - PancakeSwap V1 - Biswap - ApeSwap V2 -- MDEX (BSC) +- MDEX - BabySwap - Nomiswap - Nomiswap Stable @@ -220,11 +220,16 @@ Swaps are being reported via Aggregator programs and do not include amm_pool fie - BakerySwap - SquadSwap -**Optimism** +#### Optimism Mainnet -Uniswap V3 Uniswap V4 Velodrome V3 Velodrome V2 Curve Beethoven X +- Uniswap V3 +- Uniswap V4 +- Velodrome V3 +- Velodrome V2 +- Curve +- Beethoven X -#### Avalanche +#### Avalanche C-Chain - Trader Joe V2.1 - Trader Joe V3 @@ -232,12 +237,12 @@ Uniswap V3 Uniswap V4 Velodrome V3 Velodrome V2 Curve Beethoven X - Pangolin V2 - Pangolin V1 - Elk Finance -- Uniswap V4 (Avalanche) +- Uniswap V4 - Lydia Finance - SushiSwap V2 - OliveSwap -#### Base +#### Base Mainnet - Uniswap V3 - Uniswap V2 @@ -249,6 +254,21 @@ Uniswap V3 Uniswap V4 Velodrome V3 Velodrome V2 Curve Beethoven X - Solidly V3 - Alien Base V2 +#### Tron Mainnet + +- SunSwap V1 (JustSwap) +- SunSwap V2 +- SunPump +- USwap +- SunSwap 1.5 (JustSwap) +- ISwap V1 +- JustMoney +- SocialSwap V2 +- ISwap V2 +- SocialSwap V1 +- WhiteSwap +- Oikos Swap V2 + ## MCP / LLM / AI ### Is there a time limit for LLM queries? @@ -281,7 +301,7 @@ NFT collections on supported chains contain a spam status field indicating wheth ### How do I retrieve the spam status for a collection? -See the spam_status field on the [`nft/collections/evm/{contract}`](/token-api/evm/get-nft-collections-evm-by-contract/) endpoint. +See the spam_status field on the [`/v1/evm/nft/collections/{contract}`](/token-api/evm-nfts/collections/) endpoint. ### Why am I seeing "pending" spam status? @@ -291,8 +311,13 @@ There are millions of collections and we only analyze for spam on demand. If you Spam detection is currently supported for the following chains: -- `mainnet` -- `base` +- Arbitrum One +- Avalanche C-Chain +- Base Mainnet +- BSC Mainnet +- Ethereum Mainnet +- Optimism Mainnet +- Polygon Mainnet We are working on fine-tuning the model to enable more chains. @@ -308,7 +333,7 @@ Reach out on [Discord](https://discord.gg/graphprotocol) in the [Token API](http ### I keep seeing a smart contract with addresses like `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` and `0x000000000000000000000000000000000000`. What is this? -The address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` is a sentinel (placeholder) address used to represent native tokens in EVM smart contracts. Since native tokens (ETH, BNB, AVAX, etc.) exist at the protocol level rather than as smart contracts, DeFi protocols need a placeholder address when their code expects contract addresses for all tokens. This address represents the native token of whatever chain you're on: ETH on Ethereum and its L2s (Base, Arbitrum, Optimism), BNB on BSC, AVAX on Avalanche, and so forth. +The address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` is a sentinel (placeholder) address used to represent native tokens in EVM smart contracts. Since native tokens (ETH, BNB, AVAX, etc.) exist at the protocol level rather than as smart contracts, DeFi protocols need a placeholder address when their code expects contract addresses for all tokens. This address represents the native token of whatever chain you're on: ETH on Ethereum Mainnet and its L2s (Base Mainnet, Arbitrum One, Optimism Mainnet), BNB on BSC Mainnet, AVAX on Avalanche C-Chain, and so forth. The address `0x0000000000000000000000000000000000000000` was introduced in Uniswap v4 for the same purpose. @@ -332,9 +357,9 @@ If you notice data inconsistencies, please report the issue on our [Discord](htt ### How do I specify a network? -You can query which networks are available with [this endpoint](https://token-api.thegraph.com/networks). Take note that the network IDs differ between the Token API and Subgraphs. For EVM networks, use EVM endpoints with the optional `network_id` parameter (e.g., `mainnet`, `bsc`, `base`, `arbitrum-one`, `optimism`, `polygon`, `unichain`) to target a specific chain. Without this parameter, the API defaults to Ethereum mainnet. +You can query which networks are available with [this endpoint](https://token-api.thegraph.com/networks). Take note that the network IDs differ between the Token API and Subgraphs. For EVM networks, use EVM endpoints with the optional `network_id` parameter (e.g., `mainnet`, `bsc`, `base`, `arbitrum-one`, `optimism`, `polygon`, `unichain`) to target a specific chain. Without this parameter, the API defaults to Ethereum Mainnet. -To query Solana, use the SVM endpoints. +To query Solana Mainnet, use the SVM endpoints. ### Why do I only see 10 results? How can I get more data? @@ -362,7 +387,7 @@ Large numeric values (like token amounts or supply) are returned as strings to a For EVM addresses, the API accepts hex addresses with either 42 or 40 characters, with or without the `0x` prefix. The endpoint is case-insensitive, so both lower and uppercase hex characters work. Ensure EVM addresses are exactly 42 characters, or 40 if you remove the prefix. For contract queries, use the token's contract address. For balance/transfer queries, use the wallet address. -SVM addresses are base58-encoded strings that are typically 32-44 characters long. They contain a mix of uppercase letters, lowercase letters, and numbers. Unlike Ethereum addresses which are hexadecimal and start with "0x", Solana addresses don't have a consistent prefix pattern. +SVM addresses are base58-encoded strings that are typically 32-44 characters long. They contain a mix of uppercase letters, lowercase letters, and numbers. Unlike Ethereum Mainnet addresses which are hexadecimal and start with "0x", Solana Mainnet addresses don't have a consistent prefix pattern. ### Do I need special headers besides authentication? diff --git a/website/src/pages/en/token-api/quick-start.mdx b/website/src/pages/en/token-api/quick-start.mdx index be9ec5c66518..94a4544a8ce1 100644 --- a/website/src/pages/en/token-api/quick-start.mdx +++ b/website/src/pages/en/token-api/quick-start.mdx @@ -68,17 +68,18 @@ Make sure to replace `` with the JWT Token generated from your API key. ## Chain and Feature Support -| Network | Tokens | Swaps | NFTs | -| ---------------- | :-----------------------: | :-----------------------: | :-----------------------: | -| Ethereum Mainnet | | | | -| BSC | | | | -| Base | | | | -| Unichain | | | | -| Arbitrum-One | | | | -| Optimism | | | | -| Polygon | | | | -| Avalanche | | | | -| Solana | | | ❌ Unsupported | +| Network | Tokens | Swaps | NFTs | +| ----------------- | :-----------------------: | :-----------------------: | :-----------------------: | +| Ethereum Mainnet | | | | +| BSC Mainnet | | | | +| Base Mainnet | | | | +| Unichain Mainnet | | | | +| Arbitrum One | | | | +| Optimism Mainnet | | | | +| Polygon Mainnet | | | | +| Avalanche C-Chain | | | | +| Solana Mainnet | | | ❌ Unsupported | +| Tron Mainnet | | | ❌ Unsupported | A full list of chain support for The Graph services can be found [here](/supported-networks/). diff --git a/website/src/pages/es/ai-suite/graph-assistant/faq.mdx b/website/src/pages/es/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/es/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/es/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/es/token-api/faq.mdx b/website/src/pages/es/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/es/token-api/faq.mdx +++ b/website/src/pages/es/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/fr/ai-suite/graph-assistant/faq.mdx b/website/src/pages/fr/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/fr/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/fr/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/fr/token-api/faq.mdx b/website/src/pages/fr/token-api/faq.mdx index ea49e94b2b6f..46c691597e29 100644 --- a/website/src/pages/fr/token-api/faq.mdx +++ b/website/src/pages/fr/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/hi/ai-suite/graph-assistant/faq.mdx b/website/src/pages/hi/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/hi/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/hi/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/hi/token-api/faq.mdx b/website/src/pages/hi/token-api/faq.mdx index 1e6133a3aa4b..fc6e553e6352 100644 --- a/website/src/pages/hi/token-api/faq.mdx +++ b/website/src/pages/hi/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/it/ai-suite/graph-assistant/faq.mdx b/website/src/pages/it/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/it/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/it/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx index 0dd870395760..03ab13e237b2 100644 --- a/website/src/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ Dopo la finestra di trasferimento di 20 minuti, dovrai confermare il trasferimen It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet? +### Is publishing and versioning the same on L2 as Ethereum Mainnet? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/it/token-api/faq.mdx b/website/src/pages/it/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/it/token-api/faq.mdx +++ b/website/src/pages/it/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/ja/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ja/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/ja/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ja/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/ja/token-api/faq.mdx b/website/src/pages/ja/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/ja/token-api/faq.mdx +++ b/website/src/pages/ja/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/ko/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ko/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/ko/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ko/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx index 62477d152eff..0383f30f2242 100644 --- a/website/src/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ After transferring your Subgraph to Arbitrum, the Ethereum mainnet version will It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### L2에서 Ethereum Ethereum 메인넷과 게시 및 버전 관리가 동일합니까? +### L2에서 Ethereum Mainnet 메인넷과 게시 및 버전 관리가 동일합니까? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/ko/token-api/faq.mdx b/website/src/pages/ko/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/ko/token-api/faq.mdx +++ b/website/src/pages/ko/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/mr/ai-suite/graph-assistant/faq.mdx b/website/src/pages/mr/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/mr/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/mr/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/mr/token-api/faq.mdx b/website/src/pages/mr/token-api/faq.mdx index f5190f267970..7a0e77ae93ec 100644 --- a/website/src/pages/mr/token-api/faq.mdx +++ b/website/src/pages/mr/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/nl/ai-suite/graph-assistant/faq.mdx b/website/src/pages/nl/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/nl/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/nl/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/nl/token-api/faq.mdx b/website/src/pages/nl/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/nl/token-api/faq.mdx +++ b/website/src/pages/nl/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/pl/ai-suite/graph-assistant/faq.mdx b/website/src/pages/pl/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/pl/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/pl/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/pl/token-api/faq.mdx b/website/src/pages/pl/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/pl/token-api/faq.mdx +++ b/website/src/pages/pl/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/pt/ai-suite/graph-assistant/faq.mdx b/website/src/pages/pt/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/pt/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/pt/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/pt/token-api/faq.mdx b/website/src/pages/pt/token-api/faq.mdx index a220592a5ecf..42c7dacc6ebd 100644 --- a/website/src/pages/pt/token-api/faq.mdx +++ b/website/src/pages/pt/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/ro/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ro/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/ro/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ro/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx index 7edde3d0cbcd..a741d6783d2a 100644 --- a/website/src/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ After the 20 minute transfer window, you will need to confirm the transfer with It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet? +### Is publishing and versioning the same on L2 as Ethereum Mainnet? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/ro/token-api/faq.mdx b/website/src/pages/ro/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/ro/token-api/faq.mdx +++ b/website/src/pages/ro/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/ru/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ru/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/ru/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ru/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/ru/token-api/faq.mdx b/website/src/pages/ru/token-api/faq.mdx index 9d6edb42b482..426be5c759aa 100644 --- a/website/src/pages/ru/token-api/faq.mdx +++ b/website/src/pages/ru/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/sv/ai-suite/graph-assistant/faq.mdx b/website/src/pages/sv/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/sv/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/sv/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/sv/token-api/faq.mdx b/website/src/pages/sv/token-api/faq.mdx index 123b4867805e..946208314dfb 100644 --- a/website/src/pages/sv/token-api/faq.mdx +++ b/website/src/pages/sv/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/tr/ai-suite/graph-assistant/faq.mdx b/website/src/pages/tr/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/tr/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/tr/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/tr/token-api/faq.mdx b/website/src/pages/tr/token-api/faq.mdx index ba8708e750c4..dc2d35645abb 100644 --- a/website/src/pages/tr/token-api/faq.mdx +++ b/website/src/pages/tr/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/uk/ai-suite/graph-assistant/faq.mdx b/website/src/pages/uk/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/uk/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/uk/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx index 7edde3d0cbcd..a741d6783d2a 100644 --- a/website/src/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ After the 20 minute transfer window, you will need to confirm the transfer with It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet? +### Is publishing and versioning the same on L2 as Ethereum Mainnet? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/uk/token-api/faq.mdx b/website/src/pages/uk/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/uk/token-api/faq.mdx +++ b/website/src/pages/uk/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/ur/ai-suite/graph-assistant/faq.mdx b/website/src/pages/ur/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/ur/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/ur/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/ur/token-api/faq.mdx b/website/src/pages/ur/token-api/faq.mdx index df35c790e961..3dd469955710 100644 --- a/website/src/pages/ur/token-api/faq.mdx +++ b/website/src/pages/ur/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/vi/ai-suite/graph-assistant/faq.mdx b/website/src/pages/vi/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/vi/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/vi/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/src/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx index 2fec5116ce58..865b1fd7c42e 100644 --- a/website/src/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/src/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -82,7 +82,7 @@ After the 20 minute transfer window, you will need to confirm the transfer with It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the Subgraph on L1 and whether they keep indexing it until the Subgraph is fully supported on L2. -### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet? +### Is publishing and versioning the same on L2 as Ethereum Mainnet? Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the Subgraph. diff --git a/website/src/pages/vi/token-api/faq.mdx b/website/src/pages/vi/token-api/faq.mdx index 59313e1da8b4..b4e0c0a383ba 100644 --- a/website/src/pages/vi/token-api/faq.mdx +++ b/website/src/pages/vi/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this? diff --git a/website/src/pages/zh/ai-suite/graph-assistant/faq.mdx b/website/src/pages/zh/ai-suite/graph-assistant/faq.mdx index 8addf9935524..0388ac49bb25 100644 --- a/website/src/pages/zh/ai-suite/graph-assistant/faq.mdx +++ b/website/src/pages/zh/ai-suite/graph-assistant/faq.mdx @@ -15,7 +15,7 @@ An agentic application combines AI-driven reasoning with external data sources o 3. Which networks and data does Graph Assistant support? -The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum-One, Optimism, and Polygon. +The Assistant has access to Subgraphs across multiple chains. If a Subgraph is published to The Graph Network and is being indexed, the Assistant can automatically route queries to it. The Assistant also has access to the Token API on Ethereum Mainnet, BSC, Unichain, Arbitrum One, Optimism, and Polygon. 4. Is there a usage limit or quota? diff --git a/website/src/pages/zh/token-api/faq.mdx b/website/src/pages/zh/token-api/faq.mdx index a20b3420b380..1c34aebb8a78 100644 --- a/website/src/pages/zh/token-api/faq.mdx +++ b/website/src/pages/zh/token-api/faq.mdx @@ -94,7 +94,7 @@ The API accepts 40-character hex addresses with or without the `0x` prefix. The ### Do I need special headers besides authentication? -While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/balances/evm/{address}` not `/balance`). +While recommended, `Accept: application/json` isn't strictly required as the API returns JSON by default. The critical header is `Authorization: Bearer `. Ensure you make a GET request to the correct URL without trailing slashes or path typos (e.g., use `/v1/evm/balances` not `/v1/evm/balance`). ### MCP integration with Claude/Cline/Cursor shows errors like "ENOENT" or "Server disconnected". How do I fix this?