Hello! Gitter chat support has been cancelled. Please redirect all requests to Discord: discord.gg/gnosischain (Channel #blockscout)
dependabot[bot] on npm_and_yarn
Bump css-minimizer-webpack-plug… (compare)
dependabot[bot] on npm_and_yarn
Bump eslint from 8.17.0 to 8.21… (compare)
dependabot[bot] on npm_and_yarn
Bump bignumber.js from 9.0.2 to… (compare)
dependabot[bot] on npm_and_yarn
Bump sass from 1.49.8 to 1.54.3… (compare)
[Igor Barinov, POA Network] There is no bounty program for BlockScout yet.
Meanwhile please contact security@poanetwork.com or @igorpoa on telegram and it can be discussed case by case
[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.
@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