Hex-String data type perhaps could be better described as “hex-encoded byte array”.
It’s not clear what exactly
returnStack is, please provide an example where it’s not empty.
Please provide an example where
error is not empty.
Clients SHOULD output the fields in the same order as listed in this EIP.
According to the JSON spec “an object is an unordered set of name/value pairs”, so strictly speaking this requires something not supported by JSON.
The CUT MUST NOT output a line for the
STOP operation if an error occurred: Example:
The example following this does in fact output
STOP operation, so it’s contradictory, or an example for something else.
This example of a summary contains
successful field not mentioned in the spec.