eth-monitor

Monitor and cache ethereum transactions with match filters
git clone git://git.defalsify.org/eth-monitor.git
Info | Log | Files | Refs | README | LICENSE

eth-monitor-import.head.groff (1254B)


      1 .TH eth-monitor-import	1
      2 
      3 
      4 .SH NAME
      5 eth-monitor-import \- Import transaction data from an indexing service
      6 
      7 
      8 .SH SYNOPSIS
      9 .SY eth-monitor-import
     10 [ -i \fIchain_spec\fP] [ --api-key-file \fIfile\fp ] [ --address-file \fIfile\fP ] [ -a \fIaddress\fP ... ] [ --cache-dir \fIdirectory\fP ] \fIservice\fP
     11 
     12 
     13 .SH DESCRIPTION
     14 Use an indexing service to retrieve transaction hashes for one or more addresses. Supported services may be listed using the \fB--list-services\fP option.
     15 .P
     16 Which addresses to retrieve data for may be defined by the \fB-a\fP \fIaddress\fP option. Alternatively, the \fB--address-file\fP \fIfile\fP option may be used, where addresses are supplied from the given file as a comma-separated list. The address matching mechanism used in transaction processing is the same as for \fBeth-monitor(1)\fP.
     17 .P
     18 Only block and transaction hashes are used from the indexing service. The RPC endpoint will be used to retrieve the block and transaction data.
     19 .P
     20 If \fB--cache-dir\fP \fIdirectory\fP is defined, data will be cached to the given path using the same caching filter as \fBeth-monitor(1)\fP. \fB--store-tx-data\fP and \fB--store-block-data-\fP define whether also transaction and block data is stored to cache, respectively.
     21 
     22 
     23 .SS OPTIONS