https://github.com/blockscout/frontend/blob/main/docs/ENVS.md#app-features

options:

frontend                        | To adjust their configuration, please refer to the documentation - https://github.com/blockscout/frontend/blob/main/docs/ENVS.md#app-features
frontend                        |     
frontend                        |     [ ] My account
frontend                        |     [ ] Address verification in "My account"
frontend                        |     [v] Banner ads
frontend                        |     [v] Text ads
frontend                        |     [ ] Beacon chain
frontend                        |     [ ] Bridged tokens
frontend                        |     [ ] Blockchain interaction (writing to contract, etc.)
frontend                        |     [ ] Export data to CSV file
frontend                        |     [ ] Google analytics
frontend                        |     [v] GraphQL API documentation
frontend                        |     [ ] Marketplace
frontend                        |     [ ] Mixpanel analytics
frontend                        |     [v] REST API documentation
frontend                        |     [ ] Rollup (L2) chain
frontend                        |     [v] Safe address tags
frontend                        |     [ ] Sentry error monitoring
frontend                        |     [v] Solidity to UML diagrams
frontend                        |     [v] Blockchain statistics
frontend                        |     [ ] SUAVE chain
frontend                        |     [v] Web3 wallet integration (add token or network to the wallet)
frontend                        |     [ ] Verified tokens info
frontend                        |     [ ] ZkEVM rollup (L2) chain
frontend                        | 

Figure out if and how the current implementation works.
See: apps/explorer/config/config.exs

config :explorer, Explorer.Staking.PoolsReader,
validators_contract_address: System.get_env("POS_VALIDATORS_CONTRACT"),
staking_contract_address: System.get_env("POS_STAKING_CONTRACT")

if System.get_env("POS_STAKING_CONTRACT") do
config :explorer, Explorer.Staking.EpochCounter,
enabled: true,
staking_contract_address: System.get_env("POS_STAKING_CONTRACT")
else
config :explorer, Explorer.Staking.EpochCounter, enabled: false
end

Bad impact on performance / disk usage / analizability

2021-12-06T15:48:38.606 application=explorer [warn] Failed to get exchange rates with reason 'Source URL is nil'.
2021-12-06T15:48:38.606 application=explorer [warn] Failed to get exchange rates with reason 'Source URL is nil'.
2021-12-06T15:48:38.606 application=explorer [warn] Failed to get exchange rates with reason 'Source URL is nil'.
2021-12-06T15:48:38.606 application=explorer [warn] Failed to get exchange rates with reason 'Source URL is nil'.

Should act as easy solution to use to debug development and staging chains.

• build and upload a image to docker-hub
• provide a well documented sample config (docker-compose.yml) in a seperate repository.
• consider to make to update workflow (uploading new blockscout image) easy or automated.

currently blockscout shows the average block time as performance indicator on the front page.
In terms of HBBFT, this value is not a good performance indicator.

If you look up an transaction, you will find a "confirmation speed" information, like
example
Confirmed within <= 5.73 seconds

the "average block confirmation time" for transactions is arguable a better indicator than the average blocktime for the status and health of the blockchain.
It delivers much more information for the actual user journey.
Like how long does someone have to wait on average, until the transaction gets confirmed.

Once we have a testnet, we need to setup a Testnet Instance.

• use the term Validator instead of Miner to be consistent with other tools and documents.

currently blockscout ignores the contracts within the genesis block.
It does have an environment variable to handle that: CHAIN_SPEC_PATH
see: https://docs.blockscout.com/for-developers/information-and-settings/env-variables

the first try did not show good luck with it.
we need to investigate that further.

First tests have shown crashes because of block rewards.
blockscout#1572

Block reward feature got deactivated in the test instance.
Issue should get investigated again once HBBFT is running again.

Contract Sourcecode upload have always been one of the top pain points when it comes to managing a blockscout instance.

Sourcify targets this problem https://sourcify.dev/ and Blockscout has integrated support for that in 3.7.0:
seen env-variables:

ENABLE_SOURCIFY_INTEGRATION
SOURCIFY_SERVER_URL
SOURCIFY_REPO_URL

this could solve: DMDcoin/diamond-contracts-core#32 in a lot of cases, or make it easier to implement.

Prepare a Theme for the DMD Blockchain.

contract validation seems still not work in general.

Since the last update of blockscout the value transaction speed is missing:

and the explorer shows 'Confirmed within <= 79.869 seconds'

Might be connected with this pull request ?
https://github.com/blockscout/blockscout/pull/3124/files