# IBC Rate Limiting v2.1 - Upgrade contract

**URL:** <https://forum.osmosis.zone/t/ibc-rate-limiting-v2-1-upgrade-contract/3422>\
**Category:** DApps / Tooling\
**Tags:** passed\
**Created:** [January 13, 2025, 10:34am UTC](https://forum.osmosis.zone/t/ibc-rate-limiting-v2-1-upgrade-contract/3422 "2025-01-13T10:34:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnnyWyles](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/johnnywyles/32/3114_2.png) [@JohnnyWyles](https://forum.osmosis.zone/u/JohnnyWyles)\
**Post date:** [January 13, 2025, 10:34am UTC](https://forum.osmosis.zone/t/ibc-rate-limiting-v2-1-upgrade-contract/3422/1 "2025-01-13T10:34:24Z")

</div>

This proposal implements an update to the IBC Rate Limit contract administered by Osmosis governance.

# IBC Rate Limits

The IBC Rate Limit module is a safety control implemented in [v13](https://daodao.zone/dao/osmosis/proposals/370), intended to protect assets on Osmosis in the event of security issues with:

- Osmosis
- A counter-party chain
- IBC

Rate limits allow only a specified net percentage change in the quantity of an asset on Osmosis within a specified period.

Slowing down the rate of security incidents allows validators more time to respond, investigate, and take any required action. It either caps the rate at which exploited tokens generated elsewhere can be sent to Osmosis for disposal or prevents unusually high amounts of tokens on Osmosis from being removed.

This upgrade to the IBC Rate Limit contract adds additional checks to the existing contract while maintaining all previous functionality and states.

**Target Onchain Date** : 16th January 2025

---

<div class="post-metadata">

**Author:** ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)\
**Post date:** [January 13, 2025, 8:00pm UTC](https://forum.osmosis.zone/t/ibc-rate-limiting-v2-1-upgrade-contract/3422/2 "2025-01-13T20:00:38Z")

</div>

Go for it.

IBC limits are good to have in general in case of emergency. Do we still have graphs in place how often the caps are hit (if it has hit at all)?

---

<div class="post-metadata">

**Author:** ![JohnnyWyles](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/johnnywyles/32/3114_2.png) [@JohnnyWyles](https://forum.osmosis.zone/u/JohnnyWyles)\
**Post date:** [January 14, 2025, 11:13am UTC](https://forum.osmosis.zone/t/ibc-rate-limiting-v2-1-upgrade-contract/3422/3 "2025-01-14T11:13:53Z")

</div>

> **[IBC Rate Limits](https://ibc.range.org/ibc/rate-limits)**
>
> The IBC Rate Limits community dashboard tracks the status of IBC net inflows and their safety daily and weekly quotas.

and

> **[IBC Rate Limits](https://ibc.range.org/ibc/workbench)**
>
> The IBC Rate Limits community dashboard tracks the status of IBC net inflows and their safety daily and weekly quotas.

Maybe what you’re after

There are also alerts set up for rate limits being hit that the IBC rate limit subDAO uses to trigger a reset. So far, there have only been a couple of times when the rate limits have been hit despite the tightening of these limits. These haven’t been overridden since the time frame for the rates resetting automatically was imminent in all cases.