ICONex Wallet · Documentation

ICONex Wallet docs

Documentation for the desktop self-custody wallet in the ICON ecosystem: installation, wallet creation, recovery drills, staking, and readable signing flows.

Start with a small balance, learn how signing works, and then grow your usage. Nothing in this app should force you to hurry. If you need policy context, skim the terms and privacy notice.

Download & install Security & recovery

Section 1 · Overview

Getting started: mental model & first setup

ICONex is a self-custody wallet for the ICON ecosystem. It runs on your device and treats three things as first-class: your keys, transaction intent, and the audit trail.

What ICONex does:

  • Stores your wallet keys locally, encrypted with a password you choose.
  • Lets you hold, send, and receive ICX and ICON-based tokens.
  • Provides an intent-focused signing screen before anything is broadcast on-chain.
  • Supports staking so you can participate in ICON network rewards and governance.
  • Keeps a human-readable history of what you actually approved.

What ICONex does not do:

  • It does not hold your funds or keys for you.
  • It cannot reset your password or restore a wallet without your recovery phrase or backup.
  • It cannot stop on-chain transactions once they are signed and confirmed.
If you lose both your device and your recovery phrase, your funds are effectively lost. There is no central account, support line, or “forgot password” for self-custody.

Zero-to-ready checklist:

  1. Decide which computer will be your primary wallet device.
  2. Download ICONex only from links published on official channels or this site.
  3. Verify the file’s checksum (and signature, if available) before installing.
  4. Install the app and create a new wallet, or restore from an existing backup.
  5. Write down your 12-word recovery phrase on paper and store it offline.
  6. Send a tiny test transaction to confirm everything behaves as expected.
You don’t have to stake or interact with dApps on day one. Start with receiving, sending a small amount, and restoring your wallet on a second device you control.

Section 2 · Download & verification

Download, verify, install

Installing the wallet is easy. Installing the right wallet is more important. Treat the download step as part of your security perimeter.

Supported desktop platforms

Windows 10+ macOS 12+ Linux · 64-bit

Basic flow:

  1. Go to the Download section on the main site or from the header.
  2. Choose the build for your operating system (Windows, macOS, Linux).
  3. Download the installer file and the matching SHA-256 checksum.
  4. Compute the checksum locally and compare it to the published value.
  5. Only if they match, proceed to run the installer.
Never run an installer whose checksum does not match the published value — even if it “probably downloaded fine this time”. Delete it and download again.

Example checksum verification

Windows (PowerShell)

1. Open PowerShell
2. Run:
Get-FileHash .\iconex-wallet-setup.exe -Algorithm SHA256
3. Compare the hash to the value on the downloads page.

macOS / Linux (Terminal)

1. Open Terminal
2. Run:
shasum -a 256 iconex-wallet.dmg or
sha256sum iconex-wallet.AppImage
3. Compare the result with the published hash.

After installing, launch ICONex and make sure your system warns you if any unknown app tries to inject itself into the signing or network flow.

Section 3 · Security & recovery

Keys, passwords, and recovery habits

ICONex is built around local, encrypted keys and a recovery phrase. Knowing how they interact will save you from most catastrophic mistakes.

What lives where

  • Recovery phrase (12 words) — human-readable backup that can recreate your wallet on any compatible client.
  • Wallet password — protects your keys on this particular device only.
  • Local key storage — encrypted on disk; not synced to any cloud by ICONex.

Golden rules:

  • Write your recovery phrase on paper; keep at least one copy offline and away from this computer.
  • Never type the recovery phrase into websites, chats, or “support” forms.
  • Assume anyone asking for your phrase is trying to steal your funds.
If an app, website, or person asks for your full 12-word phrase to “check airdrop eligibility”, “verify KYC”, or “restore access”, close it. ICONex support will never ask for your phrase or private key.

Creating vs restoring

  • Create wallet — generates a new keypair and recovery phrase.
  • Restore wallet — re-creates an existing wallet from phrase, keystore, or private key.

Recommended recovery rehearsal:

  1. Create a new wallet and back up the recovery phrase on paper.
  2. Send a very small amount of ICX to that wallet.
  3. On another computer you control, install ICONex and choose Restore.
  4. Enter the 12-word phrase and confirm the address and balance match.
  5. Once confirmed, wipe ICONex from the second device if you don’t plan to use it.
A one-time “fire drill” is the best way to prove your backups actually work before they’re ever needed in an emergency.

Section 4 · Transfers & signing

Readable transfers and contract calls

Most people lose funds in the few seconds before clicking “Confirm”. ICONex slows that moment down and shows intent in plain language.

Everyday send

  1. Open ICONex and select the wallet/account you’re sending from.
  2. Click Send, paste the recipient address, and choose the asset.
  3. Enter the amount and optionally a memo (if required by the receiving service).
  4. Review the fee and network information.
  5. Click Review to open the full intent screen.
  6. If everything reads as expected, enter your password and confirm.

Intent screen checklist:

  • Asset and amount match what you typed.
  • Recipient address is exactly what you intended (compare the first & last characters).
  • Network is the one you expect (no surprise testnets or sidechains).
  • Fee is reasonable and shown in the correct asset.

