> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# eth_newFilter | Fantom
> Fantom API method that generates a filter object based on the filter parameters. Available on Fantom via Chainstack JSON-RPC nodes.
Fantom API method that generates a filter object based on the filter parameters. It returns a filter ID, which can be used to retrieve the filter results using the [eth\_getFilterChanges](/reference/fantom-getfilterchanges) method. By creating a filter for specific events, developers can receive notifications when those events occur and use them to trigger actions in their applications.
**Get your own node endpoint today**
[Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.
You can sign up with your GitHub, X, Google, or Microsoft account.
## Parameters
* `object` — the filter parameters:
* `fromBlock` — (optional, default: `latest`) integer that specifies the starting block number from which the logs should be fetched.
* `toBlock` — (optional, default: `latest`) integer that specifies the ending block number until which the logs should be fetched.
* `address` — (optional) the contract address from which the logs should be fetched. It can be a single address or an array of addresses.
* `topics` — (optional) an array of `DATA` topics. The event topics for which the logs should be fetched. It can be a single topic or an array of topics.
* `blockhash` — (optional) the hash of the specific block. Limits logs to a specific block with a 32-byte hash value. It takes precedence over `fromBlock` and `toBlock`.
**Possible tags forfromBlockandtoBlock**
* `latest` — the most recent block in the blockchain and the current state of the blockchain at the most recent block.
* `safe` — the block that received justification from the beacon chain. Although this block could be involved in a chain reorganization, it would necessitate either a coordinated attack by the majority of validators or an instance of severe propagation latency.
* `finalized` — the block accepted as canonical by more than 2/3 of the validators. A chain reorganization is extremely unlikely, and it would require at least 1/3 of the staked ETH to be burned.
* `earliest` — the earliest available or genesis block.
* `pending` — the pending state and transactions block. The current state of transactions that have been broadcast to the network but have not yet been included in a block.
See the [default block parameter](https://ethereum.org/en/developers/docs/apis/json-rpc/#default-block) and [How The Merge Impacts Ethereum’s Application Layer](https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer).
## Response
* `result` — a hexadecimal string representing the ID of the newly created filter
The filters created are stored on the blockchain client instance. The filter is automatically deleted if not polled within a certain time (5 minutes by default).
Use the following methods with the filter ID:
* [eth\_getFilterChanges](/reference/fantom-getfilterchanges) to retrieve updated logs
* [eth\_uninstallFilter](/reference/fantom-uninstallfilter) to remove the filter
## `eth_newFilter` code examples
Note that the `web3.eth.filter` methods have been deprecated and replaced with the `web3.eth.subscribe` in web3.js. See [web3.js subscriptions](/reference/ethereum-web3js-subscriptions-methods).
```javascript ethers.js theme={"system"}
const ethers = require('ethers');
const NODE_URL = "CHAINSTACK_NODE_URL";
const provider = new ethers.JsonRpcProvider(NODE_URL);
const filter = {
toBlock: 'latest',
address: '0x21be370D5312f44cB42ce377BC9b8a0cEF1A4C83',
topics: ['0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef']
};
const createFilter = async () => {
try {
const filterId = await provider.send('eth_newFilter', [filter]);
console.log(filterId); // the filter ID returned by eth_newFilter
return filterId
} catch (error) {
console.log(error);
}
};
createFilter();
```
```python web3.py theme={"system"}
from web3 import Web3
node_url = "CHAINSTACK_NODE_URL"
web3 = Web3(Web3.HTTPProvider(node_url))
filter = {
'toBlock': 'latest',
'address': '0x21be370D5312f44cB42ce377BC9b8a0cEF1A4C83',
'topics': ['0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef']
}
def create_logs_filter(filter_object):
try:
logs_filter = web3.eth.filter(filter_object)
return logs_filter
except Exception as e:
print(e)
logs_filter = create_logs_filter(filter)
filter_id = logs_filter.filter_id
print(f'New filter ID: {filter_id}')
```
## Use case
You can use `eth_newFilter` to create a filter for a specific action on a smart contract, for example, to monitor the transfer transactions from the [Wrapped BNB token](https://bscscan.com/token/0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c).
The idea is to create a filter using the `eth_newFilter` method to monitor an ERC-20 smart contract, WBNB in this case.
## OpenAPI
````yaml /openapi/fantom_node_api/eth_newFilter.json POST /4ab982aa70a7baead515ffdb5915df3f
openapi: 3.0.0
info:
title: Fantom Node API
version: 1.0.0
description: This is an API for interacting with a Fantom node.
servers:
- url: https://fantom-mainnet.core.chainstack.com
security: []
paths:
/4ab982aa70a7baead515ffdb5915df3f:
post:
tags:
- logs
summary: eth_newFilter
operationId: newFilter
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
method:
type: string
default: eth_newFilter
params:
type: array
items:
type: object
properties:
fromBlock:
type: string
title: from block
description: >-
The block number or tag to start searching for logs
from.
default: latest
address:
type: string
title: smart contract address
description: The contract address to retrieve the logs for.
topics:
type: array
title: topics
items:
type: string
description: >-
An array of 32-byte topics to filter for. Each topic
is treated as an OR condition.
default:
- fromBlock: latest
address: '0x21be370D5312f44cB42ce377BC9b8a0cEF1A4C83'
topics:
- >-
0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
id:
type: integer
default: 1
jsonrpc:
type: string
default: '2.0'
responses:
'200':
description: The filter ID.
content:
application/json:
schema:
type: object
properties:
jsonrpc:
type: string
id:
type: integer
result:
type: string
````