If we add an `rpc` field under each Network object in the YAML config, does that mean we're no longer using HyperSync?

[PaulRBerg]

I was looking at these docs: Improving resilience with RPC fallback.

It's not clear to me what happens if we add an rpc field like this:

name: Greeter
description: Greeter indexer
networks:
  - id: 137 # Polygon
+   # Short and simple
+   rpc: https://eth-mainnet.your-rpc-provider.com?API_KEY={ENVIO_MAINNET_API_KEY}

Does this field completely override HyperSync, i.e., HyperSync will no longer be used. Or will it be used as a fallback?

I can see that when I add multiple rpc, there is a for: fallback thingy, but I'm not sure if the same setting applies when I am only defining rpc.

[DZakh]

It uses fallback mode by default if there is available HyperSync support.