Currently, whenever an EraVmError is encountered, we invoke the inexplicit_panic function. We need to confirm whether this behavior aligns with the specification.
I've been investigating this behavior and it does actually align with the spec. The only opcode that behaves differently is far_call which we are handling correctly through panic_from_far_call see here.
Currently, whenever an EraVmError is encountered, we invoke the
inexplicit_panic
function. We need to confirm whether this behavior aligns with the specification.