Return excess profit from ProtoRev in exchange for 20% bounty

Proposal Discussion
1

Summary

The proposal aims to redress a user who lost 90% of a USDC cross-chain withdrawal from dYdX via Osmosis, by returning a portion of ProtoRev profits while keeping 20% for the Osmosis community as a bounty.

What happened

On August 8, a dYdX user lost 964,482.780794 USDC, comprising over 90% of their equity, due to extremely high slippage when withdrawing from dYdX via Osmosis.

Proposed reimbursement and bounty

The proposal asks that the Osmosis community vote to return 80% of its share of ProtoRev profits (~732,891 USDC) to the user’s address osmo12e0c4wcw72rprzntrvnfk0egn8q9d2tz6zexls. The Osmosis community would keep the remaining 20% of its profit (~183,223 USDC) as a bounty.

To enable the Osmosis community to keep a healthy 20% bounty:

  • Skip Protocol has agreed to refund its 5% share of ProtoRev profits (~48,216 USDC) to the user; and

  • dYdX commits to matching Skip’s contribution and addressing the user’s remaining shortfall should the proposal be granted

What’s being done to improve

From dYdX

The dYdX frontend user interface displayed the amount in and the amount out to the user. However in the instance of large withdrawal slippage, the UI will going forward display a more prominent warning to the user and a check box to opt into the execution.

For transactions greater than $1M, CCTP can’t process them and so the Skip Go API may return a route that requires a swap with large price impact using Axelar if no other safeguards are in place. We understand that Skip is updating their API to never return routes where the difference in USD value is >$10K as an additional safeguard.

From Skip

By default, the Skip Go API prevents routes with greater than 10% price impact and greater than 10% differences in USD value between the input and output assets. This behavior has historically caused issues for users transacting in small amounts where the bridging fee exceeds the threshold, preventing the routes from happening.

For that reason, clients in some cases disable this safeguard to prevent small withdrawals from being systematically blocked. In this case while disabled, the API returned a route that involved swapping to USDC.eth.axl due to CCTP’s $1m limit. To prevent this from happening in the future, the Skip Go API will prevent any route involving a loss of $10k or greater, even when default protections are disabled.

Why grant this proposal

This loss primarily resulted from the combination of user action and the bridge routing logic, which unintentionally directed funds into a low-liquidity market on Osmosis, resulting in the loss of 90% of the withdrawal value for the user. Due to Osmosis’ ProtoRev module, this value is now held by a known third party, the Osmosis DAO.
While Osmosis bears no operational fault in the routing decision, returning a portion of the captured value demonstrates goodwill, strengthens ecosystem partnerships, and reinforces user trust.

Granting this proposal would also strengthen partnership between the dYdX and Osmosis communities, which includes USDC bridging to and from dYdX Chain as well as an upcoming integration permitting dYdX front-end users to access DYDX-USD liquidity pools on Osmosis, generating deeper liquidity and fees for Osmosis community. dYdX is a long-running perpetuals DEX project with over $1.5 trillion in cumulative perps volume, and the only significant perps DEX on Cosmos.

We appreciate the Osmosis community’s consideration of this proposal and look forward to feedback and discussion.

7 Likes
3

We support this proposal. Agree with Aaron’s comment above too.

5 Likes
4

Deleted my prior comment as the text was updated :folded_hands:

4 Likes
5

We’ve seen proposals like this before and back then were very controversial: Refund dYdX user funds lost from high price impact out of ProtoRev profits

However I think this case is quite simple and resolving it doesn’t seem to have too much overhead. It seems like edge-cases like these will be covered in front-ends going forward and Osmosis is still keeping a very nice ~200k USD bounty for catching the initial arb.

As long as we dont see strong aversion from token holders we will vote yes as we think it is a fair proposal and solution. Governance exists for a reason, this is a fine use of it.

Best,
Ertemann
Lavender.Five Nodes

6

As someone who has served on the Osmosis Protocol Fee Controller up until very recently, validated both the Osmosis and dYdX networks, and now works at the dYdX Foundation, I’ve seen firsthand how much our ecosystems can achieve through collaboration.

This loss wasn’t the result of malice, but of an unfortunate routing outcome that sent a large withdrawal into a thinly liquid pool - with most of the resulting value now held by Osmosis via ProtoRev.

In the past, I’ve admittedly opposed similar reimbursement proposals. But having now worked closely with both ecosystems, and with a clear view of the dYdX roadmap - which offers significant opportunities for Osmosis to benefit from deeper partnership - I urge community members to view this case through the lens of long-term collaboration more than anything.

And importantly, Osmosis will still get to retain $200,000 as a 20% bounty.