331 Commits (1435347ea6d96e4cb946de5b79c7a56cdc56bb2c)

Author	SHA1	Message	Date
Amanda Sposito	95de1ebcb0	Add token details page backend	6 years ago
Alex Garibay	8b16f81b73	Catalog token transfers and tokens during indexing (#484) ... * Fetch token information asynchronously during indexing * Include token transfers imports in main importer * Extract token transfers when importing blocks while indexing * Move ecto to explorer deps * Update References to the Indexer namespace * Add token insertions with main importer * Import token address/type during block indexing	6 years ago
Stamates	b941b6b927	Rename function	6 years ago
Stamates	8e8d23fb57	Fix flaky hashes_to_transactions tests (non-ordered results)	6 years ago
Stamates	f75eee5e61	Refactor import test	6 years ago
Stamates	d7fd7d27fb	Update etherscan context transactions list to use created_contract_address_hash from transaction	6 years ago
Tim Mecklem	5a54caecb7	Use union for address fields match to improve slow token_transfers join ... Co-authored-by: stamates <stamates@hotmail.com>	6 years ago
Stamates	7b82a3442d	Added test that contract_creadted_address_hash is nil if to_address is not nil	6 years ago
Tim Mecklem	ab0ca21dac	Update indexer to set created_contract_address_hash on transaction ... Co-authored-by: stamates <stamates@hotmail.com>	6 years ago
Tim Mecklem	6a7381b296	Add `created_contract_address_hash` to transactions and update queries	6 years ago
Luke Imhoff	f2884992a7	Fetch realtime internal transactions and balances synchronously ... Fixes #366 Queuing the internal transactions and balances to be fetched asynchronously for realtime blocks lead to upto 15 minute delay between when a block appeared and the internal transaction was drained from the queue. It is a better user experience to not see the realtime blocks at all than to see them incomplete, so fetch the internal transactions and then the balances before importing the whole tree of data instead of using the catchup asynchronous queues.	6 years ago
Luke Imhoff	12f70945da	Switch Chain.import options to maps ... 1. Allows for easier composing with put_in than Keyword.t 2. Allows more precise specs as individal options can be marked as optional or required while the Keyword.t pattern makes it seem like everything is optional.	6 years ago
Felipe Renan	b6a4e48414	Add Token's reference to Token Transfers	6 years ago
Felipe Renan	64f289fcf1	Fix Token Transfer factory	6 years ago
Felipe Renan	09cd139341	Move where_address_fields_match/2 to Transaction Schema	6 years ago
Felipe Renan	7c2255f7fc	Show token transfers on transactions' tab from Address' page. ... Resolves https://github.com/poanetwork/poa-explorer/issues/75	6 years ago
Luke Imhoff	a28b06f788	Use _map suffix to clarify type with _list as value	6 years ago
Luke Imhoff	2f3af51741	Unified Explorer.Chain.import ... * Merge `Explorer.Chain.import_blocks` and `Explorer.Chain.import_internal_transactions` into `Explorer.Chain.import`. * Move body of `Explorer.Chain.import` and its private helper functions to `Explorer.Chain.Import` as an independent context that `Explorer.Chain` can use. `Explorer.Chain.Import` must be under `Explorer.Chain` because `Explorer.Chain.Import` still needs direct access to the `Explorer.Chain` schemas.	6 years ago
Luke Imhoff	c4133c1fb0	Validate Transacton from_address_hash as required ... It was marked null: false, but an optional parameter in Transaction.changeset, so could trigger a database not-null constraint violation.	6 years ago
Luke Imhoff	b96891ced2	Move import functions into Explorer.Chain.Import ... Context needs to stay under `Explorer.Chain` because `Explorer.Chain.*` schemas, which only respects the `Explorer.Chain` API boundard when `Import` stays below `Explorer.Chain`.	6 years ago
Stamates	078f1e6955	Move transaction_hashes to transactions fetching to single query ... Co-authored-by: jimmay5469 <jimmay5469@gmail.com>	6 years ago
jimmay5469	e5e695331f	Subscribe to only realtime-indexer events for channel broadcasts	6 years ago
Peter Romfeld	d9e37c44a6	fix formatting	6 years ago
Peter Romfeld	b473420df3	use ETHEREUM_JSONRPC_HTTP_URL instead	6 years ago
Peter Romfeld	2ddc1b9747	get geth_url from environment and fix `variant` for {dev,prod}.exs	6 years ago
Luke Imhoff	52196bf329	Clean setup and shutdown of Explorer.Chain.Statistics.Server ... Fixes #466	6 years ago
Luke Imhoff	e71781cde8	Increase pool_timeout for tests ... test/indexer/block_fetcher_test.exs:50 was flaky and sometimes fail due to errors like ``` [error] Realtime index stream exited with reason ({:timeout, {GenServer, :call, [#PID<0.596.0>, {:checkout, #Reference<0.851308976.2388656130.16563>, true, 120000}, 5000]}}) ```	6 years ago
Luke Imhoff	e3f7581572	Historical Address Balances	6 years ago
Sebastian Abondano	86de475385	Add optional params to account txlist API endpoint ... Why: * For users to be able to specify optional params when calling the API RPC account transactions (action=txlist) endpoint. Example usage: ``` /api?module=account&action=txlist \ &address=0xddbd2b932c763ba5b1b7ae3b362eac3e8d40121a \ &startblock=100&endblock=150&page=1&offset=10&sort=asc ``` * Issue link: https://github.com/poanetwork/poa-explorer/issues/138 This change addresses the need by: * Editing `Explorer.Etherscan.list_transactions/2` to support `order_by_direction`, `page_number`, `page_size`, `start_block`, and `end_block` options. * Editing `API.RPC.AddressController` to support 'sort', 'page', 'offset', 'startblock', and 'endblock' params. Mimics Etherscan's API. When the optional params are not provided we return a max of 10,000 transactions, order by block number in ascending order, and target all blocks.	6 years ago
Stamates	9b69c218b3	Add default port setup for postgres in test.example and include optional setup in README. ... Format/cleanup README file. Co-authored-by: jimmay5469 <jimmay5469@gmail.com>	6 years ago
Stamates	51ce0c1123	Code cleanup	6 years ago
Tim Mecklem	2313d8d976	to_address and to_address_hash can be nil ... Co-authored-by: stamates <stamates@hotmail.com>	6 years ago
Tim Mecklem	ee0e726fb4	Return addresses from bulk insert instead of address_hashes ... Co-authored-by: stamates <stamates@hotmail.com>	6 years ago
jimmay5469	4d612d59f0	Setup live updates for address balance	6 years ago
jimmay5469	477e01c993	Extract logic from event_handler to notifier	6 years ago
Tim Mecklem	9ce3f3d9e4	Hook up block confirmations to subscribed indexer update	6 years ago
Tim Mecklem	89c1416b2c	Allow test environment configuration to be overridden similar to dev	6 years ago
Alex Garibay	a49acfea10	Add token transfer schema	6 years ago
Amanda Sposito	dae9ff2f10	Add support to Pluggable Transport and HTTP transport modules	6 years ago
Amanda Sposito	e545841407	Add error treatment to the 'ex_abi' lib	6 years ago
Amanda Sposito	f772e1a56f	Increase db timeout at dev enviroment	6 years ago
Amanda Sposito	01472cb353	Add 'Read Smart Contract' page	6 years ago
Tim Mecklem	7392b84fb1	Restore factory needed by tests	6 years ago
Tim Mecklem	e42a7cfb10	Set up contract verification test with `create` internal transaction ... Co-authored-by: stamates <stamates@hotmail.com>	6 years ago
Amanda Sposito	73856a72df	Add read only functions to 'SmartContract.Reader'	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	e914bf1065	Add the EthereumJSONRPC dependency on Explorer ... Now the Explorer app has the functionality to read a smart contract function call, but the app responsible to interact with the blockchain is EthereumJSONRPC, so the Explorer now depends on EthereumJSONRPC.	6 years ago
Amanda Sposito	2b57b537c7	Add address_hash_to_smart_contract/1 function	6 years ago
Sebastian Abondano	e8a9b63d7b	Add account transactions API RPC endpoint ... Why: * For users to be able to get the transactions for a given address hash. Support for optional parameters will be added in an upcoming PR. * Issue link: https://github.com/poanetwork/poa-explorer/issues/138 This change addresses the need by: * Adding `Explorer.Etherscan` context, where we want to keep etherscan-only logic within the Explorer app. This is because we want to mimic the way their RPC API works. The only function in this module for now is `list_transactions/1`, which gets all transactions for a given address hash. * Adding `txlist/2` action to `API.RPC.AddressController`, to handle account transactions requests. Example usage: ``` api?module=account&action=txlist \ &address=0xddbd2b932c763ba5b1b7ae3b362eac3e8d40121a ``` * Editing `API.RPC.AddressView` and `API.RPC.RPCView` to format responses for new API endpoint as required. * Editing `.credo.exs` to allow for `Hash.Address.t()` alias usage in `Explorer.Etherscan` without Credo complaining with: ``` Software Design ┃ ┃ [D] ↓ Nested modules could be aliased at the top of the invoking module. ┃ apps/explorer/lib/explorer/etherscan.ex:19:51 ```	6 years ago
Sebastian Abondano	cc059dac1e	Enhance API account balance endpoint ... Why: * Currently, the API account balance endpoint allows users to get the ether balance for a single address. This commit introduces support for getting the ether balance for multiple addresses (maximum of 20) in a single batch. * Issue link: https://github.com/poanetwork/poa-explorer/issues/138 This change addresses the need by: * Adding `Chain.hashes_to_addresses/1` to get multiple addresses from the DB, given a list of hashes. * Editing `balance/2` in `API.RPC.AddressController` to support multiple addresses. Previously it only supported a single address. * Editing `API.RPC.AddressView` to handle a single address differently than multiple addresses. This is to mimic Etherscan's API.	6 years ago