Blockchain explorer for Ethereum based network and a tool for inspecting and analyzing EVM based blockchains.

History

Paul Tsupikoff 2a8def19e2 Allow executing smart contract functions in arbitrarily sized batches # Problem There are a lot of `getBalanceOf` token function calls during indexing blockchain. Each of them is sent as a separate JSONRPC request, which creates a lot of unnecessary overhead and clogs archive node workers, which could otherwise be busy performing other JSONRPC queries. Moreover, function name is used as the `id` parameter of JSONRPC queries, which doesn't allow us to simply put multiple requests into one batch. # Solution * Change `EthereumJSONRPC.execute_contract_functions` to accept a list of arbitrary function calls and return a list of results. * Handle `id` field generation in the `EthereumJSONRPC` package instead of leaking implementation details to `Explorer.SmartContract.Reader`. * Change `Token.BalanceReader.get_balance_of` to accept a list of parameter sets and return a list of balances. * Make one batch request instead of launching multiple concurrent tasks in `Indexer.TokenBalances.fetch_token_balances_from_blockchain` # Notes * Protocol details of calling smart contract functions is now fully encapsulated in `EthereumJSONRPC` package. * `SmartContract.Reader.query_contract` is left for backwards compatibility with other existing applications of smart contract requests, but can be fully deprecated at some later time.		6 years ago
..
config	set correct log level for production	6 years ago
lib	Allow executing smart contract functions in arbitrarily sized batches	6 years ago
test	Allow executing smart contract functions in arbitrarily sized batches	6 years ago
.gitignore	mix new indexer --sup	7 years ago
README.md	Update sokol node tests	6 years ago
mix.exs	upgrade elixir to 1.8.1	6 years ago

README.md

Indexer

TODO: Add description

Installation

If available in Hex, the package can be installed by adding indexer to your list of dependencies in mix.exs:

def deps do
  [
    {:indexer, "~> 0.1.0"}
  ]
end

Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/indexer.

Memory Usage

The work queues for building the index of all blocks, balances (coin and token), and internal transactions can grow quite large. By default, the soft-limit is 1 GiB, which can be changed in config/config.exs:

config :indexer, memory_limit: 1 <<< 30

Memory usage is checked once per minute. If the soft-limit is reached, the shrinkable work queues will shed half their load. The shed load will be restored from the database, the same as when a restart of the server occurs, so rebuilding the work queue will be slower, but use less memory.

If all queues are at their minimum size, then no more memory can be reclaimed and an error will be logged.

Testing

Parity

Mox

This is the default setup. mix test will work on its own, but to be explicit, use the following setup:

export ETHEREUM_JSONRPC_CASE=EthereumJSONRPC.Case.Parity.Mox
mix test --exclude no_parity

HTTP / WebSocket

export ETHEREUM_JSONRPC_CASE=EthereumJSONRPC.Case.Parity.HTTPWebSocket
mix test --exclude no_parity

Protocol	URL
HTTP	`http://localhost:8545`
WebSocket	`ws://localhost:8546`

Geth

Mox

export ETHEREUM_JSONRPC_CASE=EthereumJSONRPC.Case.Geth.Mox
mix test --exclude no_geth

HTTP / WebSocket

export ETHEREUM_JSONRPC_CASE=EthereumJSONRPC.Case.Geth.HTTPWebSocket
mix test --exclude no_geth

Protocol	URL
HTTP	`https://mainnet.infura.io/8lTvJTKmHPCHazkneJsY`
WebSocket	`wss://mainnet.infura.io/ws/8lTvJTKmHPCHazkneJsY`