Hello! Gitter chat support has been cancelled. Please redirect all requests to Discord: discord.gg/gnosischain (Channel #blockscout)
Qwerty5Uiop on vb-eth-tests
Clean up release (compare)
Qwerty5Uiop on release-building
Clean up release (compare)
vbaranov on vb-eth-tests-socker-root
Change order of tables deletion… Drop staking_polls & stakin_poo… Add clause for EthereumJSONRPC.… and 2 more (compare)
vbaranov on vb-fix-tx-response-for-txpoolcontent
vbaranov on master
Add clause for EthereumJSONRPC.… Merge pull request #5714 from b… (compare)
vbaranov on vb-fix-tx-response-for-txpoolcontent
Add clause for EthereumJSONRPC.… (compare)
[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