# Sushi RouteProcessor2 Post-Exploit Request For Comment

**URL:** <https://research.lido.fi/t/sushi-routeprocessor2-post-exploit-request-for-comment/4383>\
**Category:** Proposals\
**Created:** [April 12, 2023, 1:55pm UTC](https://research.lido.fi/t/sushi-routeprocessor2-post-exploit-request-for-comment/4383 "2023-04-12T13:55:29Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Misha\_Statemind](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/misha_statemind/32/2741_2.png) [@Misha\_Statemind](https://research.lido.fi/u/Misha_Statemind)\
**Post date:** [April 13, 2023, 1:47pm UTC](https://research.lido.fi/t/sushi-routeprocessor2-post-exploit-request-for-comment/4383/5 "2023-04-13T13:47:39Z")

</div>

On surface level proposal makes sense, however, if passed, it might set a dangerous precedent as there is no framework to govern this activity, yet, we all know, that cases like this are plentiful. Without a proper research ramifications to the protocol are simply unknowable. I see several possible risks here:

1. Without a clear framework Lido DAO can be heavily throttled by inflow of hack reimbursement proposals.
2. In case of reimbursement DAO needs to be an arbitrary judge of what is legal/illegals activity for other protocols which is way beyond it’s usual capacity and might bring an unpredictable legal risks.
3. What about other MEV manipulations and their status?

---

_[View the full topic](https://research.lido.fi/t/sushi-routeprocessor2-post-exploit-request-for-comment/4383)._
