- Use defined constants instead of hard-coding their integer value.
- Allocate secp256k1 structs on the C stack instead of converting []byte
- Remove dead code

tests: unskip test

core: remove support for Olympic network

core: improve import log alignment

vendor: update dependencies

cmd/utils: fix comma-separated --bootnodes

The Azure SDK doesn't support Go 1.5 anymore. We can't upgrade it until
Go 1.8 comes out.

all: fix ineffectual assignments

params, VERSION: start 1.5.7 release cycle

params: stable version 1.5.6

go get github.com/gordonklaus/ineffassign
ineffassign .

We don't use this anymore.

les: fixed selectPeer deadlock, improved request distribution

core: fix race condition in WriteMipmapBloom

console: fix error message in faux JSON-RPC responses

accounts/abi: support custom int slice types

Check for slice in type as well and adapted test case as arrays
also store its types.

On solidity contract I have "uint32 []" type, when abigen creates Go
bindings - they are also "[]uint32" type on Go side. Even though it
looks like it should work - the actual type of the data coming from
the chain is of type " []*big.Int".

When executing contract function from Go side - getting unmarshal error:
abi: cannot unmarshal []*big.Int in to []uint32

The fix is to create array with the correct type

This fixed the issue reported in: https://github.com/ethereum/go-ethereum/issues/2802

The message was used as both key and value in the error object.
This only affected unusual errors with no error code.