Alex Beregszaszi

I see two options: 1) returns `struct account`, but has a field within: `int exists`. 2) takes pointer to `struct account` and returns int I think 1) may be nicer...

@chfast are you tackling this for 7?

@chfast why is this needed?

@chfast is this still valid? https://github.com/ethereum/evmc/blob/master/include/evmc/hex.hpp still has a few functions without `noexcept` probably because fo `.reserve()`.

I was thinking about this and of course it has to be optional, but instead of in execute, I think it should be in some kind of initialisation stage. Actually...

An update on this: evmone has some support for tracing merged, though it is not part of the EVMC interface. Also we are considering an Wasm version (including for use...

The libc on eWASM (soon to be uploaded) can be reused for this to compile C snippets.

The private key is stored using a wrapper over bn.js here: https://github.com/bitpay/bitcore-lib/blob/master/lib/hdprivatekey.js#L193 And the said wrapper's serialisation method (https://github.com/bitpay/bitcore-lib/blob/master/lib/crypto/bn.js#L71) must have this issue. I'm wondering though why this wrapper isn't...

@braydonf actually I would suggest using `toArrayLike(Buffer, 32, 'be')` to avoid the need of back and forth hex conversion.

> BIP032 states serialization to be 32 bytes as input, and with leading zero for 33 bytes: There's a leading zero prepended in every case during private key derivation, however...