* Start removing duplicated functionality (v1 inside v2)
* Update compilation targets
* Update locks
* Fix js-old build
* Update with removed extra references
* Adapt dev.{parity,web3}.html for extra debug info
* Update dependencies
* Remove Tooltips
* Update dependencies
* Only inject window.ethereum once
* Fix versions to 2.0.x for @parity libraries
* Update to @parity/api 2.1.x
* Update for @parity/api 2.1.x
* Freeze signer plugin dependency hashes
* Fix lint
* Move local account handling from API
* Update for 2.2.x @parity/{shared,ui}
* Update API references for middleware
* Install updated dependencies
* Update for build
* Always do local builds for development
* Remove unused hasAccounts property
* Fix Windows build for js-old
* Adjust inclusing rules to be Windows friendly
* Explicitly add --config option to webpack
* Add process.env.EMBED flag for Windows compatability
* Revert embed flag
* Fix build
* Merge changes from beta
* Update packages after merge
* Update Accounts from beta
* Update with beta
* Remove upgrade check
* Fix CI build script execution
* Make rm -rf commands cross-platform
* Remove ability to deploy wallets (only watch)
* Update path references for js-old (Windows)
* Render local dapps first
* Cleanup dependencies
* Optional offset and count added on client level
* Rpc interface extended
* Tests corrected
* Filtering code refactored a little bit
* Offset type was changed to usize
* Handling of block hash in offset added
* Offset reworked to number
* Trailing comma removed
* Import for Quantity type added
* Offset and count moved into filter object
* Lost comma removed
* Return empty vec instead of None in case of incorrect range
* Add RPC eth_chainId for querying the current blockchain chain ID
Currently although we can use `net_version` RPC call to get the
current network ID, there's no RPC for querying the chain ID. This
makes it impossible to determine the current actual blockchain using
the RPC. An ETH/ETC client can accidentally connect to an ETC/ETH RPC
endpoint without knowing it unless it tries to sign a transaction or
it fetch a transaction that is known to have signed with a chain
ID. This has since caused trouble for application developers, such as
MetaMask, to add multi-chain support.
The same RPC endpoint is also about to be merged for ETC's
go-ethereum: https://github.com/ethereumproject/go-ethereum/pull/336
* Add eth_chainId to js's web3 interface
* Add a mocked test for eth_chainId
* Add chainId in js's jsonrpc interfaces
* Change return type for eth_chainId to `Option<u64>`
* Change name eth_chainId to parity_chainId
* Wrong test name and missed var for rpc_parity_chain_id test
* Use U256 to return chainId and fix for master
u64 returns decimal integer, and there seems to be no type called
U64. So here I use U256 to return the hex integer.
* Fix chainID test
Before EIP155 fork number, chainID should be null.
* Change both parity_chainId and transaction::chainId to use U64
This makes it consistent that all chain ids returned are hex string.
* Fix wrong U64 serialization
