Skip to content

Blockscout Explorer Deployment for EVM Chains and Rollups

Protofire handles Blockscout explorer deployment for EVM chains and rollups. We tune and upgrade the explorer and, under a written scope, operate it. Each proposal names the release and its license terms before work starts. Blockscout's own registry lists Protofire as host of the Vana and Autonomys EVM explorers.

Arsenii Petrovich

Reviewed by Arsenii Petrovich, Offer Owner at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Why Protofire
  3. What you get
  4. License
  5. How the build runs
  6. Ownership
  7. How work starts
  8. Not the right fit
  9. Related infrastructure services
  10. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

A Blockscout explorer depends on your node, database and chain type

A Blockscout explorer reads from your node, and your node was not built with Blockscout in mind. Blockscout explorer deployment looks like a small task because the software can be self-hosted. Once your mainnet date is set, the first thing wallets, exchanges and users look for is an explorer that shows the latest block.

Blockscout fetches internal transactions through tracing methods such as debug_traceBlockByNumber. Blockscout's sizing table put an Ethereum mainnet database at about 21,000 GiB in December 2024. The CHAIN_TYPE setting picks data models and fetchers, and values such as optimism and arbitrum need a recompile.

A wrong call on the node, database or chain type shows up later as empty internal transactions, a head that lags or a rebuild.

Who holds each layer of a Blockscout deployment

The other layers read from the chain's node. In the deployments Protofire scopes, the chain keeps its domain and its own configuration.

Your chain

Chain node

The explorer reads from an archive node with tracing enabled, and on rollups also from a settlement-layer RPC.

Domain, configuration and data

The chain keeps the domain, the configuration files, the PostgreSQL data or scheduled backups, and the indexer's node credentials.
Protofire deploys

Indexer and PostgreSQL

The indexer walks from the current block back to genesis, then fetches internal transactions.

Rust services

The verifier, eth-bytecode-db, sig-provider, stats and visualizer each run as a separate service.

API and frontend

The API is written in Elixir, and the React frontend shows your name, logo and theme.
Protofire runs

Monitoring and upgrades

Protofire watches head lag, backlog, disk and API errors, and checks each upgrade against the release notes.
Blockscout Limited

Blockscout software and its terms

Blockscout Limited publishes the code and sets the license that comes with each release line.

Our Blockscout record: Vana, Autonomys, Somnia and Quai

On 9 November 2026, Blockscout's own chain registry, Chainscout, listed Protofire as host of the Vana and Autonomys EVM explorers.

Vana and Autonomys in Blockscout's registry

Chainscout's entries for Vana cover Vana's mainnet and its Moksha testnet. On 13 January 2025, Blockscout's maintainers merged pull request 24, whose title begins "Added Protofire as provider". On 9 June 2025, they merged pull request 113, which added Autonomys's Taurus testnet and updated Vana's information.

Somnia's explorer, deployed and tuned during its testnet

Protofire deployed and tuned Somnia's explorer on Blockscout during Somnia's testnet. We changed PostgreSQL memory settings, vacuum thresholds and indexes. We also changed batch sizes and concurrency. After the tuning, the explorer indexed up to 103 million transactions in a day at peak, in near real time.

Blockscout adapted for Quai's sharded design

Between April and October 2024, Protofire changed Blockscout for Quai. We added Quai-specific block fields, UTXO transactions and shard regions. The work took about 130 commits across the backend fork and the frontend fork. Both forks are archived.

What Blockscout explorer deployment gives your chain

The explorer's other layers read from the node, so work on a new chain starts with the node.A chain that already has a working explorer can start at tuning or upgrades. Each package is quoted against a named release line.

A node tested against Blockscout's requirements

You learn before the build whether your node can feed an explorer. Protofire times the node's RPC calls against Blockscout's targets and checks tracing on your client. Our report lists each method that passed or failed.

An index that reaches the chain head

Users see new blocks as they arrive and the history behind them, instead of a warning that counts may be inaccurate. Protofire tunes the indexer and PostgreSQL for your chain's growth. Named queries report lag, gaps and backlog.

Contracts your developers can verify themselves

A team that deploys on your chain publishes its source and gets a verified contract page without asking you. Protofire brings up the verifier services. We then verify a test contract on each route your developers use.

Custom fetchers, API fields and pages for your chain

