dshulyak

i think parse_payload interface is not compatible with spawn (and remote execution in general). by design it parses two independent objects: header (max gas, gas price, nonce) and method call...

> at this level of abstraction, methodArguments is just an array of bytes. methodArguments can't be represented as array of bytes. even in your document there is no length prefix...

> It can be a fixed size byte array, since we can its length based on the entire transaction length minus known length fields. Does this solve the problem? i...

i need to finalize change to parse_payload (if any), there are three options: 1. split parse_payload into parse_envelope and parse_args. parse_envelope is called on principal account template, parse_args is called...

> main question i have is about the design. why not implement single sig acct as 1-1 and we will just have one type of wallet? i don't know yet...

bors merge

bors merge

i will actually close this. when the time comes it will be tracked elsewhere (svm probably)

> Right now, if many miners disappear for any reason, self-healing ensures that consensus will eventually be re-established and tortoise will begin verifying layers again, but this may take a...

btw the only time when self spawn can get consumed without spawning account is due to https://github.com/spacemeshos/go-spacemesh/issues/3391