Idea from @pyskell

Allow declarative specify the account state in genesis block. After that, in block 1, also allow declarative executing transactions with the given account state in genesis block.

As all blocks for sputnikvm-dev is stored in memory and is not likely to be very long, create a new set of RPC endpoints that allows to modify account state starting from genesis block. This modification will spread through all blocks and transactions that have already been appended.

The request

{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["pending",true],"id":6}

Returns

{"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request"},"id":6}

(Requires sharing some code with etclient to avoid duplication.)

I've taken this request from MetaMask:

{id: 4645179836049334, jsonrpc: "2.0", params: ["0x52", true], method: "eth_getBlockByNumber"}

It returns

{"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request"},"id":4645179836049334}

To avoid using String in RPC calls all over the places.

The following parameters for eth_call cause error:

{"jsonrpc":"2.0","method":"eth_call","params":[{"to":"0x085fb4f24031eaedbc2b611aa528f22343eb52db","data":"0x70a08231000000000000000000000000255573e004be419bd9f9eb481276092423415fa9"},"latest"],"id":18}

Result:

{"jsonrpc":"2.0","error":{"code":-32602,"message":"Invalid params: missing field `from`."},"id":18}

Spec says that from field is optional - https://github.com/ethereumproject/wiki/wiki/JSON-RPC#eth_call

we have this in geth, would be great to have this in development for sputnikvm-dev

Allows uploading nightly builds to build.etcdevteam.com

• Update Appveyor releases deployment access token from @splix.

i use some really old builds. theres no windows build for v0.2.0-36, im using 26 to support windows for now.

• sputnikvm
• secp256k1-plus
• etcommon
• sputnikvm-dev

Thus truffle would be much faster.

eth_estimateGas rpc method should work even if only data parameter provided.

For instance,

const callData = {
    data: "0xblablabla",
  }
  let gas = web3.eth.estimateGas(callData);

It would be nice to have option '--db' which allows to load preconfigured blockchain snapshot.
Zipped snapshot as example can be found there https://s3.amazonaws.com/testrpc-shapshots/07d00cc515e0f9825b81595386b358593b7a3d6f.zip

Why this is important ? Developers can deploy a set of smart contracts once and then use it many times for testing some libraries.

Sputnik-vm-dev is a confusing name. Its a test Rpc server, lets just name it that.

@shanejonas

Remix successfully can be connected to sputnikmv-dev, but deploying contract doesn't work there. However deploy in truffle works fine.

If I understood correctly, for methods like eth_gasPrice, eth_getBalance and some other ZERO in result must be represented as 0x0, not as 0x.
(reference https://github.com/ethereumproject/wiki/wiki/JSON-RPC#output-hex-values)

Simply use sputnikvm::Opcode

Handle the case where hash for a block is not found in miner states and RPC.

Also after upgrading:

• Get miner to print out transaction hashes when it's mined.

The code can't be compiled and it gets bunch of errors.

This makes it less awkward when passing around the Client Arc.

Following code with web3.js causes sputnikvm-dev panic:

const callData = {
    from: "0x0000000000000000000000000000000000000000",
    gasPrice: "0x04a817c800",
    gas: "0x5208",
    to: "0x0000000000000000000000000000000000000000",
    value: "0x0de0b6b3a7640000",
    data: "",
  }
  let gas = web3.eth.estimateGas(callData);

Result:

thread 'http.worker0' panicked at 'arithmetic operation overflow', /home/bill/.cargo/registry/src/github.com-1ecc6299db9ec823/etcommon-bigint-0.2.9/src/uint/mod.rs:1184:0
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', /checkout/src/libcore/result.rs:906:4

sputnikvm-dev built by cargo run from master branch.

This is only applied partially currently.