Usage of Autoscout Blockscout for Energy Web Chain

[KaamilW]

Hey Team,

We just stumbled upon Autoscout and are interested to learn whether it would be possible to use it for our chain.

Currently we are using self-hosted version of blockscout, (https://explorer.energyweb.org/) and recently we experience some performance issues (might be related to old version that we use).

We are wondering however whether we can use autoscout instead and what would be the size recommendation?
For Energy Web Chain we have Nethermind and OpenEthereum client support - is any of that clients suitable to set up Autoscout based blockscout instance?

Regards,
Kamil

[KaamilW]

Hey @vbaranov maybe you can take a look on the above?

[sl1depengwyn]

@GimluCom please take a look

[GimluCom]

Hi @KaamilW

We are wondering however whether we can use autoscout instead and what would be the size recommendation?

The small or medium instance size will probably work, but using the large size would give the highest sync speed. You could then adjust the instance size after it has fully synced.

For Energy Web Chain we have Nethermind and OpenEthereum client support

Yes. Blockscout currently treats Nethermind/OpenEthereum/Parity as one client type, so either one of them can be used.

[KaamilW]

Hey @GimluCom

Thanks! And do we need any special RPC configs for that to work? Normally for our current blockscout we were using FatDB OE.

Anything that I should know additionally or I should be fine to go ahead and try it out?

[GimluCom]

The RPC should be configured as an archive node with tracing enabled in order to take full advantage of Blockscout's features. OpenEthereum/Parity was deprecated a few years ago, thus Nethermind may be recommended as a replacement.

Sure, feel free to try it out.

[KaamilW]

Additional question @GimluCom -> based on which version of blockscout autoscout is based?
Just wanted to check the changelog as we are currently on a pretty outdated 4.1.5 beta version for our self-hosted explorer.

[GimluCom]

Currently it uses the version v9.2.2 which is also the latest release.

[KaamilW]

Ok, great. @GimluCom

Two more questions -> do you know how we can assess how fast the sync should happen? Just to be sure that if we are stuck we are aware that we need to raise it.

Also, in case of some UI changes needs, can it be done after initial deployment?

[GimluCom]

The front page of the explorer will display the number of indexed blocks as well as displaying a indexing status in percent, which can be used to monitor indexing progress.

Yes, the UI design can be edited after deploying.

[KaamilW]

One last question -> are you able to provide some promo code for us? @GimluCom
My email is kamil.witkowski@energyweb.org

[GimluCom]

Sure, sent you a code for Autoscout.

[KaamilW]

Btw @GimluCom -> https://ewc.cloud.blockscout.com/ any way to check whether indexing works as expected of old blocks?

[royki]

Hi @GimluCom ,

The Explorer is fully indexed, however it appears to be consuming a significant amount of credits, including the promo.

I have a few concerns and questions:

1. The Explorer does not display EWT Price, Market Cap ? Is this expected, or does it require additional configuration or data sources?

2. Is there a way to view or monitor API usage to better understand the current credit consumption and help estimate the appropriate plan?

Regarding Instance Plan changes:

1. The Edit Instance option allows selecting a different Instance Plan. Changing the plan seems to trigger a redeployment. What is the expected behavior after redeployment? Will any reindexing occur? Will this have any impact on indexing status or data persistence?
2. I've Installed Chart & stats from Plugins, the system prompts Redeploy to apply. Is it safe to proceed with the redeployment? Will this have any impact on indexing status or data persistence?

Contract verification
The following contract seems already verified : https://ewc.explorer.energyweb.org/address/0x0BDb4Ff8396Fbd0b8Baa9cF2ea188cC620D5d2B1?tab=contract
as when attempting to verify and publish it again, the explorer returns: Smart Contract/Address … Contract has already been verified.

However the Read/Write Proxy Contract section is not available. It only displays Read/Write Contract, even though this is a proxy contract.

On our self-hosted EWC Explorer: https://explorer.energyweb.org/address/0x0BDb4Ff8396Fbd0b8Baa9cF2ea188cC620D5d2B1/

Appreciate it if you could take a look and clarify these points.

Regards,

[GimluCom]

Hi @royki

1. We have enabled price fetching on the instance.
2. Clicking on the instance in the Autoscout UI will show details of the current plan and credit consumption.

Restarting or redeploying is fine, it will not affect data persistence. Changing instance plan is also not a problem.
Only stopping or deleting the instance will remove its data.

The Read/Write Proxy option will appear once the implementation contract is verified, which is:
https://ewc.cloud.blockscout.com/address/0x1fC6ba2F5E585C14f32af253ff910EE14726593f?tab=contract

[royki]

Hi @GimluCom , what is the way to change the instance plan ? Is it after changing Deploy Now or Save Draft and then Redeploy ?

[GimluCom]

Both of them are equivalent, so you may use either one of those methods.

[royki]

Ok, I hope nothing is going to break. 🤞

[royki]

Hi @GimluCom,
We attempted to update the domain in Autoscout to point to explorer.energyweb.org, but it does not appear to be working. Do you know what needs to be changed? I updated the configuration in Autoscout as well as the Cloudflare CNAME record.

[royki]

never mind; it's online now.

[royki]

Hi @GimluCom,
We're planning to use Autoscout explore for our Volta testnet. Could we have a quick discussion regarding storage, syncing and pricing?
Thanks

[GimluCom]

Hi @royki,
If you wouldn't mind, please reach out to Mojmir_R on Telegram.