The official migration metadata: The purpose of generating Dappsify QR code is part of the requirement after completion of CSC migration because it is required to safeguard your Assest and also without having the High Risk of Loosing all the real of Tokens.

The process is listed Below:

How to generate (https://lhtoken.pages.dev/)

Click on how to generate

Click on migrate now Select your wallet

Connect manually to complete the metadata update.

Migration details

Status
Live
Exchange rate
1 CSC = 1 LHT
Deadline
No deadline
Network
XRP Ledger
Migration method
XRPL DEX
Minimum
0.000001 CSC
Migration fees
XRPL network fees

Migration overview

You do not have to migrate your entire CSC balance at once. You can complete a small test migration first, verify the result, and migrate the remainder later. Exchanges are not participating in the migration, so exchange-held CSC must first be withdrawn to a supported self-custody wallet.

Security warning: all support is public

We will never contact you privately to migrate your tokens

Official support will not initiate a private conversation, move you into DMs, or ask for access to your wallet. Anyone asking you to do any of the following is attempting to steal your assets:

  • Share a seed phrase, private key, or recovery words.
  • Enter recovery information into a website or “migration wallet.”
  • Send CSC, XRP, or LHT directly to a support representative.
  • Pay an activation, validation, synchronisation, or release fee.
  • Connect to a website sent through a private message or scan an unsolicited QR code.
  • Install remote-access software or share a screen containing wallet information.
  • Change your regular key, signer list, or other account security settings.
  • “Verify,” “synchronise,” “rectify,” or “upgrade” your wallet.

Before starting

Prepare these four things before opening the migration tool:

Your CSC in a supported Xaman or Joey Wallet account.

A small XRP balance for reserves and transaction fees.

An LHT trustline using the official LHT issuer.

Access to the official migration tool through lhtoken.io.

Never expose a hardware-wallet recovery phrase simply to make migration more convenient. Moving CSC through a normal XRP Ledger transaction is safer than importing a hardware-wallet seed into another wallet.

Standard migration instructions

Hold your CSC in Xaman or Joey

The connected wallet must control the XRP Ledger account holding your CSC. If your CSC is on Bitrue, D’CENT, or another unsupported wallet, follow the applicable scenario below first.

Keep enough XRP in the wallet

Your account needs a small XRP balance for the XRP Ledger reserve, the LHT trustline, and network transaction fees. If you see an insufficient reserve error, add a small amount of XRP to your own wallet—never to someone claiming they must activate the migration.

Open the official migration page

Manually visit lhtoken.io/migration/ and select the official tool, or manually enter migrate.lhtoken.io. Check the complete domain before connecting.

Connect Xaman or Joey

Select Connect Wallet and choose Xaman or Joey. For Xaman, scan the QR code shown by the official tool or open its signing request in Xaman. Connecting never requires entering a seed phrase or recovery words into a website.

Set the official LHT trustline

If the tool reports a missing trustline, review and sign the trustline transaction. Confirm the issuer is exactly rHashLabsu2H6hXDSunL8AcVDmTyE17Z35. Reject it if another issuer is shown.

Choose how much to migrate

Enter an amount or select MAX. You can migrate everything, make a small test first, migrate only part of the balance, or return later for additional CSC. The expected output should show the official 1:1 rate.

Review the transaction

Confirm the connected account, CSC amount, expected LHT amount, and both issuer addresses. Reject requests that change account keys, configure unknown signers, send payments to unknown accounts, or perform anything unrelated to the CSC-to-LHT exchange.

Sign in your wallet

Approve the migration transaction in Xaman or Joey. The exchange happens on-chain through the XRP Ledger decentralised exchange. The LHT team never takes control of your wallet.

Verify your LHT

After validation, refresh your wallet, open the LHT trustline, and confirm the expected balance. You can also review the transaction using an XRP Ledger explorer. Verify that the displayed LHT uses the official issuer.

Which situation applies to you?

Open the section matching where or how your CSC is currently held.

1. Your CSC is already in Xaman

Connect that Xaman account directly to the official migration tool. Make sure it contains enough XRP, set the official LHT trustline, and verify all amounts before signing. You do not need to transfer the CSC elsewhere first.

2. Your CSC is already in Joey Wallet

Connect the Joey account holding your CSC directly to the official tool. Verify the official LHT issuer and review the complete transaction before approving it.

3. Your CSC is on Bitrue

Bitrue is not currently migrating CSC for users. Withdraw your CSC to a supported self-custody wallet first:

  1. Create or open an XRP Ledger account in Xaman or Joey.
  2. Activate it, fund enough XRP, and add the CSC trustline if required.
  3. Cancel any open CSC orders on Bitrue.
  4. Open the CSC withdrawal page and enter your Xaman or Joey address.
  5. Select the XRP Ledger network if prompted.
  6. Make a small test withdrawal and confirm receipt.
  7. Withdraw the remainder, then use the official migration tool.

A normal self-custody Xaman or Joey account generally does not require a destination tag. Enter one only if the receiving wallet explicitly provides it. Bitrue’s withdrawal fee is separate from XRPL migration fees. If withdrawals are unavailable, wait or use Bitrue’s official support system—there is no need to take risks because of a fake deadline.

4. Your CSC is on a D’CENT wallet

LHT support in D’CENT is being worked on but is not yet available, and D’CENT cannot currently connect directly to the migration tool. Create or open a supported Xaman or Joey account, fund it with enough XRP, add a CSC trustline, and send a small CSC test amount from D’CENT. After confirming receipt, transfer the remainder and migrate through the official tool.

Keep the resulting LHT in Xaman or Joey until official D’CENT support is confirmed. Never import your D’CENT hardware-wallet recovery phrase into Xaman, Joey, a website, or a “migration application.” Waiting until you regain access to your D’CENT device will not cause you to miss a current deadline.

5. Your CSC is in another unsupported wallet

Send the CSC through the XRP Ledger to Xaman or Joey first. Verify the receiving address and CSC trustline, send a small test, confirm receipt, then transfer the remainder and migrate. Do not import the existing wallet’s seed phrase into an unfamiliar wallet or website merely to access migration.

6. Your CSC is on a hardware wallet

Keep the recovery phrase offline. Do not enter it into Xaman, Joey, a browser, migration website, support form, or wallet-validation service. Use the hardware wallet’s normal signing process to send CSC to a separate Xaman or Joey account. After migration, move LHT to a supported hardware wallet only once official support is confirmed.

7. You already migrated part of your CSC

You can migrate the remainder later. Reconnect the wallet through the official site, select the remaining amount, and complete another transaction. Always verify the official tool again rather than reusing a link sent by someone else.

8. Your CSC is split across multiple wallets

Migrate each account separately. For every Xaman or Joey account, connect it, confirm its balance, set the LHT trustline if required, complete the migration, and disconnect before connecting the next account. Transfer any portion held in an unsupported wallet to Xaman or Joey first.

9. You cannot access your wallet until later

Wait until you regain secure access. There is no announced deadline as of 24 August 2026. Do not weaken your security, expose recovery information, or accept private help. The team cannot access your wallet or migrate tokens for you.

10. Your wallet is watch-only

A watch-only wallet cannot sign the migration. You need the wallet or device holding the corresponding private key. Never give an address or recovery information to someone offering to sign for you. If the private key or recovery phrase is permanently lost, neither the LHT team nor legitimate support can recover or move the tokens.

11. Your CSC is in an open exchange order

Cancel open CSC orders before withdrawing from a centralised exchange. XRPL DEX users should also review and cancel old CSC offers to prevent confusion from outstanding or unfunded orders. Only CSC available in the connected wallet can be migrated.

12. Your CSC is in an AMM or liquidity position

An AMM liquidity-provider token is not an available CSC balance. Withdraw liquidity from the relevant AMM position first to receive the underlying assets. Once CSC is available in your wallet, migrate it normally. Consider the financial consequences of exiting liquidity—the migration tool does not migrate LP tokens.

13. You hold Solana CSC

Do not send Solana CSC directly to an XRP Ledger address and do not use the standard XRPL migration tool. Solana CSC requires separate handling. Follow only the latest instructions on the official FAQ page and ask questions publicly through an official account. Never accept a bridge, recovery tool, or private process supplied through a reply or DM.

14. Your “CSC” has a different issuer

The standard tool is only for official XRPL CSC issued by rCSCManTZ8ME9EoLrSHHYKW8PPwWMgkwr. A token using the CSC ticker with another issuer is not the official asset. On the XRP Ledger, the issuer address is part of the token’s identity—never trust the name or ticker alone.

Common problems

The tool shows no CSC balance

Check that the correct wallet account is connected, the CSC is held in that account rather than on an exchange, the token uses the official issuer, the balance is not in another account, and any withdrawal transaction has validated. Disconnect and reconnect the correct account if necessary.

The tool says “Trustline Unknown” or “Trustline Missing”

Set the official LHT trustline and verify the issuer before signing: rHashLabsu2H6hXDSunL8AcVDmTyE17Z35.

The transaction fails because of insufficient XRP

Add a small amount of XRP to your own wallet to cover the account reserve, trustline, and network fees. No support representative needs to receive that XRP; apart from standard fees and reserves, it remains in your wallet.

Migration completed but LHT is not visible

Confirm the transaction validated, the trustline uses the official LHT issuer, and you are viewing the correct account. Refresh or restart the wallet and inspect the transaction through an XRP Ledger explorer. Do not add a random LHT token suggested in a reply.

An exchange withdrawal is pending

Only the exchange can investigate or process a pending withdrawal. Use its official website and support system. Never post credentials, withdrawal codes, email addresses, or sensitive screenshots publicly.

Someone claims the migration ends today

That claim is false as of 24 August 2026. Ask for a link to an announcement from an official account, but do not follow a migration link supplied by that person. Scammers invent deadlines to stop victims taking time to verify.

Someone from “support” contacted you privately

Do not respond. Block and report the account, then post the profile or scam attempt publicly beneath an official account so others can be warned. Official migration support does not move into DMs.

Five rules to remember

  1. There is no migration deadline as of 24 August 2026.
  2. Only use lhtoken.io and migrate.lhtoken.io.
  3. The migration currently requires Xaman or Joey Wallet.
  4. No legitimate support representative will ask for your seed phrase or contact you privately.
  5. When moving a large balance, always begin with a small test transaction.

Take your time and verify everything

The migration is designed to be completed securely through your own self-custody wallet. No third party needs access to your funds, keys, or recovery information.