# (feat) implement decay-based rate limiting in AsyncRequestContext #7481

- Space: [Pull Request Proposals](https://snapshot.box/s:hbot-prp.eth.md)
- Author: 0x552d8A7856e71852E7190e11cD0bdaa28E3eD968
- State: Rejected
- Voting type: Basic
- Start: 2025-03-05 14:51 UTC
- End: 2025-03-12 14:51 UTC
- Votes: 1
- Quorum: 409,101 voting power
- Open in Snapshot: https://snapshot.box/#/s:hbot-prp.eth/proposal/0xaf1b812ed7964645cd24f90eb9c8fa0545eb341a05eef2439626e796719b7cbb

## Results

- For: 100 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

## Summary

This PR adds support for decay-based rate limits in the AsyncThrottler, addressing issue https://github.com/hummingbot/hummingbot/issues/4163. These limits differ from fixed window limits as they continuously recover capacity over time instead of resetting at fixed intervals.

Key design principle: Added this functionality without breaking existing code. Backward compatible with zero changes needed for existing connectors for easy and fast integration.

## Rationale

Exchanges like Kraken and Coinbase Pro use decay-based rate limiting rather than traditional fixed windows. Adding this functionality allows connectors to more accurately model these API behaviors and optimize request throughput.

## Github Link

https://github.com/hummingbot/hummingbot/pull/7481

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

