INDEXER_AGENT_NETWORK_SUBGRAPH_ENDPOINT

[ThomasBlock]

Thank you for this project. Setting up a node is very easy.

just one undocumented change: in the .env file we need now to enter a custom
INDEXER_AGENT_NETWORK_SUBGRAPH_ENDPOINT

As described here
https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md

this needs an api key from
https://thegraph.com/studio/apikeys/

[payne0420]

Hi @ThomasBlock, yeah, I'm yet to update the mainnet repo to be on par with the Testnet repo, aiming for this weekend 🫡
Gonna close this issue after I'm done with all the changes.

[ThomasBlock]

great. one more warning to my solution:
maybe its because i used a dummy operator seed phrase.. but the agent fired 100.000 api calls in the first day. this would be quite expensive. so the quick fix for me is
docker-compose -f compose-indexer.yml stop indexer-agent

and only start it when neccessay.

[payne0420]

It's totally normal. You won't be able to use the free tier with the agent/service connected to the network subgraph and ebo. Your $200 cost per month seems a good ballpark, but could be higher.
One way around this would be to disable the indexer-agent every time you are done reallocating.

[ThomasBlock]

okay.. but automatic reallocations can be handy sometimes.. is there a way to reduce the requests, like check only every 6 hours?

[payne0420]

As far as I'm aware, there's no way to rate limit it.

[ThomasBlock]

Querys cant be completed, the following is also missing in the .env
INDEXER_SERVICE_NETWORK_SUBGRAPH_ENDPOINT="$INDEXER_AGENT_NETWORK_SUBGRAPH_ENDPOINT"

[payne0420]

Like I said, the mainnet repo is not updated yet. I'm working on it.
It will come with super cool updates.
The testnet repo is almost ready.

[ThomasBlock]

no worries, this is not a request, i just write down documentation before i forget it.
certainly looking foreward to cool updates :) i will be the first to test it