Electrum ETH Documentation
This documentation explains how to install Electrum ETH, understand the wallet view, how routing works across Ethereum and L2s, which networks are supported, and how the wallet behaves when routes fail. It also covers security, backups, and advanced configuration.
Quick navigation
Use the links below to jump to a specific topic. Links from the main page (“Open wallet view docs”, “How routes are chosen”, “Which networks are supported”, “How failed routes are handled”) point to the same sections.
1. Getting started
This section covers installation, first launch, and basic setup of Electrum ETH on your desktop.
1.1 Installing Electrum ETH
Download the wallet from the official downloads page:
For detailed build lists, checksums, and verification instructions, see:
1.2 First launch
On first launch, Electrum ETH will:
- Prompt you to create a new wallet or restore an existing one.
- Generate a new recovery phrase (seed) if you choose “new wallet”.
- Offer basic default settings for fee presets and networks.
1.3 Creating or restoring a wallet
- New wallet: the app will show you a list of words (seed phrase). Confirm them by following the prompts. This seed controls all accounts derived from it.
- Restore wallet: input an existing seed phrase using the interface. Make sure the word list and order match exactly.
Electrum ETH never sends your seed phrase or private keys to our servers. See Security and Backups & recovery for details.
2. Wallet view Open wallet view docs
The wallet view is designed to show everything you need before you confirm a transaction: which account you are using, how much each account holds across networks, and what the fees look like.
2.1 Accounts and labels
The accounts list helps you keep context at a glance:
- Each row represents an account derived from your wallet seed (or imported via a separate key).
- You can assign labels such as “Main”, “Cold”, “Team multisig” to accounts.
- Color marks and pinning make it easy to separate hot, cold, and shared accounts while still keeping them on one screen.
2.2 Balances across Ethereum and L2s
Under each account, Electrum ETH groups balances by network and asset:
- ETH and tokens on Ethereum mainnet are shown under a single header.
- Balances on supported L2s (e.g. rollups) appear as additional lines per chain, so you see where value is parked.
- Optional fiat equivalents (if enabled) use market data from third-party providers; they are indicative only.
2.3 Fees panel
When preparing a transaction, the fees panel shows a simple set of options, plus the underlying gas values if you need them:
- Presets: typically “Economy”, “Balanced”, “Fast”, tuned per-network.
- Advanced view: raw gas limit, base fee, priority fee, and estimated total in ETH.
- Route-aware fees: for routeable transfers, fee estimates consider the current route candidate (see How routes are chosen).
2.4 Activity and confirmations
Recent activity per account shows outgoing and incoming transfers, confirmations, and failed attempts where available:
- Status icons indicate “pending”, “confirmed”, and “failed / replaced”.
- Clicking into a transaction opens a detail view with gas used, route (if applicable), and a link to a block explorer.
3. How routes are chosen How routes are chosen
For supported transfer types, Electrum ETH can suggest routes across Ethereum and L2 networks before you send. The goal is not to be “smart” for you, but to make trade-offs between cost and speed explicit.
3.1 Inputs to the routing engine
The routing engine typically considers:
- Source and destination network for the asset you want to move.
- Current gas prices and congestion on Ethereum and L2s.
- Available bridges or canonical paths we support for that asset.
- Historical success and failure rates for each route (if available from recent history).
3.2 How route candidates are compared
For each route candidate (e.g. “direct on Ethereum”, “via L2-A”, “via L2-B”), the engine estimates:
- Total cost: network fees on each hop, plus any bridge fees that apply.
- Estimated time: number of confirmations required and typical block times.
- Reliability: whether we have observed recent issues with that path.
The UI then marks a default suggestion (for example, “Suggested: Ethereum” or “Suggested: L2 route”) but always shows alternatives side by side.
3.3 Overriding route suggestions
You always stay in control:
- You can switch to any available alternative route before signing.
- You can disable multi-route suggestions for certain transaction types and keep a simpler “one-route” experience.
- Advanced users can prefer specific networks or bridges in settings, within safety limits.
4. Supported networks Which networks are supported
Electrum ETH is focused on Ethereum and a curated set of L2 networks. The exact list can evolve over time as networks mature or become less relevant.
4.1 Core support
- Ethereum mainnet: full wallet support, routing, and fee estimation.
- Selected L2s: mainstream rollups and sidechains integrated for balance display and routing where appropriate.
- Test networks: a small subset of testnets for development and experiments (availability may change).
4.2 Custom networks and nodes
Advanced users can connect to their own nodes or custom RPC endpoints for certain networks:
- Add or edit RPC URLs, chain IDs, and explorer links in Advanced configuration.
- Disable networks you do not use to keep the interface focused.
- Prefer your own node for privacy or compliance reasons.
4.3 Asset coverage
Token balances are typically shown for standard ERC-20 tokens on supported networks. Some assets (e.g. complex LP positions or highly custom contracts) may not be fully understood by the wallet, and may appear as generic balances.
5. How failed routes are handled How failed routes are handled
Not every route succeeds. Networks can become congested, bridges can pause, and individual transactions can fail. Electrum ETH aims to make failures visible, understandable, and recoverable where possible.
5.1 Types of failures
- Pre-flight failures: a route is unavailable or unsafe before you sign (e.g. bridge paused, bad quote).
- On-chain failures: a transaction you signed is mined but reverts, or is dropped and replaced.
- Timeouts: confirmations are taking significantly longer than expected.
5.2 What the wallet does
- Marks the affected transaction with a clear status (“Failed”, “Stuck”, “Replaced”).
- Shows any error messages exposed by the network or smart contract, when available.
- Suggests simple next steps (e.g. “Try again with higher gas”, “Consider alternative route on L2-X”).
5.3 What the wallet does not do
- It does not automatically re-spend your funds or reroute without a new signature from you.
- It cannot recover funds lost due to protocol bugs, malicious contracts, or irreversible on-chain actions.
6. Security
Electrum ETH is non-custodial: keys stay on your device and signing never leaves it. This chapter outlines what the wallet defends against, what it cannot protect you from, and how to operate it safely.
6.1 Threat model & assumptions
Electrum ETH is designed with these assumptions:
- Your desktop is trusted and free of malware or keyloggers.
- You can verify the app you installed (hashes/signatures) and you downloaded it from an official source.
- Networks, bridges, and contracts you interact with may fail or be malicious; the wallet surfaces data but cannot make them safe.
- You keep your recovery phrase private and offline. Anyone with it controls your funds.
6.2 Key management
- Keys are generated, stored, and encrypted locally; they are never sent to Electrum ETH servers.
- Transaction signing happens locally; only signed transactions are broadcast.
- Hardware wallets (where supported) keep private keys off your computer; always confirm details on the device screen.
- Store seed phrases offline (paper/metal). Do not screenshot or sync to cloud notes.
6.3 Signing & transaction safety
- Read the summary before signing: network, destination address, amount, and fees. If something looks off, cancel.
- Prefer known contracts and official links; avoid signing messages or approvals from untrusted sites.
- For new bridges or protocols, start with a small “test” transfer to validate routes and behavior.
- Review token allowances periodically and revoke stale approvals with trusted tools.
6.4 Networks, RPC endpoints, and bridges
- Use trusted RPC endpoints. A malicious RPC can lie about balances or suggested gas; it cannot forge your signatures.
- Verify chain IDs match the network you expect before signing.
- Bridges carry protocol risk. Check their status pages and avoid large transfers during incidents or upgrades.
- Keep some native gas token on each network for exits or retries.
6.5 Data handling & privacy
- Account data and signing material stay local. Network calls carry only what is needed to query balances or broadcast transactions.
- Avoid pasting private data (seeds, keys) into any chat or support channel. The team will never ask for them.
- Review the Privacy Policy for details on analytics or crash reporting if enabled in your build.
6.6 Supply chain & updates
- Download installers from the official downloads page and verify hashes/signatures against the posted checksums.
- Read release notes before updating, especially if you rely on specific networks or plugins.
- Avoid running unsigned binaries or “patched” builds from third parties.
6.7 Reporting security issues
- If you suspect a vulnerability, do not post publicly. Use a private channel to contact the maintainers (security contact or repository advisory form).
- Include app version, OS, reproduction steps, and expected vs actual behavior. Never include seeds or private keys.
7. Backups & recovery
Proper backups are essential. Electrum ETH cannot restore your wallet if you lose your recovery phrase and all backups.
7.1 What you need to back up
- The primary recovery phrase (seed) shown when creating a wallet.
- Any additional wallets or imported keys that are not derived from the main seed.
- Optional: a copy of the wallet configuration file for convenience (does not replace the seed).
7.2 Recovery
To recover on a new machine:
- Install the wallet from the official downloads page.
- Choose “Restore wallet” on first launch or in the app menu.
- Enter your seed phrase carefully in the correct order.
- Re-add any imported accounts or custom networks if they were not part of the primary seed setup.
8. Advanced configuration
Advanced users can tailor Electrum ETH to their setup, including custom RPC nodes, fee policies, and privacy options.
8.1 Custom RPC and nodes
- Replace default RPC endpoints with your own node URLs for Ethereum or supported L2s.
- Configure chain ID, explorer URL, and network name for custom entries.
- Disable telemetry or diagnostics (where available) for a tighter privacy posture.
8.2 Fee and routing preferences
- Choose default fee preset (e.g. Balanced vs. Fast) per network.
- Turn route suggestions on or off for certain transaction types.
- Prefer specific networks or bridges where multiple routes are available (subject to safety checks).
9. Releases and updates
Electrum ETH is updated periodically with new features, security fixes, and network support improvements.
9.1 Release channels
- Stable: recommended for most users; focuses on reliability.
- Pre-release / beta (if offered): early access to features, recommended for testing only.
9.2 Updating safely
- Always download from the official website or repositories linked from it.
- Verify signatures or checksums as documented on the downloads page.
- Keep a recent backup of your seed phrase before upgrading, even if upgrades are designed to be safe.
10. Troubleshooting & FAQ
10.1 Common issues
- Balances not updating: check your network connection and node status. Try switching to a different RPC or your own node.
- Transaction stuck: see the status in the wallet and block explorer. For replaceable transactions, use “speed up” or “cancel” options if available.
- Route options missing: routing is only available for certain assets and networks. Check Supported networks.
10.2 Getting help
You can get help from:
- The official documentation (this page and related sections).
- Community channels listed under Community.
- Security-sensitive issues: security@electrum.eth.
When asking for help, it is safe to share transaction hashes and error messages, but never your seed phrase or private keys.