You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
66
65
67
-
> Note: `indexer-cli` does not currently have a command to index this subgraph like it does for `graph-network`. As a result, you have to index it manually.
66
+
-[Graph TAP Aribtrum Sepolia subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD)
67
+
-[Graph TAP Arbitrum One subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1)
68
+
69
+
> Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployement. As a result, you have to index it manually.
68
70
69
71
## Migration Guide
70
72
71
-
### Prerequisites
73
+
### Software versions
72
74
73
-
Make sure you have the following version: `<insert the version here>`
75
+
The required software version can be found [here](https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md#latest-releases).
74
76
75
77
### Steps
76
78
77
79
1.**Indexer Agent**
78
80
79
81
- Follow the [same process](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components).
80
-
-Use the new argument `–tap-subgraph-endpoint`.
82
+
-Give the new argument `--tap-subgraph-endpoint` to activate the new TAP codepaths and enable redeeming of TAP RAVs.
81
83
82
84
2.**Indexer Service**
83
85
84
-
- Fully replace your current configuration with the new application.
85
-
- You can reuse some of the values in your environment variables and command arguments inside the configuration.
86
-
> It’s critical to install the new `tap-agent` component to receive your payments.
86
+
- 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).
87
+
- Like the older version, you can scale Indexer Service horizontally easily. It is still stateless.
88
+
89
+
3.**TAP Agent**
87
90
88
-
3.**Configure**
91
+
- 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).
89
92
90
-
Configuration is shared between components, enabling you to use a single configuration for both `indexer-service` and `tap-agent`. Each component will use the required fields.
93
+
4.**Configure Indexer Service and TAP Agent**
94
+
95
+
Configuration is a TOML file shared between `indexer-service` and `tap-agent`, supplied with the argument `--config /path/to/config.toml`.
91
96
92
97
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)
93
98
94
-
For minimal configuration, use the following:
99
+
For minimal configuration, use the following template:
95
100
96
101
```bash
97
102
# You will have to change *all* the values below to match your setup.
- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
169
174
- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
66
65
67
-
> Note: `indexer-cli` does not currently have a command to index this subgraph like it does for `graph-network`. As a result, you have to index it manually.
66
+
-[Graph TAP Aribtrum Sepolia subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD)
67
+
-[Graph TAP Arbitrum One subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1)
68
+
69
+
> Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployement. As a result, you have to index it manually.
68
70
69
71
## Migration Guide
70
72
71
-
### Prerequisites
73
+
### Software versions
72
74
73
-
Make sure you have the following version: `<insert the version here>`
75
+
The required software version can be found [here](https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md#latest-releases).
74
76
75
77
### Steps
76
78
77
79
1.**Indexer Agent**
78
80
79
81
- Follow the [same process](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components).
80
-
-Use the new argument `–tap-subgraph-endpoint`.
82
+
-Give the new argument `--tap-subgraph-endpoint` to activate the new TAP codepaths and enable redeeming of TAP RAVs.
81
83
82
84
2.**Indexer Service**
83
85
84
-
- Fully replace your current configuration with the new application.
85
-
- You can reuse some of the values in your environment variables and command arguments inside the configuration.
86
-
> It’s critical to install the new `tap-agent` component to receive your payments.
86
+
- 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).
87
+
- Like the older version, you can scale Indexer Service horizontally easily. It is still stateless.
88
+
89
+
3.**TAP Agent**
87
90
88
-
3.**Configure**
91
+
- 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).
89
92
90
-
Configuration is shared between components, enabling you to use a single configuration for both `indexer-service` and `tap-agent`. Each component will use the required fields.
93
+
4.**Configure Indexer Service and TAP Agent**
94
+
95
+
Configuration is a TOML file shared between `indexer-service` and `tap-agent`, supplied with the argument `--config /path/to/config.toml`.
91
96
92
97
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)
93
98
94
-
For minimal configuration, use the following:
99
+
For minimal configuration, use the following template:
95
100
96
101
```bash
97
102
# You will have to change *all* the values below to match your setup.
- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
169
174
- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
0 commit comments