This article will show you how to manage and store Quant (QNT) using Ledger Live. Quant is developed and supported by the Quant Community.
Before you start
- Update Ledger Live through the notification banner or download the latest version.
- Update the firmware on your Ledger Nano S / Nano S Plus / Nano X.
All set? Great, let’s dive in.
About Quant (QNT)
Quant is an Ethereum-based token with the goal of connecting various enterprise, private, and public blockchains. QNT is a type of cryptocurrency native to the Quant network. The Quant network contains Overledger OS and the Overledger Network.
How do I use Quant (QNT) with Ledger?
For now, users who want to safely store their QNT can do so by sending it to your Ledger Ethereum address. It will show up as a token underneath your Ethereum account.
Here is how to set up an Ethereum account in Ledger Live:
- Connect and unlock your Ledger device.
- Open Ledger Live and navigate to My Ledger.
- If asked, allow access to My Ledger (manager) by pressing both buttons on your Ledger device simultaneously.
- In My Ledger, select the App catalog, search for Ethereum, and click Install.
- Now, Add an Ethereum account. Learn how to do that here.
- Once you've set up the account, go ahead and generate the Ethereum receive address you'd like to deposit the QNT into. Learn more about this by going here.
That's it! Pretty easy right? Be sure to have your Ethereum app open while sending or trading QNT.
I can't see my Quant (QNT) tokens in my account
If your Quant (QNT) isn't appearing in Ledger Live, several factors might be at play:
- Ensure you're using the latest version of Ledger Live.
- Occasionally, old data might prevent accurate display. Try clearing the cache or check if you're able to see your tokens through Zerion which is available in the Discover section of Ledger Live.
- Visit etherscan.io and enter your Ethereum account address. Navigate to the Token Holdings section and look for your Quant (QNT) tokens. If they're absent, it suggests that your tokens may have been sent to the wrong network. Learn more about this issue here.