-
Notifications
You must be signed in to change notification settings - Fork 2
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
Subscribe for events from a given block #83
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
khssnv
force-pushed
the
feature/subscribe-for-events-from-block
branch
2 times, most recently
from
March 15, 2024 13:16
854ed49
to
792dd79
Compare
khssnv
force-pushed
the
feature/subscribe-for-events-from-block
branch
from
March 20, 2024 13:20
d30e293
to
6cb83df
Compare
upalinski
reviewed
Mar 21, 2024
upalinski
reviewed
Mar 21, 2024
upalinski
reviewed
Mar 21, 2024
upalinski
approved these changes
Mar 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow events listening from a given (historical or future) block. Best block events will are on hold until the historical events sequentially processed. Default queue size is 20 000 blocks (source) which with 6 seconds block time gives us about 33 hours to process historical events before overflow. Also events listeners invocation made synchronous and a client may provide a callback function to call after all events listeners are done with a certain block events.