[Filter] kaia_newFilter
Creates a filter object, based on filter options, to notify when the state changes (logs).
- To check if the state has changed, call kaia_getFilterChanges.
- To obtain all logs matching the filter created by kaia_newFilter, call kaia_getFilterLogs.
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)"
NOTE: In versions earlier than Kaia v1.7.0, only integer block number, the string "earliest" and "latest" are available.
JSONRPC: kaia_newFilter
Request
- application/json
Body
Array [
- IntegerBlockNumber
- HexadecimalBlockNumber
- BlockTag
- IntegerBlockNumber
- HexadecimalBlockNumber
- BlockTag
- MOD1
- Address
Array [
- Address
]
]
params
object[]
required
fromBlock
object
(optional, default: "latest") Integer or hexadecimal block number, or the string "earliest", "latest" or "pending" as in the default block parameter.
oneOf
the block number with type integer
number
the block number with type hexadecimal
string
the block tag [latest, pending, earliest]
string
toBlock
object
(optional, default: "latest") Integer or hexadecimal block number, or the string "earliest", "latest" or "pending" as in the default block parameter.
oneOf
the block number with type integer
number
the block number with type hexadecimal
string
the block tag [latest, pending, earliest]
string
address
object
(optional) Contract address or a list of addresses from which logs should originate.
oneOf
anyOf
Address
string
Address
string
(optional) Array of 32-byte DATA topics. Topics are order-dependent. Each topic can also be an array of DATA with "or" options.
Responses
- 200
Returns a filter id
- application/json
- Schema
- Example (from schema)
Schema
error
object
A Number that indicates the error type that occurred. This MUST be an integer.
code | message | description |
---|---|---|
-32700 | Parse error | invalid JSON was received by the server. An error occurred on the server while parsing the JSON text. |
-32602 | Invalid params | Invalid method parameter(s). |
A String providing a short description of the error. The message SHOULD be limited to a concise single sentence.
A Primitive or Structured value that contains additional information about the error. This may be omitted. The value of this member is defined by the Server (e.g. detailed error information, nested errors etc.).
A filter id
{
"jsonrpc": "2.0",
"id": 0,
"error": {
"code": -32700,
"message": "Parse error",
"data": "string"
},
"result": "0xd32fd16b6906e67f6e2b65dcf48fc272"
}