Xor error handling does not respect the relay about aqua HOT 4 CLOSED

Can you write an example? Because I already met with this, but it was not a bug, but a route simplification that is built into the compiler.

from aqua.

I think it actually doesn't matter which instruction was the last one because the execution may break on the remote peer anywhere inside the script. In that case we ALWAYS need the hop through the relay

from aqua.

I think the best solution is to modify every OnTag, wrapping its contents with xor with the exact path to init peer, so that we have many xor wrappers instead of a single one. Each wrapper may add something like a code branch label to the callback so that it's easier to find what exactly failed in case of error.

from aqua.

Each wrapper may add something like a code branch label to the callback so that it's easier to find what exactly failed in case of error.

%last_error% already kinda solves this, but on the AIR level obviously. Adding Aqua expression that caused the error would pretty useful.

from aqua.