status-im
/
status-react
mirror of https://github.com/status-im/status-react.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-react/status-go-version.json

9 lines
315 B
JSON
Raw Normal View History

nix: Use status-go commit sha1 in Nix expression to allow for moving branches Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-07-19 18:42:16 +00:00
{
"_comment": "DO NOT EDIT THIS FILE BY HAND. USE 'scripts/update-status-go.sh <tag>' instead",
"owner": "status-im",
build status-go for Nix cache Also fix scripts/update-status-go.sh to accept commit SHA1 Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-07-22 03:31:47 +00:00
"repo": "status-go",
[#9927] Fast blocks sync after being offline Front end changes: As there is no guarantee that `newblock` event will be dispatched consequently (e.g. if there was a delay after block#1 the next event might be dispatched for a block#2000, no guarantee that block#2 will be the next one), `newTransactions` field was added with a map of accounts to the number of new transactions received to this block. In result if there are new transactions we request them all of db instead of fetching them on for the block specified in `newblock` event, as it was done previously. Back end changes: - In order to avoid handling of the reorganized blocks we use an offset from the latest known block when start listening to new blocks. Before this commit the offset was 15 blocks for all networks. This offset is too big for mainnet and causes noticeable delay of marking a transfer as confirmed in Status (comparing to etherscan). So it was changed to be 5 blocks on mainnet and is still 15 blocks on other networks. - Also before this commit all new blocks were handled one by one with network specific interval (10s for mainnet), which means that in case of lost internet connection or application suspension (happens on iOS) receiving of new blocks would be paused and then resumed with the same "speed" - 1 blocks per 10s. In case if that pause is big enough the application would never catch up with the latest block in the network, and this also causes the state of transfers to be delayed in the application. In this commit in case if there was more than 40s delay after receiving of the previous block the whole history in range between the previous received block and ("latest"-reorgeSafetyDepth) block is checked at once and app catches up with a recent state of the chain.
2020-01-29 09:13:12 +00:00
"version": "v0.41.1",
"commit-sha1": "c2f22f1fbc73e68b8d82370c4645c786739fb40b",
"src-sha256": "038paj2gwdih154nnafcxc3w02x9p21ifkv1g9k2rr1ac0ypainb"
nix: Use status-go commit sha1 in Nix expression to allow for moving branches Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-07-19 18:42:16 +00:00
}