OpenZeppelin / OpenZeppelin/Event-Scanner
Add support for pending blocks in Latest and Historic Modes
Open
Nobody has claimed this yet.
priority: low
status: needs discussion
type: enhancement
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
Add support for pending blocks. The issue is that this may cause issues during reorgs.
What can happen is that what were previously Pending logs are part of the chain post-reorg. This would mean that the returned events would now contain effectively duplicate logs, ones in Pending state, and the same ones in Included state.
Related to #243
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
No files, tests, or entry points are identified in the issue. Start by reviewing the pending and included event handling and related issue #243; done should include pending blocks while avoiding duplicate logs when a reorganization moves pending logs onto the chain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100