forked from LayerZero-Labs/devtools
-
Notifications
You must be signed in to change notification settings - Fork 1
[Feature] L2 inbound rate limiting #4
Copy link
Copy link
Open
Description
This feature:
(NICE TO HAVE)
Mvmt Labs can set a (total token) volume rate limit on the L2 contract that rejects DVN's completion of transfers on L2. The rate limit on L2 is equal or higher than the rate limit on L1. The rate limit is such that the L2MOVE pool does not get depleted. (this requires diligent human observation of remaining pool balance).
is one that has been discussed on Slack but not formally decided upon.
I tend to think that monitoring the L2 MOVE and topping it up as needed should suffice to ensure that the L2 MOVE pool does not get depleted.
- Decide whether or not to implement this feature
- Implement whatever is decided
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels