Paul D.

I looked through each edit. I see no reason for any of these arguments to be signed. It just adds complexity, adds checking overhead, and decreases possible address offsets, lengths,...

How about the first argument is the output. so output position is consistent for different numbers of arguments, for example `binary_op(output,input1,input2)` and `unary_op(output, input)`?

> What would be the benefit we gain? Convention. Gnu Multiple Precision and lots of crypto pass output first. But it doesn't matter. > We also need to make a...

> What about returning a carry where necessary, e.g. add256? Makes sense to return a carry. It may also make sense to have an extra argument for carry. > Whether...

Good ideas and good points. I just want to write down the design problem. ewasm contracts will be Wasm modules. So we have the option to use Wasm's import/export infrastructure...

Another possibility for calling functions in other modules: Using `call_indirect`. Brief description: - A contract can import the table and use `call_indirect` to call functions based on their index in...

We have discussed options of disallowing `memory.grow`, or bounding Wasm memory with gas charges. The WebAssembly spec Section 7.2 Implementation Limitations lists many more things. There are some subtle things...

The option to bound Wasm memory with gas would involve the honest majority of miners keeping the gas limit low enough so that their clients can easily handle any amount...

More generally, it seems that we want Clients and VMs to both be swappable by each exposing only an API. I can envision three common cases, which follow. 1) Client...

A comment which may confuse the conversation. Feel free to ignore. When someone reads "Ethereum Environment Interface", it needs explanation. "Ethereum Client-VM Connector API" is more self-explanatory, but the word...