-
Notifications
You must be signed in to change notification settings - Fork 246
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
Transaction sortition for inclusion in bundle #1530
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make sense over all. Is there any specific reasoning behind the initial tx_range ? If so, can you point me to the spec pls
Not a blocker but I feel Transaction selection makes more sense to me than transaction sortition and selector is used in some places as well.
Either is fine but we should be consistent
Changed it (back to TxSelector, as it was originally). The cmd line flags are still call sortition, otherwise it becomes hard to tell this feature is sortition related |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few nits and unsure about the feature flag enable_tx_sortition
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me logically. For the actual code quality others should approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor comments and still unsure if the feature flag is necessary.
PTAL |
bd54ee0
to
766954e
Compare
Co-authored-by: Liu-Cheng Xu <[email protected]>
This PR implements the bundle proposer changes to include the transactions based on sortition. The tx range is static as of now. Dynamic adjustment of tx range would be in separate changes.
Code contributor checklist:
Issue: #1495