Hugo

@axic fixed

I started this cargo submodule here: https://github.com/hugo-dc/cargo-build-ewasm it executes: `cargo build --target=wasm32-unknown-unknown --release`, then runs `chisel run` (expects a default `chisel.yml` configuration), and lastly executes `wasm-snip` to reduce the bytecode...

@axic please take a look at the deployed contract: http://ewasm.ethereum.org/explorer/account/0x793a8d040319253446F90D072D47e95719700026

Could you explain a bit further what has to be done? Here is what I understand so far: Current blake2 implementation just reads an input data and calculates the blake2b...

@yglukhov Contracts are deployed using ewasm-studio (http://ewasm.ethereum.org/studio/) or the explorer's deployer (http://ewasm.ethereum.org/explorer/deploy). You cannot deploy your wasm contract directly, it has to be wrapped into a deployer wasm module which...

@jwasinger I created a Dockerfile to generate the charts in a docker instance, but it is generating the exact same files (no diff), I'll take a closer look at the...

@lrettig I changed u256.js as @axic suggested, right now I have 40+ failing tests still have to figure out what is causing them.

@daxdax89 Try with this command: ``` NODE_ENV=production INSTANCE_NAME="ewasmTestnet" CONTACT_DETAILS="[email protected]" WS_SERVER=wss://ewasm.ethereum.org WS_SECRET=97255273942224 VERBOSITY=2 node app.js ```

I removed `startingBlock` for precompiles as all precompiles should be able to be callled since first block.

@jwasinger this genesis file won't work for the current testnet, the faucet balance was changed https://github.com/ewasm/testnet/commit/931c30402378176e2d34d7677bc38dc509deed45#diff-8ff30e3d87b04b0d6767d45bce187afd If you want to sync aleth to the testnet you must use the genesis...