-
Couldn't load subscription status.
- Fork 296
Add execution payload bid pool #7646
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
base: unstable
Are you sure you want to change the base?
Conversation
beacon_chain/nimbus_beacon_node.nim
Outdated
| MsgSource.gossip, signedBlock))) | ||
|
|
||
| # execution_payload_bid | ||
| # https://github.com/ethereum/consensus-specs/blob/v1.6.0-beta.0/specs/gloas/p2p-interface.md#execution_payload_bid |
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.
beta.1 is out now
|
|
||
| try: | ||
| for key, detail in pool.bids: | ||
| if detail.bid.message.slot < finalizedSlot: |
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.
How much of a concern is a whole-pool iteration, as this pruning code does? It's conceptually inefficient, but whether it's enough to be problematic.
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.
Very true.
I don't have a figure/data on what the pool size for the bids will potentially look like and the O(n) iteration could very well be bad.
We could potentilaly prune by slots O(slots) instead of bids O(bids)
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.
The performance gain from pruning by slots was negligible for large pools. The new approach stores only the highest-value bid per slot.
Implement execution payload bid pool for Gloas