IBC Rate Limiting

[nicolaslara]

Background

In the event of a chain exploit on osmosis or another chain connected via IBC, an attacker may want to quickly move the funds off osmosis (or into osmosis in the case of an infinite mint). To mitigate this, IBC channels should have a rate limiting capability so that no more than a pre-established amount can be moved through the channel

Suggested Design

Create a cosmwasm contract that keeps track of the balance moved through the bridge during a period of time and allows or denies IBC messages. Add an IBC middleware that calls the contract and forwards the messages in the case of success or fails when rate limiting.

Acceptance Criteria

• Test for the middleware are comprehensive and pass
• Test for the contract are comprehensive and pass

[hiromaily]

I have a question about why this contract is created by cosmwasm, not basic golang code.

[ValarDragon]

So it can be upgraded without a chain upgrade!

Closing this as IBC rate limiting has gotten into v13