Rupto - Documentation
  • Introduction
  • The Concept
    • Tokenization
    • Token Classification
  • Rupto Project
  • RPT Token
  • Rupto Blockchain
    • EVM Compatibility
    • Gas
    • Sharding
  • Rupto Values
  • Utility
  • Ecosystem
  • Developer Resources
  • RuptoChain Network
    • RuptoChain Mainnet
    • RuptoChain Testnet
    • CLI Command
  • Deploying on RuptoChain
    • Using Remix
    • Using Truffle
    • Using Hardhat
    • Using Raplit
    • Using Alchemy
  • API
    • accounts
    • blockNumber
    • call
    • chainId
    • estimateGas
    • gasPrice
    • getBalance
    • getBlockByHash
    • getBlockByNumber
    • getBlockTransactionCountByHash
    • getBlockTransactionCountByNumber
    • getCode
    • getLogs
    • getStorageAt
    • getTransactionByBlockHashAndIndex
    • getTransactionByBlockNumberAndIndex
    • getTransactionByHash
    • getTransactionCount
    • getTransactionReceipt
    • getUncleByBlockHashAndIndex
    • getUncleByBlockNumberAndIndex
    • getUncleCountByBlockHash
    • getUncleCountByBlockNumber
    • getWork
    • hashrate
    • mining
    • protocolVersion
    • sendRawTransaction
    • submitWork
    • syncing
    • net_listening
    • net_peerCount
    • net_version
    • web3_clientVersion
    • parity_nextNonce
    • Filter methods
    • newFilter
    • newBlockFilter
    • getFilterChanges
    • uninstallFilter
  • Conclusion
Powered by GitBook
On this page
  1. API

Filter methods

Rupto supports the following filter methods over both HTTP and WebSocket. In both cases, the filter IDs can be shared by any connection using the same v3 Project ID.

Filters that are not polled using eth_getFilterChanges will be automatically expired after fifteen minutes of inactivity.

Previousparity_nextNonceNextnewFilter

Last updated 2 years ago