Implement 8 more of the core eth_* read-only RPC endpoints

This is a tracking issue for the next alpha release milestone. The endpoints are a subset of #612, and can be chosen from that list as desired. Feel free to make individual PRs for each endpoint chosen (or group them if there are a few that are trivial to group). Link the PRs back to this issue for tracking.

This list is NOT kept up to date – see the list at #612 for the latest known state of implemented rpc methods

• eth_accounts (always return [])
• eth_syncing
• eth_gasPrice (should get its own issue to plan the algorithm)
• eth_getBlockTransactionCountByHash
• eth_getBlockTransactionCountByNumber
• eth_getUncleCountByBlockNumber block string
• eth_call
• eth_estimateGas
• eth_getTransactionByHash
• eth_getTransactionByBlockHashAndIndex
• eth_getTransactionByBlockNumberAndIndex
• eth_getTransactionReceipt
• eth_getUncleByBlockHashAndIndex
• eth_getUncleByBlockNumberAndIndex block int
• eth_getUncleByBlockNumberAndIndex block string
• eth_getLogs

[pipermerriam]

personal_ will be lower priority for a while here.

1. because we don’t plan to do key management.
2. because it’s a non-standard API that only exists in geth

We can add or mock any behavior in eth-tester but it’s a bit ambiguous to me how to best implement something like the personal_ module functionality in a modular fasion. Since it’s non-standard JSON-RPC API, I wouldn’t want it to be a core piece, but rather something that could be enabled.

[carver]

Sweet, I guess someone just forgot to check off some methods after implementing them. With those, and the three more implemented, we now have 8 more than we thought we had. Just under the wire for today’s release. 😃