closed Docker image for version 2.6.x

[wwwmilan]

Overview

Hi team,
I hope you're doing well.
Could you please generate a closed Docker image for version 2.6.x?
The current version 2.3.5 is a bit outdated, and unfortunately I’m unable to upload an open version to my company’s binary repository.
Let me know if you need any additional information from my side.
Thank you in advance!

To‑do / Implementation notes

No response

Mockups / Screenshots / Links

No response

Deployment info

No response

Acceptance criteria

No response

[human-77]

We're having the same problem in my company.

[Mojmir-R]

Hey @wwwmilan @human-77, thank you for reaching out and for using Blockscout.
The delayed release of Docker is intentional and part of our broader effort to sustain the project and ensure its long-term availability. We’re encouraging more projects to explore our hosted solutions, such as our one-click deployment tool Autoscout or our Explorer-as-a-Service (EaaS) offering.
At the moment, there’s no ETA for the Docker 2.6.x release, but we do plan to publish it eventually. In the meantime, you have three options:

1. Build Docker yourself. The source code is still fully open-source, so anyone can build it directly.
2. Use Autoscout. It’s currently the most cost-efficient and fastest way to deploy the latest Blockscout release for your chain. If you’d like to try it, we’re happy to provide free credits.
3. Try our Explorer-as-a-Service offering. If you’re interested, I’d be happy to schedule a call and share more details about it.

You can also reach me on Telegram at Mojmir_R if you’d like to discuss anything Blockscout-related in more detail.

[human-77]

Hi @Mojmir-R !

Can you tell me more about the Explorer-as-a-Service offering? Is there a pricing page or any tutorial on how it would work or is a "by case" scenario? If it's the latter, can you give me a overview of what the process may look like?

Similarly, can you point me to the Autoscout documentation?

[Mojmir-R]

Hey @human-77,

As for Autoscout resources, I am linking below the relevant resources and can help answer any additional questions.

Landing page: https://autoscout.blockscout.com/
Docs: https://docs.blockscout.com/using-blockscout/autoscout#autoscout-explorer-launchpad

As for EaaS, it is on a "by case" base. You can find more general details here: https://eaas.blockscout.com/ and I would be happy to share more on the pricing in private if you are interested.

[human-77]

Thanks for the answer @Mojmir-R !

Just a few questions:

• Does Autoscout work with private networks or that is just for EaaS?
• Is there the possibility of we run our own instance of blockscout and just hire you to provide us with support?
• Do you have any service to address questions of privacy?

[Mojmir-R]

Hey @human-77,

Does Autoscout work with private networks or that is just for EaaS?

It does work for private networks too, you can launch it with any custom obfuscated domain to not disclose the instance publicly in any way.

Is there the possibility of we run our own instance of blockscout and just hire you to provide us with support?

This would depend on the exact scope and type of support and number of explorers etc. It is something we can discuss.

Do you have any service to address questions of privacy?

Depends on exact context of the privacy, if this is privacy features for explorer, or some 3rd party service or only about access to explorer etc. But we do have a privacy solution of our own and we can also work on custom features developed specifically for your needs - it is something we do often for other chains and ecosystems.

[human-77]

This would depend on the exact scope and type of support and number of explorers etc. It is something we can discuss.

Mostly, we just want access to new docker images so we can keep working as previously.

Depends on exact context of the privacy

Ideally, something that would be executed internally or in such a way that only allowed individuals can look at the actual chain as we want to keep our client's data private.

[Mojmir-R]

Mostly, we just want access to new docker images so we can keep working as previously.

Understood. That is very straightforward and definitely doable.

Ideally, something that would be executed internally or in such a way that only allowed individuals can look at the actual chain as we want to keep our client's data private.

Straightforward again, such solution is something we could work on for you.