* [rpc] updated rpc to GetCirculationSupply to sub token burnt
* [explorer] add a small fix
* [rpc] fix at getInaccessible tokens
* [rpc] added fix at header.Root
* [explorer] added a lot of code
* [explorer] added a lot of code
* [explorer] more adding
* [explorer] clean up and more code added
* [explorer] fixes according to test results
* [explorer] changed leveldb params, batch size, and a dirty data fix
* [explorer] fix on dirty data, fix on HasPendingTasks, and increase worker number
* [explorer] fix for contract creation
* [explorer] fixed local travis test
* [explorer] added caching fix at flushing db.
* [explorer] fixed all rpc points
* [explorer] small change to refactor storage.Start
* [explorer] fix go test
* [explorer] further increase the batch size
* [explorer] release lock during db writing data
* [explorer] change to rlock/runlock at flushLocked
* [explorer] also add flush time mechanism to trigger flushing
* [explorer] when checking checkpoint, first check memory, then check db
* [p2p] ban beacon node sync message where block height is smaller than current height
* small param change
* small wording fix
* elaborate log message
* fix spelling
During the p2p message validation, the node will drop the node message if
the size is bigger than the MaxPoolTransactionDataSize.
The initial value was just a heuristic value set during the open staking testnet.
However, the valid node message becomes
bigger now due to the higher tx count in the mainnet. So we need to lift the
upper bound. We have observed the oversized node message from metrics.
Ex,
use `curl http://localhost:9900/metrics | grep ^hmy_p2p` to check the metrics
hmy_p2p_node_msg{type="invalid_oversized"} 3484
Signed-off-by: Leo Chen <leo@harmony.one>