forked from paradigmxyz/reth
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Spawn executor in transaction pool #25
Labels
A-execution
Related to execution and EVM
A-tx-pool
Related to transaction pool
D-interop-devnet
Planned for interop-devnet
Comments
use branch |
this is already performed on a validation task |
links pls @mattsse ? |
this is just configures the number of validation tasks, I don't see anywhere to pass a hook to tx pool validation to perform an extra task? cc @Rjected |
refcell
added a commit
that referenced
this issue
Jan 31, 2025
### Description Closes #25 Spawns an executor in transaction validation. --------- Co-authored-by: Emilia Hane <elsaemiliaevahane@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-execution
Related to execution and EVM
A-tx-pool
Related to transaction pool
D-interop-devnet
Planned for interop-devnet
Describe the feature
Spawn executor inside of
OpTransactionValidator::validate_one
to execute the transactions on the current state. Discard transactions that fail execution.op-reth/crates/optimism/node/src/txpool.rs
Lines 294 to 366 in fdb6925
Note: use trait bound
OpTransactionValidator<Client: StateProviderFactory, ..>
check out how it's done in rpc for
trace_filter
(https://www.quicknode.com/docs/ethereum/trace_filter)op-reth/crates/rpc/rpc-eth-api/src/helpers/trace.rs
Lines 328 to 399 in fdb6925
Additional context
Following issue will also use maili API to determine validity of the executed transaction, ref op-rs/maili#98
The text was updated successfully, but these errors were encountered: