# 4. $LUXY Swap

In October 2023, we officially migrated the $LUXY token from being a multichain token to a token native to the Rollux network. Before we dive into the details of how to migrate your $LUXY from Polygon or Syscoin NEVM to Rollux, here is some information regarding the migration!

The journey to Rollux marks a significant step towards streamlining this amazing ecosystem. By consolidating the $LUXY token onto Rollux, we're ensuring heightened security, seamless user experience, and enhanced token liquidity. And this focuses mainly on two things:

1. :bulb: **Safety First: Native to Rollux:** The migration to Rollux ensures an elevated level of safety for users. The $LUXY token will become **Syscoin NEVM and Rollux native**, eliminating the reliance on centralized bridges and safeguarding you against external vulnerabilities
2. :gem: **Focused Token Liquidity:** We're committed to channeling the token liquidity where it truly matters - Rollux! This strategic move enhances liquidity efficiency, simplifies trading, and empowers the community with a dynamic marketplace.

You can check our Twitter announcements for more in-depth details:

* [Luxy Update: Token Migration to Rollux](https://twitter.com/Luxy_io/status/1697700605203017765)
* [Elevating Safety and Supercharging Liquidity](https://twitter.com/Luxy_io/status/1706433147347362008)
* [Rewards, Incentives, and exclusive opportunities](https://twitter.com/Luxy_io/status/1702750877247815944)


---

# Agent Instructions: 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:

```
GET https://docs.luxy.io/help-center/finance/usdluxy-guide/4.-usdluxy-swap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
