EEI: blockhash to signal success or failure

ewasm / design

Ewasm Design Overview and Specification

Apache License 2.0

1.02k stars 125 forks source link

EEI: blockhash to signal success or failure #76

Closed axic closed 6 years ago

jwasinger commented 6 years ago

As an alternative, we could have the behaviorBLOCKHASH(num>256) = 0x0...0 in order to be more EVM-compliant.

However, this proposed solution is more transparent IMO.

axic commented 6 years ago

We are trying to avoid the implicit reporting. Also hope that before eWASM is final, the blockhash EIP will be merged and we could remove this interface.

axic commented 6 years ago

The other question is shouldn't al the other non-returning but data writing methods have a return value? e.g. codeCopy, externalCodeCopy, etc.

chfast commented 6 years ago

Probably they should. VM should also has an information whenever an account exists.

axic commented 6 years ago

Updated to match #77 and added a comment regarding the output memory.