Your users see behavior that Blockscout does not cover on your chain in the explorer they already open. Protofire writes custom fetchers, API fields or interface pages in a repository your team controls. We track that code against upstream releases.

Upgrades tested against the tools that read your API

Wallets and dashboards break first when Blockscout changes an API or an export. Protofire reviews the release notes and runs the release in staging. We diff the API and prepare a rollback from a PostgreSQL snapshot taken before migrations run.

Monitoring and operation of the explorer

When a chain asks Protofire to operate its explorer, alerts go to a named engineer. A monthly note reports lag, backlog and storage growth.

Blockscout's April 2026 license change and paid deployment work

On 22 April 2026, Blockscout Limited changed Blockscout's license terms, and the change applies to paid deployment work.Backend v11.0.0 and later, frontend v2.7.3 and later, and the Rust service tags that include the license ship under the Blockscout Software Licence v1.0. Blockscout calls this license source-available. Blockscout's license FAQ lists paid implementation, customization and maintenance among the uses that need a Commercial Licence (license text). Each Protofire proposal names the release of each component and the party that holds the Commercial Licence. The Commercial Licence is agreed with Blockscout Limited before paid work starts. Blockscout can change the license, and continued use counts as acceptance (section 3(c)). A chain on Blockscout Software Licence releases writes the change and termination clauses into its exit plan. If Blockscout declines a Commercial Licence, paid work has two routes left: the GPL line or Blockscout's own hosting. The GPL line has a cost of its own. Blockscout offers "no guarantees that previous versions of the software will continue to run properly". So a chain on the GPL line is responsible for its own hard-fork fixes. On the GPL line, each Protofire proposal names each fix we write. The fixes contain no code copied from v11 or later. Your counsel reads the license against your setup.

Releases

GPL v3 line: Backend before v11.0.0, and frontend through v2.7.2

Blockscout Software Licence v1.0: Backend v11.0.0 and later, and frontend v2.7.3 and later. Blockscout's FAQ names v2.8.0, but the v2.7.3 tag already includes the license file.

A chain running its own explorer

GPL v3 line: Earlier releases are "governed by their original licence terms"

Blockscout Software Licence v1.0: "you do not need a Commercial Licence" when it is "for your own chain and not charging others to access it"

Paid work for a customer

GPL v3 line: The GPL "permitted unrestricted commercial use"

Blockscout Software Licence v1.0: "If you are being paid to configure, deploy, or maintain Blockscout for a customer, contact us to discuss a Commercial Licence."

Custom code

GPL v3 line: GPL v3 terms apply

Blockscout Software Licence v1.0: Custom code is allowed "solely for your internal use". Giving it to a third party needs a Commercial Licence first. Blockscout receives a "perpetual, irrevocable" license to your code. The proposal states how section 5 on Derivative Works applies.

Termination

GPL v3 line: GPL v3 terms apply

Blockscout Software Licence v1.0: Blockscout "may terminate this Licence at any time in its sole discretion" (section 10). Termination requires deleting the software and derivative works, including "any copies held by your contractors or service providers".

How an explorer gets from an empty database to the chain head

A Blockscout explorer shows new blocks first and completes its index in two passes.

  1. Step 1

    Test the node first

    Blockscout expects the node to answer eth_getBlockByNumber and eth_getTransactionReceipt in under 0.5 seconds. Geth traces through debug_traceBlockByNumber, while Erigon and Nethermind use trace_replayBlockTransactions. If your client is modified, Protofire first compares its output with Geth's output.
  2. Step 2

    Set the chain type before the build

    The CHAIN_TYPE values optimism, arbitrum and filecoin need recompilation. The values arc, neon, stability and shibarium can change at runtime. A standard EVM chain keeps the default value.
  3. Step 3

    Backfill from the head to genesis

    The indexer works back from the chain head, so the genesis block arrives last. Protofire counts gaps with the generate_series query from Blockscout's docs, so a missing range is a number in the report. A block from a fork has consensus set to false, so the gap query and each export we build filter on that field.
  4. Step 4

    Drain the internal transaction backlog

    Blockscout says the count of pending_block_operations "should move towards zero". A flat count points at the tracing calls or at node capacity. Skipping this pass leaves the explorer without internal transactions.
  5. Step 5

    Bring up verification and the Rust services

    Verification, signature lookups, statistics and contract diagrams run as separate Rust services. The backend must reach the verifier before developers can verify contracts against it.
  6. Step 6

    Upgrade against the release notes

    Blockscout v11.0.0 changed CSV exports and WebSocket new_block payloads, and it removed Polygon zkEVM support. Version 12.0.0, released on 6 October 2026, lists its own API breaking changes. A separate license check comes before a component moves onto the Blockscout Software Licence.

