Skip to content

Conversation

@0xNeshi
Copy link
Collaborator

@0xNeshi 0xNeshi commented Sep 18, 2025

Closes #33

@0xNeshi 0xNeshi requested a review from LeoPatOZ September 18, 2025 09:42
@0xNeshi 0xNeshi self-assigned this Sep 18, 2025
The library exposes two primary layers:

- `EventScannerBuilder` / `EventScanner` – the main module the application will interact with.
- `BlockScanner` – lower-level component that streams block ranges, handles reorg, batching, and provider subscriptions. This is exposed to the user but has many edge cases which will be documented in the future. For now interact with this via the `EventScanner`
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already noted that this is in alpha, and the block range scanner is as stable as the event scanner, so seems redundant to recommend this.

@LeoPatOZ LeoPatOZ merged commit 26ee1ca into main Sep 18, 2025
6 checks passed
@LeoPatOZ LeoPatOZ deleted the block-scanner-rename branch September 18, 2025 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename BlockScanner to a More Accurate BlockRangeScanner

3 participants