Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Blacklist Mitigation #737

Open
hellofromguy opened this issue Jan 3, 2024 · 0 comments
Open

RFC: Blacklist Mitigation #737

hellofromguy opened this issue Jan 3, 2024 · 0 comments
Labels
⛓ Contracts Related to Beanstalk and ecosystem contracts 📜 RFC Formal protocol RFCs

Comments

@hellofromguy
Copy link
Contributor

hellofromguy commented Jan 3, 2024

RFC: Blacklist Mitigation + Stableswap Well Function

Authors

Guy, Ben Weintraub, Brendan Sanderson, Brean

Summary

  • Implement a stableswap Well function with a variable A parameter (that increases as the L2SR increases and decreases as the L2SR decreases);
  • Deploy BEAN:[stablecoin] stableswap Wells on Basin;
  • Whitelist the Well LP tokens in the Silo (with gauge points TBD); and
  • Implement a blacklist mitigation system that detects if a Well is blacklisted by a centralized custodian and "freezes" the Beans in the Well.

Problem

Although trading against ETH and stETH is favorable in terms of decentralization and censorship resistance, the Bean price is subject to extreme volatility as a result of having nearly all liquid Beans trading against these assets.

The opportunities for Bean liquidity providers to receive Stalk and Seed rewards is currently limited. A wider variety of options increases utility for Silo Depositors, particularly with the introduction of Generalized Convert (#716).

If centralized stablecoin LP pairs are whitelisted in the Silo without any additional changes, Beanstalk could be significantly harmed if a centralized custodian blacklists the Well. While there is no way to avoid the risk associated with centralized custodians outright, the risk to the overall health of Beanstalk can be minimized at the cost of risk to the health of individual Depositors.

Solution

Introduce a blacklist mitigation system that detects if a Well is blacklisted by a centralized custodian. Upon detection, freeze Deposits of the given LP token (such that they cannot be Withdrawn) and consider the Beans in the Well burnt.

Context

Consider an example where a BEAN:USDC Well is whitelisted in the Silo and 10% of the Bean supply is in the Well.

If the Well is blacklisted, the USDC in the Well is no longer transferable. Without any changes to Beanstalk, at this point BEANUSDC Well LP Depositors have the ability to and may potentially Withdraw and sell up to 10% of the Bean supply into other liquidity pools. The damage to Beanstalk would be proportional to the Bean supply in the Well.

LP Depositors take on the risk associated with the non-Bean assets in the Well they are providing liquidity in. Therefore, it is acceptable for the risk of a blacklisting event to be primarily held by individual Depositors rather than Beanstalk itself.

By freezing the LP Deposits and considering the Beans in the Well burnt, the Bean supply scales down an amount proportional to the percentage of the Bean supply that was in the Well.

Specification

TBD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⛓ Contracts Related to Beanstalk and ecosystem contracts 📜 RFC Formal protocol RFCs
Projects
None yet
Development

No branches or pull requests

1 participant