Logs
The Event Log API was designed to provide an alternative to the native eth_getLogs.
Below are the list of supported filter parameters:
fromBlock, toBlock, address
topic0, topic1, topic2, topic3 (32 Bytes per topic)
topic0_1_opr (and|or between topic0 & topic1), topic1_2_opr (and|or between topic1 & topic2), topic2_3_opr (and|or between topic2 & topic3), topic0_2_opr (and|or between topic0 & topic2), topic0_3_opr (and|or between topic0 & topic3), topic1_3_opr (and|or between topic1 & topic3)
FromBlock & ToBlock accepts the blocknumber (integer, NOT hex) or 'latest' (earliest & pending is NOT supported yet)
Topic Operator (opr) choices are either 'and' or 'or' and are restricted to the above choices only
FromBlock & ToBlock parameters are required
An address and/or topic(X) parameters are required, when multiple topic(X) parameters are used the topicX_X_opr (and|or operator) is also required
For performance & security considerations, only the first 1000 results are return. So please narrow down the filter parameters.
Sample Log API Queries
Get Event Logs from block number 13270812 to 13387434, where log address = 0x185aef1094ac9df11e4971ed844315ef9129c0d5 and topic[0] = 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
Get Event Logs from block number 13323069 to block 13387473, where log address = 0x8d4cbe791112da3fce6feaf67cae4a05e6097cdf, topic[0] = 0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925 'AND' topic[1] = 0x00000000000000000000000017c261b0b4f01fea9d4f39c1c48875f2299a47a8
Last updated