Upgrade Guide (v7.0 & v8.0)
🚗 Autoscout is now available, providing a simple one-click explorer deployment with Blockscout's optimized hosting infrastructure. Use it for early testing, modifications, and launching a full production-grade explorer. Get Started Now and have your explorer up-and-running in minutes.
If it has been a while since your last upgrade, we recommend performing incremental upgrades to ensure proper performance. For example if you are running backend v6.9.0, first upgrade to v6.10.0 prior to upgrading to the latest 7.0 version. This reduces downtime and ensures all breaking changes are handled. Please update to v7.0 before updating to v8.0. Follow the same process below replacing v7 with the latest front and backend repositories.
Getting Started
This guide walks through the process of updating Blockscout to backend v7.0.2 and frontend v1.38.0 (March, 2025) from v6.10.X. If you have questions about a different upgrade, contact us in Discord. Breaking changes follow the instructions.
1) Update backend ENV variables
Backend variable renaming only applies to the 6.10.X -> 7.0.X update. If you are performing a more extensive update, please check renaming & deprecations from the release notes of every minor release (6.8.0, 6.9.0 etc) within your update range.
Newly renamed variables include the MIGRATION
prefix. If a variable contained MIGRATION
in the name previously, it has been moved to the beginning of the variable. Expand below to see all variables you need to rename.
2) Install backend
-> blockscout/blockscout:7.0.2
3) Install frontend
-> ghcr.io/blockscout/frontend:v1.38.0
4) Install microservices
-> Stats microservice ghcr.io/blockscout/stats:v2.5.0.
-> Use the latest
tag to install any other microservices used with your instance
https://github.com/blockscout/blockscout-rs
Breaking Changes
/api/v1/health
, /api/v1/health/liveness
, /api/v1/health/readiness
have been removed in favor of /api/health/**
endpoints.
/api/v2/addresses/:address_hash
returns 200 instead 404 for valid hashes which are not in the DB.
/api/v2/tokens/:token_hash/instances
owner’s ens_domain_name property now preloads the ens domain name.
transaction hash and address hash are no longer mandatory in the txlistinternal
API v1 endpoint
/metrics
endpoint available on indexer pod (previously existed only on API pod)
Last updated
Was this helpful?