Set up your indexer
Configure your indexer to serve the GraphOps gateway's queries and be paid for them.
1. Add the GraphOps gateway's TAP senders
The gateway pays for each query with a TAP (Graph Tally) receipt signed by one of its senders. Without a sender in your config, tap-agent can't aggregate that sender's receipts, and you can't redeem the queries it paid for.
In the config file indexer-service-rs and tap-agent share, add the gateway's senders:
0xDD6a6f76eb36B873C1C184e8b9b9e762FE216490, 0xd46b87020AB3E8B4E5A64EC7c0e3496142c5CA1B, 0x382411dE4eaed896E289E6b57B3F48A766980e1F. They all use the aggregator https://tap-aggregator-arbitrum-one.graphops.xyz.
indexer-service-rs and tap-agent config (TOML)
[tap.sender_aggregator_endpoints]
0xDD6a6f76eb36B873C1C184e8b9b9e762FE216490 = "https://tap-aggregator-arbitrum-one.graphops.xyz"
0xd46b87020AB3E8B4E5A64EC7c0e3496142c5CA1B = "https://tap-aggregator-arbitrum-one.graphops.xyz"
0x382411dE4eaed896E289E6b57B3F48A766980e1F = "https://tap-aggregator-arbitrum-one.graphops.xyz"Keep any other senders you already accept in the same table. Restart indexer-service-rs and tap-agent to apply the change.
2. Run versions the gateway accepts
The gateway regularly checks indexer-service /version, Graph Node's version and /status, and only selects an indexer whose versions meet the version requirements on Constraints. Keep both endpoints reachable from the internet.
3. Allocate to the deployments you want to serve
The gateway only considers an indexer for a deployment it has an active allocation on, among the deployment's largest. Stay close to chain head on those deployments: How selection works lists every rule.
4. Check your indexer
Once the gateway sends you queries, search for your indexer address on Indexers to see its success, latency, time behind chain head and failures beside other indexers. If it has no observations, its page lists what to check.