-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle forked blocks #229
Comments
any ideas about it? @insipx |
currently trying to reproduce currently on my archive node. Might require some further investigation into I also got different values for blocks 3909354 from subscan than you listed: Subscan Values: Interestingly again, Polkascan can't seem to agree on the values either: Polkascan Querying the RPC on my polkadot archive node, I got the same values you listed so those are definitely the correct ones |
The easiest way to ensure we only index finalized blocks is not indexing anything beyond the latest finalized block: substrate-archive/substrate-archive-backend/src/read_only_backend/blockchain_backend.rs Line 68 in 30ecb33
We could just let reorgs take place, and only keep up with the last finalized block. I think this issue only arises once Archive is caught up to the running chain already, so it shouldn't matter too much if we're a couple blocks behind, and avoids all the logic or updating/reinserting blocks that are being reorged |
polkadot 0.8.28-1-99043f78-x86_64-linux-gnu:
actual block 3909354 hash: 0xd780f986d5dfbad0236876940b23bef8b0abbba03ba503cf7a8288732d6d2e37
actual block 3909355 hash: 0x29be35af4c97f731c9607f78467b9cbc6213fa22ef2403c104976c1a6783d83a
actual block 3909356 hash: 0xeb5dd585e06635916228943f6d1eeae3074ed69efee0f97ddf9f314ebdbad4c3
actual block 3909357 hash: 0x6be2819b88e29250f1b6fedf27a6c809ac2f31ed104d78c165bf12deefe9000d
The text was updated successfully, but these errors were encountered: