Add Envio to Data indexers

[Jordy-Baby]

Adds Envio to the data indexers listed on this page.

Envio is a high-performance indexing framework that turns smart contract events into a queryable GraphQL API, with managed hosting on Envio Cloud. It indexes Etherlink via HyperSync as the default data source.

• Website: https://envio.dev
• Docs: https://docs.envio.dev
• HyperIndex quickstart: https://docs.envio.dev/docs/HyperIndex/quickstart

The entry mirrors the format of the other indexer entries already on the page.

[vercel]

@Jordy-Baby is attempting to deploy a commit to the Trili Tech Team on Vercel.

A member of the Team first needs to authorize it.

[Jordy-Baby]

Hey @timothymcmackin @zamrokk, we'd love to have Envio listed here and I've kept it consistent with the existing providers. Let me know if you need anything else from my end.

[Jordy-Baby]

Gentle bump on this one. No rush at all. If any tweak to the wording, formatting or placement would help it land, just say the word and we will turn it around quickly.

Also worth flagging that the failing Vercel check here looks like a preview deployment issue on the account side rather than anything in this change. The diff itself still merges cleanly.

[NicNomadic]

I tried entering a few Etherlink addresses (picked from https://explorer.etherlink.com) on https://envio.dev/ but none was recognized, e.g.:

Your contract: 0x1c513262F13c8C317681E99d6b1BE963825e14b0
Valid contract address detected
We tried a few popular chains and couldn't find the verified ABI for this contract

So does this indexer support Etherlink?

[Jordy-Baby]

0x1c513262F13c8C317681E99d6b1BE963825e14b0

Hey @NicNomadic, thanks for flagging. I have shared it internally with our team to investigate and fix. Looks like a potential bug on our side, but Envio definitely supports Etherlink, including HyperSync support, please see both sections in our docs:

HyperIndex supported networks: https://docs.envio.dev/docs/HyperIndex/supported-networks
HyperSync supported networks: https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks

Please let me know if you have any more questions or require anything further on our end. I appreciate you taking the time to look into all of this and consider Envio. :D

[Jordy-Baby]

Hi @NicNomadic, following up on this.

Thanks again for flagging it, that turned out to be a real bug on our side and it is now fixed and live. Etherlink was missing from our contract lookup, and our Blockscout integration had also gone stale against the newer explorer API. Both are sorted, so verified Etherlink contracts now resolve on envio.dev.

One you can try is 0x6Fb65D60B4Ae844C5f9fE6929403CeE652397195, which returns its ABI straight away.

On the address you tested, 0x1c513262F13c8C317681E99d6b1BE963825e14b0, that one is not verified on explorer.etherlink.com, so there is no published ABI for us to fetch. Indexing it still works if you supply the ABI in the config yourself.

To confirm the original question, Etherlink is natively supported through HyperSync, so HyperIndex indexes it at full speed rather than over RPC.

https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks
https://docs.envio.dev/docs/HyperIndex/supported-networks

Thanks for considering Envio here. If any change to the wording or placement would help this land, say the word and we will turn it around quickly.