MoonRunners
LogoLogo

80

  1. /
  2. Initia
  3. /
  4. Mainnet
  5. /
  6. Governance
  7. /
  8. 80
  • Docs
  • Support
2026 © Made with 💜 by MoonRunnersAPI OK
DocsSupportDonate

Proposal #80

Add IBC Rate Limit for USDC (channel-3)

PassedAdd Rate Limit

Passed on 05 May 2026 with 0.0% of the votes for yes.

Yes

0.0%

0.0% without abstain

Veto

0.0%

of votes cast

Ended

05 May 2026

The ballotvotes cast · final tally
Yes

0.00%

of votes cast

Abstain

0.00%

of votes cast

No

0.00%

of votes cast

Veto

0.00%

of votes cast

1. TL;DR

This proposal adds an IBC rate limit on channel-3 (Initia ↔ Noble) for USDC, capping both inflows and outflows at 20% of the total supply per hour.

2. Proposal Details

IBC rate limiting is a security mechanism that restricts the amount of tokens that can flow in or out through a given IBC channel within a defined time window. This acts as a circuit breaker, limiting the impact of potential exploits or abnormal fund movements.

Rate Limit Parameters

ParameterValue
Channelchannel-3
Denomibc/6490A7EAB61059BFC1CDDEB05917DD70BDF3A611654162A1A47DB930D40D8AF4
Max Send (outflow)20% per hour
Max Recv (inflow)20% per hour
Duration1 hour

Rationale

By enforcing a 20% hourly rate limit on both send and receive directions for channel-3, this proposal provides the following protections:

  • Exploit mitigation: In the event of a smart contract exploit or oracle manipulation, the rate limit prevents mass drainage of funds within a short period.
  • Early warning: A triggered rate limit signals anomalous activity, giving the team and community time to respond before further damage occurs.
  • Symmetrical protection: Applying the same threshold to both inflows and outflows ensures balanced protection against both deposit and withdrawal attacks.

Technical Implementation

This proposal executes a MsgAddRateLimit via the ratelimit.v1 module (ref: [Hidden link]).

Note: Uses channel_id field as defined in the v8 proto ([Hidden link]), which is the version integrated in Initia. The newer v10 renamed this field to channel_or_client_id.

{
  "messages": [
    {
      "@type": "/ratelimit.v1.MsgAddRateLimit",
      "authority": "init10d07y265gmmuvt4z0w9aw880jnsr700j55nka3",
      "denom": "ibc/6490A7EAB61059BFC1CDDEB05917DD70BDF3A611654162A1A47DB930D40D8AF4",
      "channel_id": "channel-3",
      "max_percent_send": "20",
      "max_percent_recv": "20",
      "duration_hours": 1
    }
  ]
}

3. Timelines

  1. April 27, 2026 - Forum Proposal posted
  2. April 28, 2026 - Onchain Vote begins (7-day voting period)
  3. May 5, 2026 - Onchain Vote ends — proposal is executed or rejected

4. Governance Votes

  • YES — You support adding a 20%/hour IBC rate limit on channel-3 to protect against abnormal fund flows.
  • NO — You do not support adding this rate limit on channel-3.
  • NO WITH VETO — You believe this proposal is harmful, spam, or violates governance principles.
  • ABSTAIN — You choose not to vote for or against but wish your vote to count toward quorum.

Timeline

  1. Submitted28 Apr 2026
  2. Voting started28 Apr 2026
  3. Voting ended05 May 2026
  4. Deposit deadline29 Apr 2026

Proposer

Address
init1dsn…7qwg37
Deposit10.0K

Rules

Not recorded for this proposal.