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 6972610 to 6972710 Block, where log address = 0x15c34d8b356f21112c07ca1811d84101f480a3f1 and topic[0] = 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
Get Event Logs from block number 28731619 to block 28831619, where log address = 0x11d90ea9d16e1ee5879b299a819f6d618816d70f, topic[0] = 0xd78ad95fa46c994b6551d0da85fc275fe613ce37657fb8d5e3d130840159d822 'AND' topic[1] = 0x000000000000000000000000f491e7b69e4244ad4002bc14e878a34207e38c29
Last updated