Get harmony logs for smart contracts or transactions

Parameters

1. Object - The filter options:

2. fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

3. toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

4. address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.

5. topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

6. blockhash: DATA, 32 Bytes - (optional) , blockHash is a new filter option which restricts the logs returned to the single block with the 32-byte hash blockHash. Using blockHash is equivalent to fromBlock = toBlock = the block number with hash blockHash. If blockHash is present in the filter criteria, then neither fromBlock nor toBlock are allowed.

Returns

For filters created with hmy_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

For filters created with hmy_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

For filters created with hmy_newFilter logs are objects with following params:

• removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.

• logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.

• transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.

• transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.

• blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

• blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.

• address: DATA, 20 Bytes - address from which this log originated.

• data: DATA - contains the non-indexed arguments of the log.

• topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

Sample Curl Request

Sample Curl Response

Creates a filter object, based on filter options, to notify when the state changes (logs). To check if the state has changed, call hmy_getFilterChanges

A note on specifying topic filters:

Topics are order-dependent. A transaction with a log with topics [A, B] will be matched by the following topic filters:

• [] "anything"

• [A] "A in first position (and anything after)"

• [null, B] "anything in first position AND B in second position (and anything after)"

• [A, B] "A in first position AND B in second position (and anything after)"

• [[A, B], [A, B]] "(A OR B) in first position AND (A OR B) in second position (and anything after)"

Parameters

1. Object - The filter options:

2. fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

3. toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

4. address: DATA|Array, 20 Bytes - (optional) Contract address or a list of addresses from which logs should originate.

5. topics: Array of DATA, - (optional) Array of 32 Bytes DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.

Example Parameters

params: [{
  "fromBlock": "0x1",
  "toBlock": "0x2",
  "address": "0x8888f1f195afa192cfee860698584c030f4c9db1",
  "topics": ["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b", null, ["0x000000000000000000000000a94f5374fce5edbc8e2a8697c15331677e6ebf0b", "0x0000000000000000000000000aff3454fce5edbc8cca8697c15331677e6ebccc"]]
}]

Returns

QUANTITY - A filter id.

Example

// Request
curl -d '{"jsonrpc":"2.0","method":"hmy_newFilter","params":[{"topics":["0x0000000000000000000000000000000000000000000000000000000012341234"]}],"id":73}' -H "Content-Type:application/json" -X POST "https://api.s0.b.hmny.io"

// Result
{
  "id":1,
  "jsonrpc": "2.0",
  "result": "0x1" // 1
}

Parameters

None

Returns

QUANTITY - A filter id.

Example

// Request
curl -d '{"jsonrpc":"2.0","method":"eth_newBlockFilter","params":[],"id":73}' -H "Content-Type:application/json" -X POST "https://api.s0.b.hmny.io"

// Result
{
  "id":1,
  "jsonrpc":  "2.0",
  "result": "0x1" // 1
} 

Parameters

None

Returns

QUANTITY - A filter id.

Example

// Request
curl -d '{"jsonrpc":"2.0","method":"eth_newPendingTransactionFilter","params":[],"id":73}' -H "Content-Type:application/json" -X POST "https://api.s0.b.hmny.io"

// Result
{
  "id":1,
  "jsonrpc":  "2.0",
  "result": "0x1" // 1
}

Returns an array of all logs matching filter with given id.

Parameters

1. QUANTITY - The filter id.

Example Parameters

params: [
  "0x16" // 22
]

Returns

See hmy_getFilterChanges

Example

// Request
curl -d '{"jsonrpc":"2.0","method":"hmy_getFilterLogs","params":["0x16"],"id":74}' -H "Content-Type:application/json" -X POST "https://api.s0.b.hmny.io"

Result see hmy_getFilterChanges

Parameters

1. QUANTITY - the filter id.

Returns

Array - Array of log objects, or an empty array if nothing has changed since last poll.

• For filters created with eth_newBlockFilter the return are block hashes (DATA, 32 Bytes), e.g. ["0x3454645634534..."].

• For filters created with eth_newPendingTransactionFilter the return are transaction hashes (DATA, 32 Bytes), e.g. ["0x6345343454645..."].

• For filters created with eth_newFilter logs are objects with following params:

  • removed: TAG - true when the log was removed, due to a chain reorganization. false if its a valid log.

  • logIndex: QUANTITY - integer of the log index position in the block. null when its pending log.

  • transactionIndex: QUANTITY - integer of the transactions index position log was created from. null when its pending log.

  • transactionHash: DATA, 32 Bytes - hash of the transactions this log was created from. null when its pending log.

  • blockHash: DATA, 32 Bytes - hash of the block where this log was in. null when its pending. null when its pending log.

  • blockNumber: QUANTITY - the block number where this log was in. null when its pending. null when its pending log.

  • address: DATA, 20 Bytes - address from which this log originated.

  • data: DATA - contains the non-indexed arguments of the log.

  • topics: Array of DATA - Array of 0 to 4 32 Bytes DATA of indexed log arguments. (In solidity: The first topic is the hash of the signature of the event (e.g. Deposit(address,bytes32,uint256)), except you declared the event with the anonymous specifier.)

Sample Curl Request

curl -d
'{
   "jsonrpc":"2.0",
   "method":"hmy_getFilterChanges",
   "params":["0x16"],
   "id":73
}' -H "Content-Type:application/json" -X POST "https://api.s0.b.hmny.io"

Sample Curl Response

{
  "id":1,
  "jsonrpc":"2.0",
  "result": [{
    "logIndex": "0x1", // 1
    "blockNumber":"0x1b4", // 436
    "blockHash": "0x8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "transactionHash":  "0xdf829c5a142f1fccd7d8216c5785ac562ff41e2dcfdf5785ac562ff41e2dcf",
    "transactionIndex": "0x0", // 0
    "address": "0x16c5785ac562ff41e2dcfdf829c5a142f1fccd7d",
    "data":"0x0000000000000000000000000000000000000000000000000000000000000000",
    "topics": ["0x59ebeb90bc63057b6515673c3ecf9438e5058bca0f92585014eced636878c9a5"]
    },{
      ...
    }]
}