Add simulator service for generating throttling data and state diffs for txs #7
Conversation
This file contains hidden or 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
…ations and notification to trigger them
…types in the simulator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The simulator listens to mempool events to simulate new bundles, and listens to chain events from ExEx to trigger new simulations at the top of each block. We currently capture the execution time to use for throttling and the state diffs to pass to searchers so we can move MEV auctions off chain.
The simulator is temporarily set up to run with builder-playground in place of op-rbuilder so rollup-boost can send Engine API calls on port 4444. This will be replaced with a separate op-node instance for just the simulator. Until then, the simulator is in a separate docker-compose profile so it won't start by default.