DeFi Saver's approach to deprecating protocols

DeFi protocols are a living, breathing thing on the blockchain. Constantly evolving, or experiencing the slightest changes such as market LTV's, smart contract updates, and much more.

Seeing as DeFi Saver serves as the frontend for these protocols, our dev team also needs to ensure that they follow through with any and all changes. Without them making meticulous updates, the protocol might not work on our app - affecting both existing users, and those that are looking to open a position there.

Keeping up with these changes is relatively straightforward - However, ensuring that we've followed through with relevant front and backend updates to our features requires significant time and resources.

This brings us to a crossroads, where we need to make tough decisions on where the time and resources are allocated. If we reach a point where a specific protocol is not seeing much utilization by users, yet requires considerable effort from us to be maintained - it would make sense to consider sunsetting the specific protocol from DeFi Saver.

On the other hand, some protocols make the decision to move to a new version, and stop development of the previous one. In turn, this leads to the protocol no longer having supply, borrow, or other key elements on a specific market - or the entire protocol.

When this happens, we also need to do our due diligence and make sure that, if said protocol is integrated with DeFi Saver, we warn our users ahead of time.

Finally, some protocols experience technical issues that either pose a serious security compromise or prevents key features from functioning. In these cases, our obligation is to ensure users are aware of this, and that we prevent the creation of new positions until said issue is resolved on the protocol's side.

While we may not deprecate the protocol in these cases, we do prevent users to open new positions, provide an explanation on the protocol's dashboard, and provide actionable steps for moving out of the protocol.

How we approach deprecating protocols

The experience users have with our app is at the forefront of how we approach things at DeFi Saver. As such, we're well aware that sunsetting a protocol affects users who have positions opened on it, which is why simply removing the protocol instantly is not an acceptable solution.

To ensure that users of a sunsetting protocol have the smoothest possible experience, we employ the following approach:

• Providing a clearly visible warning on the protocol's dashboard that it is being removed from DeFi Saver.

• Providing users with actionable steps on what to do with their existing position(s).

• Preventing new positions from being created.

• Establishing a specific date when the protocol will be deprecated from DeFi Saver.

• Ensuring that the date gives enough time for users to see it and react - so that they're not surprised .

Show me an example:

Morpho Labs announced that they are gradually winding down Morpho-Aave Optimizers. Seeing as Morpho-Aave is a protocol on DeFI Saver, our first step was to notify users on the protocol's main dashboard:

In-line with the bulletpoints above, we also:

• Prevented the creation of new positions (borrowing)

• Gave users an ETA of when the protocol will no longer be visible

• Ensured the date gives existing users months to see the warning.

• Provided actionable steps i.e. using our Loan Shifter tool to move their position

Articles in this category

The "No longer available" category contains Knowledge Base articles of protocols that DeFi Saver no longer actively supports.

We've kept these articles visible in this category so that new users can still get a glimpse of DeFi Saver's history, and aspiration to consistently provide users with relevant options.