64 Commits (3dea9b9d25fe344a457065ec65422a81b54197d2)

Author	SHA1	Message	Date
Viktor Baranov	58236eebb9	Do not fill pending blocks ops with block numbers below TRACE_FIRST_BLOCK	3 years ago
Viktor Baranov	a58f3d5799	Extend TRACE_FIRST_BLOCK env var to geth variant	3 years ago
Viktor Baranov	714670e9c2	Separate FIRST_BLOCK and TRACE_FIRST_BLOCK option for blocks import and tracing methods	3 years ago
nikitosing	1a54597b4d	Add decoding for revert messages on a read contract page	3 years ago
Viktor Baranov	c685cd00fd	ERC-1155 transfers support in UI ... (cherry picked from commit d8b6f073c1)	3 years ago
Victor Baranov	6626502e90	Take into account FIRST_BLOCK in trace_ReplayBlockTransactions requests	5 years ago
Victor Baranov	93a2fd4960	Take into account FIRST_BLOCK for block rewards fetching	5 years ago
Victor Baranov	41dc4bdb4d	Finalize Besu variant	5 years ago
Victor Baranov	ee3a819c3f	Besu support	5 years ago
Victor Baranov	77ec071ef7	Raw trace on demand	5 years ago
Ayrat Badykov	b4387c2701	support chainId in integer format	5 years ago
Ayrat Badykov	2207de931c	add net_version function	6 years ago
goodsoft	8e6ee4ceb1	Use eth_getUncleByBlockHashAndIndex for uncle block fetching ... Parity returns `null` for many uncle blocks, if they are fetched using `eth_getBlockByHash`. This is most probably caused by the fact that Parity only keeps full block data for recent non-consensus blocks. This causes uncle_block fetcher to loop endlessly trying to fetch "missing" blocks, hogging both app server and Parity resources. Instead, we use `eth_getUncleByBlockHashAndIndex` method, which works for all uncle blocks. As we didn't previously store index of an uncle block within a nephew block, a new field and a temporary fixup fetcher is added to get the index from nephew blocks.	6 years ago
zachdaniel	8c1bb01fb1	feat: Add RSK support	6 years ago
goodsoft	ea3af5e299	Use transaction-level fetch_internal_transactions for Geth ... Internal transaction fetcher is split into two APIs: * `fetch_block_internal_transactions` is used for Parity * `fetch_internal_transactions` is used for the rest of variants `Indexer.InternalTransaction.Fetcher` is updated to take care of that.	6 years ago
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
Luke Imhoff	8135fcafbd	Allow lists of block numbers instead of ranges for beneficiares ... Simplifies calling as numbers don't need to grouped into ranges when getting numbers from database.	6 years ago
Ayrat Badykov	e40e4dca27	fetch codes	6 years ago
Luke Imhoff	97ce8e838b	Don't reference Explorer types in EthereumJSONRPC ... EthereumJSONRPC is not supposed to depend on Explorer at a code level, it should at most cross reference it in docs.	6 years ago
Luke Imhoff	a599aaff06	Extract EthereumJSONRPC.Block.ByTag	6 years ago
Luke Imhoff	3499155cdb	Partial retries for fetch_blocks_by_range ... Means that both Block.Fetchers, realtime and catchup, now handle fetch errors. The Block.Catchup.Fetcher will retry those blocks that failed to fetch while importing the rest that did fetch instead of refetching the whole batch.	6 years ago
Luke Imhoff	d43a8c6133	Partial retry of batches of blocks by hash	6 years ago
Luke Imhoff	3efa2d9996	Partial retries for CoinBalance.Fetcher	6 years ago
Andrew Cravenho	a64a1dc6bb	Update sokol node tests	6 years ago
Andrew Cravenho	063c393281	Update documentation replacing old sokol nodes	6 years ago
Luke Imhoff	3973e6607d	Support Parity 2.1 pending tag output ... It returns `number: null` instead of `null` or an error.	6 years ago
Alex Garibay	bbf88ca947	Fix typo	6 years ago
Alex Garibay	6d61420f32	Address code review feedback	6 years ago
Alex Garibay	76970f6258	Finish documentation and tests for request backoffs	6 years ago
zachdaniel	75c88fac85	WIP: test rolling window and request coordinator	6 years ago
Alex Garibay	be7271a8d9	WIP: clean up request coordinator with functionality and docs	6 years ago
Alex Garibay	1f021a7e1f	Provide default 2nd arg for executing contract functions on Geth (#970)	6 years ago
Sebastian Abondano	2b8ceb4e32	Update block reward contract beneficiary balances ... Why: * "Parity’s consensus engine allows using a smart contract for block reward calculation." - see https://wiki.parity.io/Block-Reward-Contract for details. This means that we need to use `trace_block` (https://wiki.parity.io/JSONRPC-trace-module#trace_block) to fetch the block reward contract beneficiaries and update their balances. Currently this doesn't happen so there are addresses (block contract reward beneficiaries) with inaccurate balances and missing rows in the `address_coin_balances` table. * Issue link: https://github.com/poanetwork/blockscout/issues/767 This change addresses the need by: * Adding `EthereumJSONRPC.fetch_beneficiaries/2` to help us fetch the block reward contract beneficiaries of a given block range. This only works with Parity. * Editing Indexer's dev and prod config by adding `trace_block` config to `:method_to_url`. * Adding `block_reward_contract_beneficiaries` to `Indexer.AddressExtraction` for it to know how to get addresses in this scenario. * Editing `Indexer.Block.Fetcher.fetch_and_import_range/2` to get block reward contract beneficiaries, create their addresses if they don't yet exist, and update their coin balances.	6 years ago
Konstantin Zolotarev	0604f7a234	Fixes for pr comments	6 years ago
Luke Imhoff	480300b542	Ethreums -> Ethereum	6 years ago
Luke Imhoff	6dbb511700	failes -> fails	6 years ago
Luke Imhoff	96d5aea311	Block.SecondDegreeRelation ... The database table block_second_degree_relations contains links between the `uncle_hash` of the uncle and the `nephew_hash` of the block that said `uncle_hash` was an uncle. It also has a `uncle_fetched_at` that is `null` until the `uncle_hash` is confirmed as fetched in the database. This does not contain such a fetcher.	6 years ago
Igor Florian	d460fb8d50	Deal with :bad_gateway errors while querying contracts functions ... We were counting on a specific error standard from ethereum_jsonrpc for formatting the errors from the SmartContract.Reader and we ended up getting an exception because we were getting a different error. There are at least two different error standards returned from ethereum_jsonrpc: 1. ```elixir { :ok, [ %{ id: id, jsonrpc: "2.0", error: %{ code: "12345", message: "<message>" } } ] } ``` 2. ```elixir {:error, {:bad_gateway, "<url>"}} ``` We're now expecting the :bad_gateway error so we can format it properly.	6 years ago
Luke Imhoff	9e6198da1b	Cover EthereumJSONRPC	6 years ago
Igor Florian	c2ff17756c	Get TokensBalance in the Blockchain ... We're now able to get the balances from a Address given it's address_hash, block_number and token_contract_address_hash.	6 years ago
Luke Imhoff	dc5ec15619	Support for Moxing WebSocket	6 years ago
Luke Imhoff	6036dea12d	Websocket json_rpc, subscribe, and unsubscribe against Sokol	6 years ago
Luke Imhoff	3427873986	{:ok, nil} -> {:error, :not_found} in handle_get_block_by_tag ... Fixes #490 Compatibility with paritytech/parity-ethereum#8281, which fixed paritytech/parity-ethereum#8028 and made pending return be compliant with Ethereum docs.	6 years ago
Luke Imhoff	e3f7581572	Historical Address Balances	6 years ago
Amanda Sposito	dae9ff2f10	Add support to Pluggable Transport and HTTP transport modules	6 years ago
Lucas Narciso	537f090597	Create Explorer.SmartContract.Reader ... This new module is the main entry point for getting results of a smart contract function. It accepts a smart contract hash and a list of functions names and its arguments (when applicable) in order to execute those functions and return their results. Before actually making the call to the blockchain, the function name is encrypted and the arguments are encoded. The EthereumJSONRPC deals with this, encrypting the name of the function using the Keccak256 algorithm and encoding the arguments based on their type. The call to the blockchain is also made by EthereumJSONRPC. The result is then decoded - as it comes in the same type of encoding that has been sent - by the EthereumJSONRPC lib as well, and returned. The return is a list of results of calling the functions in the blockchain. Note that each function may return more than one result, so for each functions there is a list of results.	6 years ago
Lucas Narciso	acdbed2ba7	Support eth_call on EthereumJSONRPC ... It just makes the call, so the smart contract function name should already be encrypted and its arguments already encoded. It supports multiple function calls, by receiving a list of hashs and data, e.g. `[{contract_hash_1, call_data_1}, {contract_hash_2, call_data_2}]`.	6 years ago
Luke Imhoff	834ad23f26	Standardize JSONRPC response ... Restrict response to only those fields supported by the JSON-RPC 2.0 standard, which means that level of keys is validated, so we can indicate that switch to atom keys.	6 years ago
Luke Imhoff	466c1e76f6	Request transport module and options for all JSONRPC calls ... To lessen load on Sokol chain nodes during testing and to allow substituting different transports than HTTP, such as IPC, in the future, pass the transport module and its options to any call to `EthereumJSONRPC.json_rpc`. This will allow us to use a `mox` module in local testing, so we only do true chain integration testing in CircleCI.	6 years ago
Luke Imhoff	3c680ff953	Log, but do not fail tests, when 502 Bad Gateway occurs ... 502 Bad Gateway is an intermittent problem that needs to be fixed by ops when the JSONRPC servers are under heavy load, so they should not fail the test runs.	6 years ago