What the chain keeps after launch

The chain keeps its domain, its configuration files and its PostgreSQL data or a scheduled backup of it.The explorer runs in the chain's own cloud account or on servers the chain rents. Where the chain asks Protofire to operate the explorer, the scope names the role we hold. The chain can remove that role. If a proposal places the explorer on servers that Protofire rents, the proposal lists those servers. It also sets a schedule for delivering backups and configuration to the chain.

The explorer's configuration holds the database URL, the SECRET_KEY_BASE and a WalletConnect project ID. The configuration holds no chain keys, and users sign in their own wallets. When an operator leaves, you rotate the database password and the SECRET_KEY_BASE. The Blockscout software belongs to Blockscout Limited.

How work with Protofire starts

You send your chain ID, your node client and your tracing setup.You also send your chain type and your current explorer version, if you have one. From those details, Protofire's proposal sets each component's release and license route. The full process is on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

When a Blockscout deployment with Protofire does not fit

Blockscout's own hosting, your own engineers, Etherscan or a custom indexer can serve some chains better.

Blockscout Limited builds and releases Blockscout. Protofire deploys and operates explorers built on Blockscout and gives no legal advice on Blockscout's license.

Explorer work on Blockscout

103M
transactions indexed in one day during testnet

Protofire deployed and tuned Somnia's explorer on Blockscout during its testnet. PostgreSQL held 2B+ rows and 19+ TB on a 96-core machine with 1 TB of RAM.

FAQ

What is a Blockscout explorer?
A Blockscout explorer is the public web interface and API for an EVM chain. It shows the chain's blocks, transactions, addresses, tokens and verified contracts. Blockscout Limited publishes the software, and a chain can self-host it or buy hosting. Protofire deploys and tunes Blockscout explorers for chains that self-host. Such an explorer reads from an archive node and stores its index in PostgreSQL.
Who can deploy and run a Blockscout explorer for our chain?
Protofire can deploy and run a Blockscout explorer for an EVM chain or rollup that keeps the explorer in its own cloud account. We test the node, set the chain type and tune indexing. We also bring up contract verification and handle upgrades. If you ask, the scope also covers operating the explorer.
Do we need a Commercial Licence for Blockscout?
Not if you run Blockscout on your own chain and do not charge others for access, according to Blockscout's FAQ. A party paid to configure, deploy or maintain Blockscout for a customer on backend v11.0.0 or later needs a Commercial Licence. The license also bars you from authorizing a third party to configure, deploy or maintain Blockscout for pay without a Commercial Licence (section 4(a)). Earlier backend releases are licensed under GPL v3. Your counsel decides how the license applies to your setup.
Can we put our own brand on the explorer?
Yes, the Blockscout frontend takes your name, logo and theme as settings. Releases under the Blockscout Software Licence also need a "Powered by Blockscout" credit that links to blockscout.com. The credit must be shown "at all times while you use the Software". The license also bars removing Blockscout's branding notices.
Should our chain use Blockscout or Etherscan?
Blockscout suits a chain that wants to choose who hosts its explorer, within Blockscout's terms. The host can be the chain itself, Blockscout or another operator. Etherscan suits a network that wants Etherscan's name on the explorer and accepts Etherscan's fully hosted model.
Why does an explorer fall behind the chain head?
The node is the usual cause when an explorer falls behind, and PostgreSQL is the next most common one. The first check compares the newest indexed block with eth_blockNumber. The second check times block and receipt calls against Blockscout's 0.5-second targets. If the node keeps up, the next place to look is PostgreSQL's memory and vacuum settings.
What happens if we move the explorer to another operator?
Your domain, configuration files and PostgreSQL backups move with you. The new operator restores the database or reindexes from your archive node. If your explorer runs releases under the Blockscout Software Licence, you raise Blockscout's FAQ line on paid maintenance with the next operator before the move.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Margaret ApanasevichReads every request · LinkedIn

A demo or repository link also works.