Message model #4
Description
What should the minimal message model look like?
Currently in the prototype a non-atomic message consists of a payload, resources, hops, origin. And an atomic message has the addition of a commit lock and a response port.
I was wondering if it worth the effort to try to make the base non-atomic message simpler, but I don't currently see away to remove anything. Resources contain some unit of "gas" and since all action need to have gas allocate be for they are executed the kernel must explicitly know about it. hops aren't really usefully in current Ethereum, but if messages could be forwarded then they would become useful. Since message payloads would be immutable the only thing that would be mutable on a message is the hops count. This then could be used by forwarding contracts to figure out where to send the message