Skip to content

Conversation

@prestwich
Copy link
Member

wip: add host sim

fix: add host evm and fix fill detection

@prestwich prestwich marked this pull request as ready for review October 30, 2025 17:45
@prestwich prestwich requested a review from a team as a code owner October 30, 2025 17:45
Copy link
Member Author

prestwich commented Oct 30, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@prestwich prestwich changed the base branch from prestwich/fill-builder to graphite-base/132 October 30, 2025 18:15
@prestwich prestwich force-pushed the prestwich/host-sim-wip branch from 579a7a3 to a853470 Compare October 30, 2025 18:15
@prestwich prestwich changed the base branch from graphite-base/132 to prestwich/remove-host-fills October 30, 2025 18:15
@prestwich prestwich force-pushed the prestwich/host-sim-wip branch from a853470 to 19236a0 Compare October 30, 2025 18:36
@prestwich prestwich changed the base branch from prestwich/remove-host-fills to graphite-base/132 October 30, 2025 20:02
@prestwich prestwich force-pushed the prestwich/host-sim-wip branch from 554d991 to 01d39a5 Compare October 30, 2025 20:06
@prestwich prestwich changed the base branch from graphite-base/132 to prestwich/remove-host-fills October 30, 2025 20:06
Copy link
Member

@Evalir Evalir left a comment

Choose a reason for hiding this comment

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

looks solid so far, few qs

candidate_orders.absorb(&tx_orders);

// Then we check that the fills are sufficient against the
// provided fill state. This does nothing on error.
Copy link
Member

Choose a reason for hiding this comment

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

shouldn't this be does nothing on success?

Comment on lines +209 to +213
// This is redundant with the driver, however, we double check here.
// If perf is hit too much we can remove.
self.rollup
.fill_state()
.check_ru_tx_events(&outputs.bundle_fills, &outputs.bundle_orders)?;
Copy link
Member

Choose a reason for hiding this comment

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

why double check? genuine question, want to understand the reasoning

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.

3 participants