74 Commits (8dfde6ad33ed0a58d5ebefa22cfebc240afbb827)

Author	SHA1	Message	Date
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
Luke Imhoff	4ecfb3b409	CircleCI tests for Geth	6 years ago
Luke Imhoff	cac1cab39c	Geth receipts compatibility ... When testing transaction receipt processing using Geth against Ethereum Mainnet, a number of missing features were discovered: * Support for `to` and `from` addresses in receipts * The need to derive status for pre-Byzantium transactions by using the supplied gas from the transaction and the gasUsed in the receipt to check for out-of-gas.	6 years ago
Luke Imhoff	72373f7770	method_to_url config ... Instead of making up symbolic names for the different types of URLs we need, have the configuration be a base `url` for a fallback and then entries under `method_to_url` which maps a JSONRPC method name to a the URL to use. This allows the devops running the JSONRPC nodes to say which nodes support which methods specifically, which is easier than knowing which symbolic name uses which methods. It also means we don't need separate variant specific symbolic names since the variants will be able to use their own method names in this new format for the config.	6 years ago
Luke Imhoff	d946b0d073	EthereumJSONRPC.Variant behaviour ... Define which callbacks and the types needed for each variant of the JSONRPC, so it is easier to add support for new variants in the future.	6 years ago
Luke Imhoff	7d8d09a370	Show HTTP status code when Jason decode fails	6 years ago
Luke Imhoff	e44a617a55	Rechunk batch JSONRPC request when 413 is returned ... When status 413 Request Entity Too Large is returned from JSONRPC, we can split the batch in half and try again. Continuing to break up the chunks of the batch until we suceed or hit 1 request in the chunk, in which case we still need to error.	7 years ago
Luke Imhoff	c7a80fb75b	Convert eth_getBalance error responses to error tuple	7 years ago
Luke Imhoff	0680973e64	fetched_balance_block_number instead of fetched_balance_at ... Fixes #243 Instead of getting the address balance at the latest block and recording the timestamp of the insert, which is only loosely correlated with even the latest block's timestamp on-chain, use the block number for the last time an address was used in the indexed address foreign keys in the chain: * blocks * miner_hash * internal_transactions * created_contract_address_hash * from_address_hash * to_address_hash * logs * address_hash * transactions * from_address_hash * to_address_hash To gather `fetched_balance_block_number` on reboot, `Explorer.Chain.stream_unfetched_addresses` queries across the above columns for the `MAX(blocks.number)`, which is used in `Explorer.Indexer.AddressBalanceFetcher.init/2`. During indexing, `Explorer.Indexer.AddressBalanceFetcher.async_fetch_balances/1` now requires a list of `%{block_number: Block.block_number(), hash: Hash.Truncated.t()}` instead of list of `Hash.Truncated.t()`. Having a `block_number` available for all importable entities's addresses required changing `Explorer.Indexer.AddressExtraction` to extract the `block_number` too. The use of `insert` in the factories was making tests that show the count not make sense, so the factories were switched to `build` because it means only the exact count is created when a default value is overridden. This does, unfortunately, mean that `params_for(factory)` no longer generates foreign keys and they must be set explicitly OR the association passed instead of the foreign key. Allow nil extracted fetched_balance_block_number when pending transaction *NOTE*: This is a database drop and reindex change.	7 years ago
Luke Imhoff	394df24ea2	Use EthereumJSONRPC.request in EthereumJSONRPC.Parity	7 years ago
Luke Imhoff	308c899379	Index from latest to genesis ... Reverse the genesis index order as most users will care about recent blocks as opposed to the very beginning of the chain. This should shorten the Time-to-Usefulness.	7 years ago
Luke Imhoff	805afcd536	Start realtime index immediately from latest block on boot.	7 years ago
Luke Imhoff	a025091af1	Extract common request code	7 years ago
Luke Imhoff	d2c1dc3696	Remove unused eth_*Filter functions	7 years ago
Luke Imhoff	240be361b8	handle_get_block_by_number -> handle_get_block ... `handle_get_block_by_number` handles the result from both `fetch_blocks_by_number` AND `fetch_blocks_by_number`, so it isn't handling just the `_by_number` result and is a misnomer.	7 years ago
Luke Imhoff	11bcecad96	Explorer.JSONRPC -> EthereumJSONRPC ... Extract Explorer.JSONRPC to its own OTP application, apps/ethereum_jsonrpc. It is not ready to be a completely separate library because it knowns the internal params format used for Explorer.Chain.	7 years ago
Luke Imhoff	75388c8ece	cd apps; mix new ethereum_jsonrpc	7 years ago