OpenZeppelin / OpenZeppelin/Event-Scanner
fix: Figure Out How to Handle `to_block(block_hash)` being reorged during historic streaming
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
Related #193
Will become relevant after #193 is implemented.
We need to decide what should happen if a reorg happens during historic streaming and the specified to_block no longer exists.
NOTE: since the scanner normalizes from/to blocks, i.e. the client can set to_block to be lower than from_block, when we refer to to_block in this issue, we refer to the block with the higher block number post-normalization.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing related issue #193 and how it defines historic streaming and block normalization. Focus on the reorganization case where the normalized higher-numbered to_block no longer exists. Done means the expected behavior is decided and clearly recorded for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100