Interacting with dApps

When a dApp requests a transaction, ICONex still shows the same intent-centric view — but with contract data translated into human-readable summaries whenever possible.

Safer signals

Contracts are grouped by action type (swap, stake, approve, vote), not raw function names. You should be able to describe in one sentence what you’re about to approve.

When to cancel

Cancel if:

  • you don’t recognize the dApp or domain;
  • the transaction description is vague or empty;
  • the requested spender looks unfamiliar or overly broad.

Approvals can be more dangerous than sends. Approving an unlimited spend lets a contract move your tokens later without another prompt. Prefer specific, limited approvals where possible.

Section 5 · Staking & rewards

Staking ICX without losing track of intent

ICONex exposes staking as a deliberate, reviewable flow — not a hidden toggle. You keep custody of your ICX while delegating it to validators on the network.

Before you stake

  • Make sure you understand that staked funds are subject to a network-defined unstaking period.
  • Decide how much ICX you’re comfortable locking and for how long.
  • Leave a small amount unstaked to cover future fees and claim actions.

Basic staking flow in ICONex

  1. Open your wallet and go to the Stake or Earn view.
  2. Choose how much ICX to stake using the slider or amount field.
  3. Select one or more validators you want to support.
  4. Review the summary: total staked, estimated rewards, and validator list.
  5. Confirm on the intent screen and sign the transaction.

Rewards accrue over time and can usually be claimed back into your available balance with a separate transaction.

Unstaking and moving stake

  • You can often re-allocate stake between validators without fully unstaking first.
  • Fully unstaking starts a countdown; ICX becomes spendable only after the period ends.
  • During unstaking, tokens typically stop earning rewards.
Current reward rates, commission levels, and unstaking times are properties of the ICON network, not this wallet. Always rely on up-to-date network dashboards or official documentation when estimating returns.

Good staking hygiene:

  • Prefer validators with a clear track record and transparent communication.
  • Avoid delegating everything to a single validator if you want more resilience.
  • Periodically review your staking positions and update if something looks off.

Section 6 · History

Keeping a human-readable audit trail

After a transaction lands on-chain, the question becomes: what exactly did I approve? ICONex keeps a local, sentence-level view of each action you took.

History views

  • Per account — see all activity for a specific address.
  • Grouped by intent — similar actions grouped together (e.g., “sent ICX”, “staked ICX”, “contract approvals”).
  • Linked to explorers — jump from a readable summary to the raw on-chain transaction in an explorer tab.

Useful for:

  • Explaining “what just happened” after a complex dApp interaction.
  • Preparing export data for taxes or compliance.
  • Spotting unusual patterns (many approvals to an unknown contract, etc.).

Exporting records

ICONex can export your transaction list in a machine-readable format suitable for spreadsheets or tax tools. When exporting, double-check:

  • the time range you’ve selected;
  • which account(s) are included;
  • whether internal contract operations are summarized or expanded.
Keep exports and backups in a safe place. While they don’t contain your keys, they may reveal balances and addresses you’d prefer to keep private.

Section 7 · FAQ

Quick answers to “wait, is this normal?” moments

This FAQ is focused on day-to-day usage. For more basic questions, see the FAQ block on the main page.

  • My balance looks different from an explorer. Is something wrong? Make sure the address and network match exactly. ICONex may also show staked, pending, or token balances differently from a generic explorer. If in doubt, paste the address from ICONex into a trusted explorer and compare line by line.
  • A transaction is “pending” for a long time. Check the transaction hash in an explorer. If it never appears, your node may be out of sync; if it appears but never confirms, the fee might have been too low or the network is congested. Avoid sending a duplicate unless you understand what happened.
  • I installed ICONex on a new computer, but my wallet is empty. Installing the app alone is not enough — you need to restore from your recovery phrase, keystore file, or private key. If you no longer have any of these, ICONex cannot recover the wallet.
  • Can I run the same wallet on multiple devices? Yes, as long as you restore it from the same recovery phrase or backup. Remember that anyone with that phrase effectively has the same power you do, so only restore onto devices you control.
  • I think I signed something malicious. What now? Disconnect from the suspicious site, move remaining funds to a fresh wallet with a new recovery phrase, and keep transaction hashes for later review. Consider the old wallet compromised and avoid re-using it for large balances.

Section 8 · Community & support

Where to ask questions and follow releases

Development, support, and security notes live in public channels. Always verify you’re in an official space before acting on advice.

Best ways to get help

  • Email: support@iconex.io for private issues.
  • GitHub: open issues for bugs and feature requests.
  • Community chat: ask “is this normal?” questions, share screenshots (never your keys).
When sharing screenshots, blur or crop out balances, full addresses, and transaction hashes unless they’re strictly needed for debugging.

Staying up to date

  • Watch release notes for changes to staking, fees, or signing UX.
  • Update the wallet from official links only — never from pop-ups or ads.
  • Bookmark explorer and docs URLs yourself to avoid look-alike domains.

If something in the app ever contradicts this docs page, treat that as a signal to slow down and verify whether you’re running the latest authentic build.