EIPs

EIPs copied to clipboard

Limits outflows for all contract assets to a given rate in a given timeframe to limit losses from hacks

When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md

We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:

• The PR edits only existing draft PRs.
• The build passes.
• Your GitHub username or email address is listed in the 'author' header of all affected PRs, inside .
• If matching on email address, the email address is the one publicly listed on your GitHub profile.

Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s):

---

(fail) eip-5075.md

classification
newEIPFile

• File with name EIPS/eip-5075.md is new and new files must be reviewed
• This PR requires review from one of [@lightclient, @axic, @samwilsn, @pandapip1]

Updated license and assigned eip. Was going to at the start but the process specifically says to wait for editor. Ty for the review.

The filename needs updated to EIPs/eip-5075.md.

My bad, saw needed to change just forgot when updating the rest.

@artdgn ah you are right does not strictly rate limit, more an av. The actual limit would be based on the previous 1h and should that be 0 yes approaches 2x for that 1h slot, though to be noted does not apply for following slots so rather than 2x, actually ends up

Net outflow limit for any time t can be seen as ratelimit available time 0 + t * rateLimit not simply t * rateLimit, 2x for cases where the start would be 0 for the previous 1h (no activity last 1h).

So let's say that you have a time window at 100m and a rateLimit at 100 bips (so lets just say theres 1000 tokens and so 100 tokens per 100m)

Time (m) Amount out (up to limit) 000 005 010 020 040 060 080 099 100 105 110 120... 100 005 010 010 020 020 020 014 001 005 005 010... Delta 1h 100+.............................................099 (199 last 1h) .......005+....................................................105 (105)

Amount out last 1h 100 105 115 125 145 165 185 199 100 105 105 110 ...

So realistically ends up as the excess possible being the free rate available at the time 0 for the window. Will update the proposal to say that. Would do mappings for amounts to stamps but the gas costs would be much higher. Though could be an alternate implementation for L2s.

Am on a phone atm so my b that may be hard to understand what was shown.

Need to check to confirm though

Note Making the window and limit small for that window limits available rate at t0. So window 5m, limit 5 may be better, though having a spikey capacity that smoothes and makes the av rate approach target could be useful. (As at worst with a 100 bip, 1h window, would take an attacker 9h to extract vs 10) as t0 would be 1h worth, but they can only do up to the rate limit every 1h after.

Have updated all needed details, detailed the reference implementation considerations, made the way that the limit be handled be a recommendation rather than a set value or way. Tested gas benchmarks aswell (about 12k overhead per transfer vs non rateLimited) updated the params to be more clear. Should be all good now.

@lightclient updated spacing

@pr0toshi, can you please move this EIP up a director and delete the directory EIPS/EIPs.

Bump.

Here's my first pass. I haven't looked at the Specification, Rationale, or Backwards Compatibility sections yet.

Thankyou so much for the thorough run through. Will update the names, was just trying to keep short so that thered be a signal that it's an extension of transfer and to be used as a replacement for the most part, but will look at alternatives such as .send vs. .transfer

The commit 7c7fec6ae66499dbde6ce3d49bb0420e16ff1e69 (as a parent of d2936a3dd379974fb82702dee2183c6bc8a643f2) contains errors. Please inspect the Run Summary for details.

The commit 16cbbfb381af7e92eeb85c3c2022d2cd886b0992 (as a parent of 93dd9baf947681365445599e7f5aafaf9e3cd4e5) contains errors. Please inspect the Run Summary for details.

There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.