Hello! Gitter chat support has been cancelled. Please redirect all requests to Discord: discord.gg/gnosischain (Channel #blockscout)
vbaranov on production-optimism-goerli-stg
Customize optimism-goerli deplo… (compare)
vbaranov on production-optimism-stg
Resolve merging conflicts (compare)
vbaranov on production-optimism-goerli-stg
Customize optimism-goerli deplo… (compare)
vbaranov on master
Update debug_traceTransaction/t… Merge pull request #5717 from s… (compare)
Qwerty5Uiop on release-building
Fix migrator pool_size (compare)
vbaranov on production-optimism-stg
Resolve merging conflicts (compare)
vbaranov on master
Update CHANGELOG (compare)
@sameroom-bot
[Victor Baranov, POA Network] @mul53
Hey everyone, i want to upgrade a repo from blockscout v1 to v3, wanted to get some pointers on the right way to perform the upgrade
In order to upgrade from V1 -> V3
- You need to meet current general software requirements https://docs.blockscout.com/for-developers/information-and-settings/requirements
- Follow manual deployment guide https://docs.blockscout.com/for-developers/manual-deployment using the latest V3 stable release https://github.com/poanetwork/blockscout/releases
- Add all currently required environment variables https://docs.blockscout.com/for-developers/information-and-settings/deprecated-env-variables if some are missing in your deployment
- Check if you are still using some deprecated environment variables and replace them https://docs.blockscout.com/for-developers/information-and-settings/deprecated-env-variables
Take into account that V3 contains a lot of DB migrations which includes optimization of indexes, new columns in existing tables and if your DB is quite big, it may take a long time to process all migrations. Do it with patience.
Thank You!
[Victor Baranov, POA Network] Ah, I recalled the reason differences. From version v2.1.0 we take into account all accounts which participated in transactions no matter which balance of the account. In the versions less than v2.1.0 we took into account only accounts with a current non-zero balance. This change initiated in this PR poanetwork/blockscout#2718. You can take for the rationale there and how to rollback the change if you don’t want to deal with it.
hey Viktor, thanks you got the answering
Does contracts also count as wallets? We have much of wallet proxy contracts that don't hold native currency. So that can explain perfectly 20k new wallets
[Victor Baranov, POA Network] If websockets endpoint provided, then I suppose it is the highest speed of appearance of the new blocks in the latest release. I assume, indexing could be slower in v3 than in v1 but it protects your DB from possible discrepancies. New indexing was introduced in v3.0.0 . Here are all PRs to enable it
poanetwork/blockscout#2835, poanetwork/blockscout#2871, poanetwork/blockscout#2872, poanetwork/blockscout#2886, poanetwork/blockscout#2925, poanetwork/blockscout#2936, poanetwork/blockscout#2949, poanetwork/blockscout#2940, poanetwork/blockscout#2958 - Add “block_hash” to logs, token_transfers and internal transactions and “pending blocks operations” approachv
[Victor Baranov, POA Network] If websockets endpoint provided, then I suppose it is the highest speed of appearance of the new blocks in the latest release. I assume, indexing could be slower in v3 than in v1 but it protects your DB from possible discrepancies. New indexing was introduced in v3.0.0 . Here are all PRs to enable it
poanetwork/blockscout#2835, poanetwork/blockscout#2871, poanetwork/blockscout#2872, poanetwork/blockscout#2886, poanetwork/blockscout#2925, poanetwork/blockscout#2936, poanetwork/blockscout#2949, poanetwork/blockscout#2940, poanetwork/blockscout#2958 - Add “block_hash” to logs, token_transfers and internal transactions and “pending blocks operations” approachv
I see, thanks. Yeah looking at xdai explorer I see the same behaviour: https://blockscout.com/poa/xdai/
We also rely on the explorer API in our apps, so 5-10 secs delay sounds non neglectable