<aside> 🗣️

For questions and discussion related to the upgrade use

#horizon-upgrade channel in discord otherwise (https://discord.com/channels/438038660412342282/1422942908713144481)

For reporting bugs/issues

Create an issue in the horizon-bugtracker repository: https://github.com/graphprotocol/horizon-bugtracker/issues
- Any type of bug/issue (contracts, indexer stack, etc) </aside>

What?

We want to test the new indexer stack versions that introduce Horizon compatibility. There are two main scenarios where this should be tested:

Before the upgrade goes live, during Phase 3. This is to make sure that the new indexer stack works well with the current network components and protocol state.
After the upgrade is live. This ensures the indexer stack works well with new Horizon protocol.

When?

Refer to Graph Horizon: Testnet schedule for an up to date schedule. Important to note that the first scenario described above, “Phase 3 testing”, will only be available for testing during a brief period of time. Once that window is closed it won’t be possible to go back for additional testing.

Requirements

You’ll need ETH and GRT for the Arbitrum Sepolia testnet. You can get GRT from the faucet or ask maikoldeelias, tmigone in discord.

Important considerations for testnet

Protocol parameters
- Epochs are 554 blocks which is ~1.84 hours or ~110 minutes (vs 24 hours in mainnet)
- Legacy max allocation lifetime of 8 epochs (vs 28 epochs in mainnet)
- Horizon max allocation lifetime of 8 hours
- Minimum indexer stake: 100k GRT
Indexer testnet configuration reference: https://github.com/graphprotocol/indexer/blob/horizon/docs/networks/arbitrum-sepolia.md
Testnet explorer: https://testnet.thegraph.com/explorer
Horizon temp network subgraph: https://thegraph.com/explorer/subgraphs/eAENt2ctaMdbCY34apzXYkBy2nEYwyojjVxLahsHo9D
- Remember addresses need to be lowercased!
In order to make troubleshooting easier we ask to run components with the highest log verbosity
- tap-agent: RUST_LOG=info,indexer_tap_agent=trace
- indexer-service: RUST_LOG=info,indexer_service_rs=trace
- indexer-agent: INDEXER_AGENT_LOG_LEVEL=trace

Test cases for Phase 3 testing

We provide here a list of basic actions and scenarios that most indexers should go through but we encourage you to go beyond, if possible try to replicate as much as possible your production setup and operation. Detailed instructions to carry out each test case won’t be provided, it’s expected indexers know how to perform these and also we know not all indexers operate their stack the same. If unsure how to perform some of the tasks please reach out and we’ll gladly help.Setup for Phase 4 testing (to be done during Phase 3)

Untitled