Merge pull request #9 from lukso-network/update-migration-pages

Update and split migration pages

docs/migration/incidents/_category_.yml

@@ -1,3 +1,3 @@
 label: '🧰 Migration Incidents'
 collapsed: true
-position: 3
+position: 6

docs/migration/introduction.md

@@ -6,8 +6,26 @@ description: Support for LUKSO LYXe Migration
 
 # Support for LYXe Migration
 
-:::warning
+## How can I migrate LYXe to LYX?
 
-This page is a Work In Progress
+You can migrate LYXe to LYX using the official [Migration Bridge](https://migrate.lukso.network/). Please check the `lukso.network` domain in order to guarantee that you are on the official app, before connecting your wallet.
 
-:::
+## What is the minimal amount of LYX that can be bridged?
+
+You need at least 1 LYXe within your connected wallet to start the migration. You can send any decimal values.
+
+## How much will it cost to migrate the LYXe?
+
+Since LYXe is managed on Ethereum, you will need some ETH to cover the Gas costs of the transaction when using the migration dApp. The transfer will cost less than 200k Gas, corresponding to [an average](https://etherscan.io/gastracker) of 0,004 ETH. Remember that these prices can fluctuate if the network is at capacity.
+
+## Where will the LYX be migrated to?
+
+The LYX will be sent to the same blockchain address (account/wallet) used during the migration. Within supported exchanges, the accounts will automatically be updated from LYXe to LYX if they have not been manually transferred to external wallets.
+
+## How long will the LYXe migration be open for?
+
+The migration process started on the 4th of July, 2023. As stated in the [Migration Article](https://medium.com/lukso/the-lyxe-migration-process-374053e5ddf5) the bridge is planned to stay open up to 4 years until July 2027, allowing anyone to migrate. The Foundation for the New Creative Economies can pause the migration bridge. Please refer to the official announcements from the [LUKSO Twitter Account](https://twitter.com/lukso_io).
+
+## Will LYXe be deprecated after the migration bridge closes?
+
+Since LYXe is the official representation of LYX on Ethereum that was used to power off the [rICO](https://medium.com/lukso/re-launching-the-reversible-ico-5289989ce7ed), the token itself will exist forever. However, we can not guarantee any price differences from LYXe to LYX after they can not be migrated anymore.

docs/migration/migration-on-exchanges.md

@@ -0,0 +1,28 @@
+---
+sidebar_label: 'Exchanges'
+sidebar_position: 4
+description: 'LYXe Migration and Exchanges'
+---
+
+# Migration on Exchanges
+
+## Will LYXe be migrated automatically?
+
+If you are holding LYXe within your own wallet, it will not be migrated automatically. You have to instantiate the migration process manually. There is likely an amount of LYXe that will never migrate due to lost wallets. Some people might even keep some LYXe for sentimental reasons.
+
+Exchanges holding LYXe might migrate the asset for their customers. However, this is not a process controlled by LUKSO directly. The following exchanges have performed an migration already:
+
+- [KuCoin LYX Migration Announcement](https://www.kucoin.com/announcement/en-kucoin-has-completed-the-token-swap-of-lyxe-to-lyx-20230721)
+- [Gate.io LYX Migration Announcement](https://www.gate.io/article/33153)
+
+For further announcements, please follow the exchange's official announcement channels.
+
+## Where can LYX be traded?
+
+You can trade or swap LYX using the following platforms:
+
+- [KuCoin Exchange](https://www.kucoin.com/announcement/en-kucoin-has-completed-the-token-swap-of-lyxe-to-lyx-20230721)
+- [Gate.io Exchange](https://www.gate.io/article/33153)
+- [Ledger Live Onramp](https://support.ledger.com/hc/en-us/articles/15847276545053-Lukso-LYX-?docs=true).
+
+3rd-party services might also create decentralized marketplaces later on.

docs/migration/supported-wallets.md

@@ -0,0 +1,29 @@
+---
+sidebar_label: 'Supported Wallets'
+sidebar_position: 2
+description: 'LUKSO Migration: Supported Wallets'
+---
+
+# Supported Wallets
+
+## Which wallets can be used to migrate LYXe?
+
+Only regular EVM-compatible browser-based wallets (Externally Owned Accounts) are supported for the migration. Universal Profiles are disabled, so your funds are kept anonymous and not directly linked to any public persona.
+
+## What if I don't have a browser-based wallet?
+
+If you migrate yourself but don't have a browser-based wallet, e.g., holding your LYXe on a Ledger or Trezor, we recommend installing an EVM-compatible browser-based wallet. After generating a new blockchain address on the installed wallet, you can send the LYXe to your new wallet and begin migrating from the browser. One of the most commonly used browser-based wallets is [MetaMask](https://metamask.io/download/), which can be installed and added to your browser within a few steps. MetaMask also supports wallet imports for both Ledger and Trezor hardware wallets.
+
+## How do I migrate if I have LYXe on a hardware wallet?
+
+If you have LYXe on a hardware wallet like Ledger or Trezor, you can send them to a supported crypto exchange or migrate independently by connecting your hardware wallet to a browser-based wallet. Make sure your hardware wallet supports external connections to browser-based wallets.
+
+## How to store LYX?
+
+You can store LYX using the [Universal Profile Browser Extension](https://docs.lukso.tech/install-up-browser-extension) or any Ethereum-compatible wallet or hardware wallet. Further details can be found on the [Wallet Support Page](#TODO).
+
+:::caution Custom Network
+
+Please ensure you can set custom blockchain networks within your blockchain wallet. Otherwise, you might not be able to see or send LYX within your wallet.
+
+:::

docs/migration/transaction-process.md

@@ -0,0 +1,31 @@
+---
+sidebar_label: 'Transaction Process'
+sidebar_position: 3
+description: 'LUKSO Migration: Transaction Process'
+---
+
+# Migration Process
+
+## Will it be possible to migrate LYX back to LYXe?
+
+No, the official [LUKSO Migration Bridge](https://migrate.lukso.network/) acts as a 1-Way-Bridge to migrate LYXe to LYX. A single locking transaction on the Ethereum blockchain automatically triggers the transfer of the equal amount of LYX on the LUKSO blockchain.
+
+## How long does it take to migrate my LYXe?
+
+The token migration usually takes about 10-15min for the transaction to be finalized and the LYX sent to the wallet on the LUKSO mainnet. This time is needed to ensure security throughout every step.
+
+:::danger Current Incident
+
+Due to the current network utilization, the migration process might take longer than expected. Please read more within [Migration Incidents January 2024](./incidents/january-2024.md)
+
+:::
+
+## What happens with LYXe sent to the LYXe contract?
+
+Any account that accidentally sent LYXe to the [LYXe Token address](https://etherscan.io/token/0xA8b919680258d369114910511cc87595aec0be6D) on Ethereum will [receive the equal amount of LYX](https://medium.com/lukso/the-lyxe-migration-process-374053e5ddf5) on the LUKSO Blockchain.
+
+## How can I see my transaction and LYX?
+
+You can check your balance using the [LUKSO Mainnet Block Explorer](https://explorer.execution.testnet.lukso.network/) and searching for your address.
+
+If you want to see the balance within your wallet, you can add LUKSO to your wallet by manually adding the RPC endpoint as described within our official [Network Properties](https://docs.lukso.tech/networks/mainnet/parameters).

docusaurus.config.js

@@ -16,7 +16,7 @@ export default {
     announcementBar: {
       id: 'incident',
       content:
-        '🚧 &nbsp; Due to a recently discovered controller malfunction, a large amount of people are experiencing issues with the extension. Please check out the latest <a href="/extension/incidents">Extension Incidents and Fixes</a> &nbsp; 🚧',
+        '🚧 &nbsp; Due to a recently discovered controller malfunction, a large amount of people are experiencing issues with the extension. Please check out the latest <a href="/extension/incidents/controller-recovery">Extension Incidents and Fixes</a> &nbsp; 🚧',
       backgroundColor: '#FEF8E6',
       textColor: 'black',
       isCloseable: false,