Skip to content

MIP-126: Non-Offsettable Gross Inflow Rate Limiting for the bridge - #126

Closed
apenzk wants to merge 4 commits into
mainfrom
mip/bridge-change
Closed

MIP-126: Non-Offsettable Gross Inflow Rate Limiting for the bridge#126
apenzk wants to merge 4 commits into
mainfrom
mip/bridge-change

Conversation

@apenzk

@apenzk apenzk commented Dec 12, 2025

Copy link
Copy Markdown
Contributor

Non-Offsettable Gross Inflow Rate Limiting for the Bridge

The proposal replaces net-flow–based bridge rate limiting with a strict gross inflow cap on Movement. Outflows do not release inflow capacity, preventing the effective inflow limit from exceeding its configured value.

Summary

  • Abandons net-flow / bidirectional offsetting semantics
  • Enforces a consume-only rate limiter on Movement
  • Outflows cannot increase inflow capacity
  • Capacity replenishes only via daily reset
  • Enforces a hard gross inflow ceiling

Possible scenarios

  • Baseline: Bidirectional offsetting across chains (net-flow accounting)
  • Alt 1: Movement-centric but still offsetting (rejected)
  • Alt 2 (proposed): Movement-centric, no releases, strict gross inflow cap

@apenzk apenzk changed the title Mip/bridge change MIP-126: bridge change Dec 16, 2025
@apenzk apenzk changed the title MIP-126: bridge change MIP-126: Non-Offsettable Gross Inflow Rate Limiting for the bridge Dec 16, 2025
@apenzk apenzk closed this May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant