> For the complete documentation index, see [llms.txt](https://docs.feg.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feg.io/recovery/old-fegex-sd-recovery/stage-1-sdr.md).

# Stage 1 - SDR - Completed

{% hint style="success" %}
Stage COMPLETED - Funds Claims finished in Nov 2024.
{% endhint %}

### Recovery of safeguarded SmartDeFi projects

SDR was developed through the collective efforts of dedicated members of our DeFi community. This initiative arose from a crucial need to secure funds that were locked in previous SmartDeFi projects due to exploits. Motivated by a commitment to our users, we pursued a comprehensive solution to protect these assets.

The process was challenging and extended over 1.5 years, involving the replication of the exploit contract, extensive testing, integrating a user-friendly interface, and continuous enhancements. The FEG developers successfully devised a secure method to release these funds. This solution was incorporated into the SmartDeFi Recovery Tool (SDR), which was further validated by a third-party security audit to ensure its robustness and reliability.

{% hint style="success" %}
SDR tool at  [https://sdr.fegtoken.com/ ](<https://sdr.fegtoken.com/ >) - Claims are closed after November 2024
{% endhint %}

To recover your locked funds from old safeguarded SD projects, refer to the comprehensive guides:\
\- [SDR for DEVs](/recovery/old-fegex-sd-recovery/stage-1-sdr/sdr-for-devs.md)\
\- [SDR for Investors](/recovery/old-fegex-sd-recovery/stage-1-sdr/sdr-for-investors.md)

### Essential Considerations for Fund Recovery&#x20;

It is important to clarify that the amount recovered through the SmartDeFi Recovery Tool (SDR) may not equate directly to the original locked amounts. Typically, the recovery might show a variance of 24% to 28%, and possibly greater for substantial amounts requiring multiple recovery attempts.

The recovery mechanism involves a flashloan strategy, leveraging 4.5 times the locked balance, which incurs fees associated with the flashloan from PancakeSwap (PCS) and additional costs due to BNB wrapping and unwrapping processes. For example, to recover 100 fBNB, a flashloan of 450 BNB is required, along with the associated blockchain fees.

For a detailed explanation of the recovery process, please visit the [SDR Process](/recovery/old-fegex-sd-recovery/stage-1-sdr.md) page.

### **A complete list of SmartDeFi Projects that qualify for SDR:**

{% embed url="<https://docs.google.com/spreadsheets/d/16EDHMAHBtJnw3fHk0JPghMpunDqnOGlJfe3ONKHG3ig/edit?usp=sharing>" %}

{% hint style="warning" %}
Please be aware that this recovery initiative is specifically designed for previously locked SmartDeFi projects. These funds have been securely preserved. Following the successful recovery of these assets, attention will be directed towards addressing other SmartDeFi projects that were not locked, in subsequent phases.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.feg.io/recovery/old-fegex-sd-recovery/stage-1-sdr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.