Investigate JSON creation rule for zero account as recipient
If a JSON is created we have the following check for the zero account:

In this case, the receiver is not set in the JSON message. We should check if we can remove this check, as this JSON is also used to propagate messages between nodes.
So, you potentially want to check, if something is burnt? :fire:
I have a potential solution: If recipient Id = 0 we set a flag burnt=true, so no compatibility issue then.
What problems does this actually cause, and, more importantly, where is it in the code? I'm curious what this is for. Judging from @ohager's comment, it's a check to burn signa, but there's no context in this issue.
yep lost the context also - sh... I think something with the node comunication ... but maybe @jjos2372 rembers it... sorry