Alex Beregszaszi

Fixed by #25.

LEB128? CBOR?

Hmm, shouldn't it be a requirement that an immutable must always be assigned in the constructor? As opposed to allow the "default value" rule?

> Error: Some immutables were read from but never assigned, possibly because of optimization. Then why this error? If zero-by-default is allowed, then we do not need this special error.

Oh thanks for this! It is a bit unfortunate a lot of this was done in the `read-callback` and `cb` branches already :(

To clarify, I was caught up with other work, but have all the callback stuff finished and support for the 0.6 series, just wasn't sure what is the best approach...

How about setting a telegram to have discussions instead? I'm glad there is some life here! @g-r-a-n-t let me know if you are interested to join the conversation on Telegram,...

@hugo-dc sorry for the delay. Yes, that is correct, it needs to follow what specification of the EIP. I'm not sure if we can use the current crate - likely...

The current version of the Blake2 precompile is here: https://github.com/ethereum/EIPs/pull/2024 Our code is pretty close to that and would be easy to update.

It seems the now-current proposal is at https://github.com/ethereum/EIPs/pull/2129, which brings us back to a specification similar to https://github.com/ewasm/ewasm-precompiles/issues/36#issuecomment-458416477