> 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/resources/feg-upgrade.md).

# FEG Upgrade

📃Current FEG contract:  0xF3c7CECF8cBC3066F9a87b310cEBE198d00479aC

{% hint style="warning" %}
**Manual Upgrade closed at** [**SmartDeFi.com**](https://smartdefi.com)

**Holders of FEG V1 (those that sent their tokens in for swap) FEG V2 & ROX Token holders have all been airdropped the current version of FEG as of April, 2025.**
{% endhint %}

### Overview

FEG has already been upgraded to the current SmartDeFi-based version.

Manual upgrade is closed. Eligible FEG V1, FEG V2, and ROX holders were airdropped the current version as of April 2025.

### Upgrade in Centralized Exchanges

If you held an older version of FEG on a centralized exchange, the migration was automatic. No extra action was required.

{% hint style="success" %}
We have admins ready to guide you on our [support Telegram chat](https://support.fegtoken.com/).

Remember to never respond to any direct messages (DMs) claiming to be from the FEG team, as those are 100% scams.
{% endhint %}

### Old FEG addresses

```
FEGv2 on BNB & ETH // 0xbededDf2eF49E87037c4fb2cA34d1FF3D3992A11
```

```
FEGv1 on BNB // 0xacfc95585d80ab62f67a14c566c1b7a49fe91167
FEGv1 on ETH // 0x389999216860AB8E0175387A0c90E5c52522C945
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feg.io/resources/feg-upgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.