Skip to content

Conversation

@Tomi-3-0
Copy link
Contributor

@Tomi-3-0 Tomi-3-0 commented Oct 22, 2025

Implement execution payload bid pool for Gloas

@Tomi-3-0 Tomi-3-0 changed the title Vxt Add execution payload bid pool Oct 22, 2025
@Tomi-3-0 Tomi-3-0 marked this pull request as ready for review October 23, 2025 02:07
@Tomi-3-0 Tomi-3-0 marked this pull request as draft October 23, 2025 02:07
@Tomi-3-0 Tomi-3-0 marked this pull request as ready for review October 23, 2025 02:46
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
Copy link
Contributor

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

@github-actions
Copy link

github-actions bot commented Oct 23, 2025

Unit Test Results

       15 files    3 035 suites   1h 28m 2s ⏱️
12 628 tests 12 048 ✔️ 580 💤 0
79 386 runs  78 509 ✔️ 877 💤 0

Results for commit ba77b81.

♻️ This comment has been updated with latest results.

@Tomi-3-0 Tomi-3-0 marked this pull request as draft October 23, 2025 14:27
@Tomi-3-0 Tomi-3-0 requested a review from tersec October 23, 2025 22:04
@Tomi-3-0 Tomi-3-0 marked this pull request as ready for review October 23, 2025 22:04

try:
for key, detail in pool.bids:
if detail.bid.message.slot < finalizedSlot:
Copy link
Contributor

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.

Copy link
Contributor Author

@Tomi-3-0 Tomi-3-0 Oct 24, 2025

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)

Copy link
Contributor Author

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.

@Tomi-3-0 Tomi-3-0 requested a review from tersec October 27, 2025 18:29
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.

2 participants