DisclaimerNote that the default interactive example in this page will not work as the filter will be expired.To test
eth_uninstallFilter
in this page, first create a new filter using one of the following:Then use the fresh filter ID as the parameter for eth_uninstallFilter
.Get you own node endpoint todayStart for free 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
string
— the filter ID that you want to uninstall
Response
boolean
— a boolean value indicating whether the filter was successfully uninstalled.true
if successfully removed, andfalse
if not.
eth_uninstallFilter
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.Use case
One use case foreth_uninstallFilter
is to optimize resource usage in a DApp. When a DApp needs to monitor events on the blockchain, it can create a filter using eth_newFilter,eth_newPendingTransactionFilter, or eth_newBlockFilter to listen for specific events or blocks.
However, once the DApp no longer needs to monitor these events or blocks, it can use eth_uninstallFilter
to stop watching for them. By doing so, the DApp can reduce the number of active filters and free up resources, such as network bandwidth and computational power, that would otherwise be used to maintain the filter.
For example, let’s say that a DApp is monitoring incoming blocks, logs batches of 50 blocks, and then uses uninstallFilter
to remove the filter.Body
application/json
Response
200 - application/json
Boolean value indicating if the filter was removed or not.
The response is of type object
.