Why do we manually set the HyperSync URL for some chains but not others?

[PaulRBerg]

@razgraf @gavriliumircea

There are some chains for which we set the HyperSync config manually, e.g. Chiliz:

indexers/apps/flow-envio/config.yaml

Lines 103 to 104 in a432c08

	hypersync_config:
	url: https://chiliz.hypersync.xyz

indexers/packages/constants/src/addresses/chiliz.ts

Line 7 in a432c08

export let hypersync = "https://chiliz.hypersync.xyz";

I carried over this logic in my PR, however, I now realize that I don't understand the goal.

As per the Envio docs on HyperSync:

Default Enablement
HyperSync is used by default as the data source for all HyperIndex networks.

Is it because in previous versions of the Envio CLI, the HyperSync config was not enabled by default? Or HyperSync did not support some chains, by default?

Sorry to tag you @DZakh but maybe you could help us quickly elucidate this mystery?

[DZakh]

Is it because in previous versions of the Envio CLI, the HyperSync config was not enabled by default? Or HyperSync did not support some chains, by default?

Yes, probably it was added manually, since envio version which new about the chain wasn't published yet. It's recommended to remove the manual hypersync config when we add support for the chains to the envio package.

[DZakh]

This is weird, I see that https://5845.hypersync.xyz/height works. I'll ask the team why we don't have it in the chain list.

[PaulRBerg]

Thanks. How do we check if the envio package supports a particular chain? What file should we look at?

[DZakh]

It's supported, we'll update the list in the near future.

[DZakh]

Probably only source code by version tag https://github.com/enviodev/hyperindex/blob/v2.22.3/codegenerator/cli/src/config_parsing/chain_helpers.rs

[PaulRBerg]

Related: enviodev/hyperindex#599