Dimitrios Kouzis-Loukas

Unfortunately there seems to be even more work beyond @reiven 's work to be done on almost every method e.g. `eth_newFilter`: ``` Traceback (most recent call last): File "tick.py", line...

Yes, we have serious issues with the concept of backwards-compatibility, since re-linking 1000's of applications in a reasonable amount of time (

@wu-sheng - interesting metric. 15% meaning 15% overhead on the application it traces? i.e. if the app uses 60% of 8 CPUs, app + tracing uses 70%?

Interesting. Makes perfect sense! For me there might be something like a taxonomy related to a) capabilities of tracing systems b) cost of implementation c) latency and d) approach in...

## Higher Order Tracers (HOT) & Migrating Between Vendors I think there's a case for Higher Order Tracers i.e. Tracers that combine other tracers (at construction time) e.g. ``` import...

@yurishkuro - I agree... no "formal" namespacing. Just that people should be aware of aliases when they design their protocols. One interesting corner-case is baggage where I can imagine implementations...

From the previous discussion... > yes, the attributes is the only read operation in the whole API, so I think the composite tracer will have to pick one of the...

Let's assume that I upgrade from a tracer that doesn't support baggage propagation to one that supports (or the reverse). I think this use case, could easily hint towards a...

No - you are correct. There were two issues on baggage, one is the one you said above, about the prefixed-keys. i.e. if someone sets `"hello": 12` as baggage, e.g....

What are your thoughts on `ACCUMULATE`?