The expectation will be for the bytes to be exactly right (they're created by the multi tracer on the other side). This is the combined byte string for the actual tracers.

One situation where this deserialisation could go wrong is where different tracers are configured on different remote nodes. It could align trace context bytes to the wrong tracers. So should it also include class names and map to tracers?

Or when there's a single tracer on the sending side and a multi tracer on the receiving side, it will try to decode the bytes for multiple tracers but there will only be the bytes for a single tracer there. This is more awkward and would always require a mapping to tracers to be used in the protocol.