graphprotocol · 0xa3k5 · Jul 14, 2025 · May 6, 2025 · May 6, 2025 · May 6, 2025
@@ -2,6 +2,8 @@
 title: Arbitrum FAQ
 ---
 
+> **Important**: L2 Transfer Tools have been deprecated, and The Graph now runs on Arbitrum, a Layer 2 blockchain.
+
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
 ## Why did The Graph implement an L2 Solution?

@@ -2,6 +2,8 @@
 title: L2 Transfer Tools FAQ
 ---
 
+> **Important**: L2 Transfer Tools have been deprecated, and The Graph now runs on Arbitrum, a Layer 2 blockchain.
+
 ## General
 
 ### What are L2 Transfer Tools?
@@ -116,7 +118,9 @@ To transfer your delegation, you will need to complete the following steps:
 
 ### 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 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 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.
 
 ### What happens if the Indexer I currently delegate to isn't on Arbitrum One?
 

@@ -2,6 +2,8 @@
 title: L2 Transfer Tools Guide
 ---
 
+> **Important**: L2 Transfer Tools have been deprecated, and The Graph now runs on Arbitrum, a Layer 2 blockchain.
+
 The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring.
 
 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.

@@ -733,7 +733,7 @@ Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexi
 
 1. Open the [Remix app](https://remix.ethereum.org/) in a browser
 
-2. In the `File Explorer` create a file named **Staking.abi** with the staking ABI.
+2. In the `File Explorer` create a file named **Staking.abi** with the [staking ABI](https://raw.githubusercontent.com/graphprotocol/contracts/mainnet-deploy-build/build/abis/Staking.json).
 
 3. With `Staking.abi` selected and open in the editor, switch to the `Deploy and run transactions` section in the Remix interface.
 

@@ -500,7 +500,25 @@ export function handleTransfer(event: TransferEvent) {
 
 As long as the `ERC20Contract` on Ethereum has a public read-only function called `symbol`, it can be called with `.symbol()`. For public state variables a method with the same name is created automatically.
 
-Any other contract that is part of the Subgraph can be imported from the generated code and can be bound to a valid address.
+Any other contract that is part of the subgraph can be imported from the generated code and can be bound to a valid address. Example of that is presented within the steps below:
+
+- extend `subgraph.yaml` file with desired ABI file:
+
+```yaml
+mapping:
+  kind: ethereum/events
+  apiVersion: 0.0.6
+  language: wasm/assemblyscript
+  entities:
+    - Gravatar
+  abis:
+    - name: Gravity
+      file: ./abis/Gravity.json
+    - name: OtherContract
+      file: ./abis/OtherContract.json
+```
+
+- Import and bind to the contract using its address
 
 #### Handling Reverted Calls
 
@@ -660,6 +678,8 @@ export function handleSomeEvent(event: SomeEvent): void {
 }
 ```
 
+<VideoEmbed title="How to Use Logging to Debug a Subgraph Mappins Error" youtube="7H3bm87u5Jw" />
+
 ### IPFS API
 
 ```typescript
@@ -772,6 +792,7 @@ When the type of a value is certain, it can be converted to a [built-in type](#b
 | BigInt               | BigDecimal           | s.toBigDecimal()             |
 | BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
 | BigInt               | String (unicode)     | s.toString()                 |
+| BigInt               | Bytes                | s.fromBigInt()               |
 | BigInt               | i32                  | s.toI32()                    |
 | Boolean              | Boolean              | none                         |
 | Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
@@ -800,8 +821,8 @@ When the type of a value is certain, it can be converted to a [built-in type](#b
 | Bytes                | Address              | Address.fromBytes(s)         |
 | String               | BigInt               | BigInt.fromString(s)         |
 | String               | BigDecimal           | BigDecimal.fromString(s)     |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
+| String (hexadecimal) | Bytes                | Bytes.fromHexString(s)       |
+| String (UTF-8)       | Bytes                | Bytes.fromUTF8(s)            |
 
 ### Data Source Metadata
 

@@ -218,7 +218,7 @@ filter:
 
 _The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
 
-> **Note:** The `call` filter currently depends on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, do not support this API. If a Subgraph indexing one of these networks contains one or more block handlers with a `call` filter, it will not start syncing.
+> **Note:** The `call` filter currently depends on the Parity tracing API. Certain networks, such as BNB chain, Arbitrum, Polygon, and Optimism do not support this API. If a Subgraph indexing one of these networks contains one or more block handlers with a `call` filter, it will not start syncing.
 
 The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
 
@@ -452,6 +452,8 @@ let tradingPair = context.getString('tradingPair')
 
 There are setters and getters like `setString` and `getString` for all value types.
 
+> **Note:** Referecing an entity is done via ID in graphQL. That id can be passed into the instantiated data source by setting it in the context and then accessed within the mapping of the template. Example can be found in the [documenation of graph-ts](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts#api).
+
 ## Start Blocks
 
 The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a Subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.