eth/tracers: add multiplexing tracer#26086
Merged
holiman merged 3 commits intoethereum:masterfrom Nov 8, 2022
Merged
Conversation
Member
|
Good idea! |
holiman
approved these changes
Nov 5, 2022
Contributor
holiman
left a comment
There was a problem hiding this comment.
This is a nice idea. I'm curious to see if it is "only" a nice idea, or if it actually is meaningful too, in the sense that people will use it.
Up until now, I've been kind of starting to see a tendency to make tracers more complex, adding tracer-specific configurations (e.g. the call-tracer taking a config whether log log LOGs etc). This PR might make it a bit more "the Unix way", so the tracers are an assortment of small simple tools, and the ability to mux makes it possible to avoid complex tracers with everything and the kitchen-sink.
shekhirin
pushed a commit
to shekhirin/go-ethereum
that referenced
this pull request
Jun 6, 2023
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api
maoueh
pushed a commit
to streamingfast/go-ethereum
that referenced
this pull request
Jul 21, 2023
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api
19 tasks
gzliudan
pushed a commit
to gzliudan/XDPoSChain
that referenced
this pull request
Aug 4, 2025
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api
gzliudan
pushed a commit
to gzliudan/XDPoSChain
that referenced
this pull request
Aug 13, 2025
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api
gzliudan
pushed a commit
to gzliudan/XDPoSChain
that referenced
this pull request
Sep 9, 2025
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api
gzliudan
added a commit
to XinFinOrg/XDPoSChain
that referenced
this pull request
Sep 9, 2025
* eth/tracers: add native multiplexing tracer * minor improv callTracer * mv evm cancellation to api Co-authored-by: Sina Mahmoodi <1591639+s1na@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Sometimes users might need the result of multiple tracers for a given tx. This PR introduces the
muxTracerwhich allows you to do this. It takes in a list of tracers and their configs and returns each one's corresponding result with one run through the tx:There's a trick that allows you to use the same tracer with different configs by using a nested
muxTracer(e.g. to get both prestate and statediff):It's possible to directly add support for this to the API, e.g.
debug.traceTransaction('<txhash>', { tracerList: {...} })but I feel like being able to add this feature without having to modify the API is a big plus.Unrelated commit in the PR: I also moved EVM cancellation to be the API's responsibility instead of the tracer. I feel like it's more fitting.