IBC rate limits for channel-40 (Injective) incl. canonical USDC
BitBadges proposal #46: Adds 5 ibcratelimit configs covering channel-40 (Injective), which currently has NO rate limits: ubadge, canonical USDC (ibc/E1116484...
Yes
100%
No
0%
Abstain
0%
Veto
0%
Original Proposal Text
Adds 5 ibcratelimit configs covering channel-40 (Injective), which currently has NO rate limits: ubadge, canonical USDC (ibc/E1116484..., native Circle USDC via transfer/channel-40/erc20:0xa00C59fF5a080D2b954d0c75e46E22a0c371235a), legacy Noble USDC.n, ATOM, and OSMO. Uses MsgUpdateRateLimit (per-config upsert: matches on channel_id+denom, appends if absent), so the 12 existing live configs on channels 0/2/3 are untouched. Quotas exactly mirror the live per-denom-class philosophy: ubadge uses the native-denom amounts and all four IBC denoms (canonical USDC included) use the uniform foreign-class amounts (10M tokens/hour and 30M/day supply shift; 1M/hour and 10M/day per address; unique-sender limits 10000/hour and 500/block identical to all existing configs).