Electrum NEO Wallet Docs

1. Overview & structure of the docs

Electrum NEO Wallet follows a simple documentation split:

The most detailed and up-to-date documentation is shipped with the codebase and in the project’s GitHub docs. Use this page as a orientation layer: it highlights which topics exist and how they relate to everyday use of the wallet.

2. Getting started with Electrum NEO Wallet

Getting started documentation focuses on a clean first-run experience on all supported desktop platforms:

• System requirements for Windows, macOS and Linux.
• Installation and first launch: where to download verified installers and how to confirm you are running an official build.
• Creating a new wallet: generating a deterministic recovery phrase, confirming it and setting a local password (if supported by your build).
• Restoring an existing wallet: using your recovery phrase to rebuild the same wallet on another machine.

These guides are intentionally non-technical and can be followed by anyone coming from other ecosystems or new to Neo.

3. Core wallet operations & features

This part of the docs explains how day-to-day wallet actions map to how Neo and Neo X actually work:

• Accounts and addresses – how the wallet derives addresses from your recovery phrase and how Neo addresses are formatted.
• Balances and history – how to read NEO / GAS balances, transaction lists and confirmations in a finality-based system.
• Sending and receiving – preparing a transaction, setting fees (where relevant) and verifying the destination before signing.
• Working with GAS rewards – where reward estimates in the UI come from and how they relate to the public NEO & GAS calculator.

For power users and integrators there are additional notes on how transaction construction aligns with the underlying Neo protocols, including Neo X specifics.

4. Networks, RPC endpoints & connectivity

Electrum NEO Wallet acts as a thin client: instead of running a full node, it talks to Neo and Neo X infrastructure over RPC. The documentation here covers:

• Supported networks – Neo N3 and Neo X, MainNet vs TestNet, and how to switch between them.
• Choosing RPC providers – recommended public endpoints, latency and reliability considerations, and how they affect UX.
• Custom endpoints – pointing the wallet at your own Neo or Neo X node for self-hosted setups.
• Troubleshooting connectivity – interpreting error messages, switching nodes and collecting logs when something goes wrong.

This section is especially relevant if you run your own infrastructure or build services that integrate tightly with Neo / Neo X.

5. Neo X, EVM and dApp connections

Neo X introduces an EVM-compatible layer within the Neo ecosystem. The docs describe how Electrum NEO Wallet behaves in that environment:

• Neo X account model – how the wallet exposes Neo X accounts and tokens alongside core Neo balances.
• Connecting dApps – the Web3-style signing flow used by dApps to request transactions and messages from the desktop wallet.
• Permissions & prompts – what you see when a dApp asks for access and how to verify what you are signing.
• Common patterns – swaps, liquidity provision, bridges and other DeFi interactions on Neo X.

Integration examples highlight how dApp developers can treat Electrum NEO Wallet as an identity and signing layer without embedding private key logic in the browser.

6. Backup, security model and limitations

A dedicated section outlines the security assumptions of a non-custodial, Electrum-style wallet:

• Recovery phrase handling – why it must never be stored as a screenshot, synced plaintext note or shared over chat.
• Local encryption – what is protected by your wallet password (if enabled) and what is not.
• Device and OS hygiene – keeping your environment free from malware, keyloggers and untrusted remote-access tools.
• Limits of support – what maintainers can and cannot do if a device is compromised or a recovery phrase is lost.

The goal of this part of the docs is to make the risk model explicit, not to shift responsibility: knowing how the wallet is designed helps you choose a security posture that matches the value you keep in it.

7. Releases, checksums and build verification

Because the wallet is a desktop application, release integrity matters. The documentation explains:

• Where releases live – official binaries, source archives and checksums published with each tagged version.
• How to verify downloads – using checksums or signatures (if provided by the project) before running an installer or binary.
• Versioning and compatibility – how version numbers relate to protocol changes, Neo / Neo X upgrades and migration notes.
• Changelogs – where to find lists of fixes, features and breaking changes between releases.

In practice, this section ties together the download links on the main site and the more detailed release artefacts published in the repository.

8. Contributing, issue reports & support

Finally, the docs describe how to work with the project as a contributor or as a user reporting issues:

• How to report bugs – what information is useful (OS, version, logs) and what must never be included (seeds, private keys).
• Feature requests and proposals – where to open them and how to frame them in terms of the wallet’s scope.
• Development environment – a high-level overview of how to clone, build and run the wallet from source.
• Community channels – links to places where technical discussion happens (chats, forums, working groups).

This overview describes the structure of the documentation set; individual guides, references and examples are updated along with wallet releases to reflect new features and network capabilities.