Everything you need to run SimplEOS
A complete technical reference for the SimplEOS desktop wallet — from installation and account import to resource management, permissions, hardware signing and recovery procedures.
Overview
SimplEOS is a non-custodial desktop wallet for the EOS blockchain, built by EOS Rio as an Electron application. Private keys never leave your machine: they are encrypted locally with a password you choose and used only to sign transactions that are then broadcast to a public API endpoint.
The wallet exposes the full native feature set of EOSIO — token transfers, staking and unstaking, REX lending, CPU/NET/RAM management, Block Producer voting, proxy delegation, permission editing and contract action inspection — through a single interface, with no browser extension required.
Keys are encrypted at rest in the application vault; nothing is synced to a remote server.
The full source code is published and can be built and verified independently.
No wrapped tokens, no custodial middleware — actions are pushed directly to the chain.
System requirements
| Platform | Minimum | Notes |
|---|---|---|
| Windows | Windows 10 64-bit | Installer (.exe), auto-update supported |
| macOS | macOS 11 Big Sur | Universal build for Intel and Apple Silicon |
| Linux | Ubuntu 20.04 / glibc 2.31 | AppImage and .deb packages |
| Memory | 4 GB RAM | 8 GB recommended with many accounts |
| Disk | 400 MB | Local vault and cached chain metadata |
| Network | HTTPS outbound | Access to at least one EOS API endpoint |
Installation
Download the package for your platform from the Download section, then follow the steps for your operating system. Always verify the checksum published with the release before installing.
- 01Windows
Run the signed installer, accept the prompt and launch SimplEOS from the Start menu. Updates are delivered in-app.
- 02macOS
Open the .dmg and drag SimplEOS to Applications. On first launch use right-click → Open if Gatekeeper blocks the app.
- 03Linux
Make the AppImage executable with chmod +x SimplEOS.AppImage and run it, or install the .deb with sudo dpkg -i.
- 04Verify
Compare the SHA-256 hash of the downloaded file with the hash listed on the release page before running it.
# Linux
chmod +x SimplEOS-2.x.AppImage
./SimplEOS-2.x.AppImage
# verify the download
sha256sum SimplEOS-2.x.AppImageFirst run & vault setup
On first launch SimplEOS creates an encrypted local vault. The password you set protects every key stored in the application and is required to unlock the wallet and to sign transactions.
- 011 — Set vault password
Use a long, unique passphrase. It cannot be recovered or reset by anyone.
- 022 — Choose network
Select the EOS mainnet endpoint, or add a custom endpoint for testnets.
- 033 — Import an account
Import an existing EOS account with its private key, or connect a hardware wallet.
- 044 — Lock timeout
Configure auto-lock so the vault seals itself after a period of inactivity.
The vault password is not a seed phrase. Losing your private keys or their backup means losing access to the account — SimplEOS cannot restore them.
Importing accounts
EOS accounts are human-readable names controlled by keys. To manage an account in SimplEOS you import a private key that is authorised by one of the account permissions — typically active for daily operations and owner for recovery.
- 01By private key
Paste a WIF private key; SimplEOS derives the public key and discovers every account it controls.
- 02By account name
Enter the account name to fetch its permission tree, then supply the matching key.
- 03Watch-only
Add an account without keys to monitor balances, resources and voting without signing ability.
- 04Multiple accounts
Any number of accounts can live in one vault; switch between them from the account selector.
Key management
Keys are stored encrypted with AES using a key derived from your vault password. They are decrypted in memory only for the moment a transaction is signed and are never transmitted.
| Operation | Where it happens | Requires |
|---|---|---|
| Key generation | Locally, offline | Unlocked vault |
| Signing | Locally, in memory | Vault password |
| Broadcast | API endpoint | Network access |
| Export | Locally, clipboard/file | Explicit confirmation |
Never paste a private key into a browser, chat or support ticket. SimplEOS never asks for your key outside the import dialog.
Permissions & multisig
EOSIO permissions are a tree of named authorities, each with a threshold and a weighted list of keys or accounts. SimplEOS lets you inspect and edit this structure, including creating custom permissions linked to specific contract actions.
# example authority for a 2-of-3 active permission
threshold: 2
keys:
- EOS7...abc weight: 1
- EOS8...def weight: 1
accounts:
- alice@active weight: 1When a transaction does not reach the required threshold it is stored as a proposal via eosio.msig, where the remaining signers can approve it before execution.
Hardware wallets
Ledger devices are supported for signing. With a hardware wallet the private key never exists on the computer — SimplEOS builds the transaction, the device displays it, and only the signature returns to the application.
- 011
Install the EOS app on the Ledger device via Ledger Live.
- 022
Connect and unlock the device, then open the EOS app.
- 033
In SimplEOS choose Import → Hardware wallet and select the derivation path.
- 044
Confirm every transaction on the device screen before it is broadcast.
Transfers & tokens
Transfers call the transfer action of a token contract. For EOS this is eosio.token; other tokens use their own contract, which SimplEOS resolves automatically for known assets and accepts manually for custom ones.
| Field | Description | Example |
|---|---|---|
| to | Recipient account name (12 chars or a name suffix) | alice.eos |
| quantity | Amount with the exact token precision | 10.0000 EOS |
| memo | Required by most exchanges for deposits | deposit id 8421 |
| contract | Token contract account | eosio.token |
A missing or incorrect memo on an exchange deposit can make funds unrecoverable. Always copy the memo exactly as provided.
CPU, NET & RAM
EOS transactions consume bandwidth resources instead of a per- transaction fee. SimplEOS shows live usage and lets you adjust each resource independently.
Execution time, measured in microseconds. Obtained by staking EOS or renting through PowerUp/REX.
Network bandwidth in bytes, allocated the same way as CPU and replenished over 24 hours.
Permanent on-chain storage, bought and sold on the Bancor-based RAM market at a floating price.
If a transaction fails with exceeded the current CPU usage limit, increase CPU by staking more EOS, renting resources, or waiting for the allowance to refill.
Staking & REX
Staking locks EOS into CPU and NET bandwidth for your account. Unstaking returns the tokens to the liquid balance after the network refund period.
| Action | Effect | Timing |
|---|---|---|
| Stake | Converts liquid EOS into CPU/NET | Immediate |
| Unstake | Queues a refund of staked EOS | 72 hours |
| Claim refund | Moves matured refund to liquid balance | After the refund window |
| Deposit to REX | Lends EOS to the rental market for yield | Immediate |
| Sell REX | Converts REX back to EOS | Maturity buckets apply |
Voting & proxies
Staked EOS carries voting weight in Block Producer elections. You can vote for up to 30 producers directly, or delegate your weight to a proxy that votes on your behalf.
- 01Direct voting
Select producers from the list; your full stake weight applies to each one you choose.
- 02Proxy voting
Pick a registered proxy account to inherit its votes automatically.
- 03Vote decay
Voting weight decays over time — re-vote periodically to keep it at full strength.
Endpoints & network
SimplEOS talks to the chain through standard EOSIO HTTP APIs. You can switch endpoints, add your own node, or point the wallet at a testnet without reinstalling.
# add a custom endpoint
Name: My Node
Protocol: https
Host: api.example.com
Port: 443
Chain ID: aca376f2...4d1a3 (EOS mainnet)A wrong chain ID makes signatures invalid on the target network — verify it when configuring testnets.
Security model
AES encryption with a password-derived key; the vault is sealed whenever the wallet locks.
Only public data (account names, balances, chain queries) leaves the machine.
Transactions can be signed on an air-gapped machine and broadcast from another device.
Source code is public, so binaries can be rebuilt and compared.
Threat model: SimplEOS protects keys at rest and in transit, but it cannot protect a compromised operating system. Use a clean machine and full-disk encryption for high-value accounts.
Backup & recovery
- 01Export keys
Export each private key and store it offline — paper, metal backup or an encrypted volume.
- 02Backup the vault
Copy the encrypted vault file; it is useless without the vault password.
- 03Test the restore
Reinstall on a second machine and import from your backup to confirm it works.
- 04Owner key hygiene
Keep the owner key offline and use active for daily operations so a leak can be repaired.
Build from source
SimplEOS is an Electron application. Building locally lets you verify the published binaries or run a development build.
git clone https://github.com/eosrio/simpleos.git
cd simpleos
npm install
npm run electron:serve # development
npm run electron:build # production packageTroubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| exceeded the current CPU usage limit | Insufficient CPU bandwidth | Stake more EOS or rent CPU, then retry |
| billed RAM exceeds available | Not enough RAM for the action | Buy RAM from the resources page |
| unsatisfied_authorization | Key does not match the permission | Import the key for the required permission |
| Transaction expired | Slow endpoint or clock drift | Switch endpoint and sync system time |
| Cannot connect to API | Endpoint down or blocked | Select another endpoint in settings |
| Vault will not unlock | Wrong password or corrupted vault | Restore the vault backup and re-import keys |
Glossary
| Term | Meaning |
|---|---|
| Account | Human-readable on-chain identity controlled by permissions |
| Permission | Named authority with a threshold and weighted keys |
| CPU / NET | Execution and bandwidth resources obtained by staking |
| RAM | Permanent state storage traded on an on-chain market |
| REX | Resource exchange for lending and renting EOS bandwidth |
| Proxy | Account that votes for Block Producers on your behalf |
| msig | Multi-signature proposal system of the eosio.msig contract |
| Chain ID | Unique identifier of a specific EOSIO network |
