You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm using the Runes Activity endpoint to track all transactions within a block. However, I encounter performance issues due to the high number of activities per block (500-1000 pages). Since the API currently returns all transaction types, I need to manually filter the results on my end, which leads to excessive API calls and rate limiting.
Describe the solution you'd like
I would like to have filtering capabilities added to the Runes Activity endpoint. Specifically, the ability to filter results based on transaction types, such as:
Include only "receive" transactions
Exclude "send" and other transaction types that are not relevant to my use case
Describe alternatives you've considered
Currently, the only alternative is to retrieve all data and manually filter it on the client side, but this is inefficient and quickly reaches API rate limits. While upgrading to a higher API limit may help, built-in filtering would optimize both API usage and performance.
Additional context
I plan to use this functionality to build a Runes bridge between Bitcoin and Starknet. Having a filtering feature would significantly enhance the efficiency of data processing and API usage.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm using the Runes Activity endpoint to track all transactions within a block. However, I encounter performance issues due to the high number of activities per block (500-1000 pages). Since the API currently returns all transaction types, I need to manually filter the results on my end, which leads to excessive API calls and rate limiting.
Describe the solution you'd like
I would like to have filtering capabilities added to the Runes Activity endpoint. Specifically, the ability to filter results based on transaction types, such as:
Include only "receive" transactions
Exclude "send" and other transaction types that are not relevant to my use case
Describe alternatives you've considered
Currently, the only alternative is to retrieve all data and manually filter it on the client side, but this is inefficient and quickly reaches API rate limits. While upgrading to a higher API limit may help, built-in filtering would optimize both API usage and performance.
Additional context
I plan to use this functionality to build a Runes bridge between Bitcoin and Starknet. Having a filtering feature would significantly enhance the efficiency of data processing and API usage.
The text was updated successfully, but these errors were encountered: