Documentation

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.

Version
2.x
Platforms
Windows · macOS · Linux
License
MIT · Open source
Custody
Non-custodial
Getting started

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.

Local-first

Keys are encrypted at rest in the application vault; nothing is synced to a remote server.

Auditable

The full source code is published and can be built and verified independently.

Native EOSIO

No wrapped tokens, no custodial middleware — actions are pushed directly to the chain.

Getting started

System requirements

PlatformMinimumNotes
WindowsWindows 10 64-bitInstaller (.exe), auto-update supported
macOSmacOS 11 Big SurUniversal build for Intel and Apple Silicon
LinuxUbuntu 20.04 / glibc 2.31AppImage and .deb packages
Memory4 GB RAM8 GB recommended with many accounts
Disk400 MBLocal vault and cached chain metadata
NetworkHTTPS outboundAccess to at least one EOS API endpoint
Getting started

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.

  1. 01
    Windows

    Run the signed installer, accept the prompt and launch SimplEOS from the Start menu. Updates are delivered in-app.

  2. 02
    macOS

    Open the .dmg and drag SimplEOS to Applications. On first launch use right-click → Open if Gatekeeper blocks the app.

  3. 03
    Linux

    Make the AppImage executable with chmod +x SimplEOS.AppImage and run it, or install the .deb with sudo dpkg -i.

  4. 04
    Verify

    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.AppImage
Getting started

First 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.

  1. 01
    1 — Set vault password

    Use a long, unique passphrase. It cannot be recovered or reset by anyone.

  2. 02
    2 — Choose network

    Select the EOS mainnet endpoint, or add a custom endpoint for testnets.

  3. 03
    3 — Import an account

    Import an existing EOS account with its private key, or connect a hardware wallet.

  4. 04
    4 — Lock timeout

    Configure auto-lock so the vault seals itself after a period of inactivity.

Note

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.

Accounts & keys

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.

  1. 01
    By private key

    Paste a WIF private key; SimplEOS derives the public key and discovers every account it controls.

  2. 02
    By account name

    Enter the account name to fetch its permission tree, then supply the matching key.

  3. 03
    Watch-only

    Add an account without keys to monitor balances, resources and voting without signing ability.

  4. 04
    Multiple accounts

    Any number of accounts can live in one vault; switch between them from the account selector.

Accounts & keys

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.

OperationWhere it happensRequires
Key generationLocally, offlineUnlocked vault
SigningLocally, in memoryVault password
BroadcastAPI endpointNetwork access
ExportLocally, clipboard/fileExplicit confirmation
Note

Never paste a private key into a browser, chat or support ticket. SimplEOS never asks for your key outside the import dialog.

Accounts & keys

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: 1

When 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.

Accounts & keys

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.

  1. 01
    1

    Install the EOS app on the Ledger device via Ledger Live.

  2. 02
    2

    Connect and unlock the device, then open the EOS app.

  3. 03
    3

    In SimplEOS choose Import → Hardware wallet and select the derivation path.

  4. 04
    4

    Confirm every transaction on the device screen before it is broadcast.

Using the wallet

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.

FieldDescriptionExample
toRecipient account name (12 chars or a name suffix)alice.eos
quantityAmount with the exact token precision10.0000 EOS
memoRequired by most exchanges for depositsdeposit id 8421
contractToken contract accounteosio.token
Note

A missing or incorrect memo on an exchange deposit can make funds unrecoverable. Always copy the memo exactly as provided.

Using the wallet

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.

CPU

Execution time, measured in microseconds. Obtained by staking EOS or renting through PowerUp/REX.

NET

Network bandwidth in bytes, allocated the same way as CPU and replenished over 24 hours.

RAM

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.

Using the wallet

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.

ActionEffectTiming
StakeConverts liquid EOS into CPU/NETImmediate
UnstakeQueues a refund of staked EOS72 hours
Claim refundMoves matured refund to liquid balanceAfter the refund window
Deposit to REXLends EOS to the rental market for yieldImmediate
Sell REXConverts REX back to EOSMaturity buckets apply
Using the wallet

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.

  1. 01
    Direct voting

    Select producers from the list; your full stake weight applies to each one you choose.

  2. 02
    Proxy voting

    Pick a registered proxy account to inherit its votes automatically.

  3. 03
    Vote decay

    Voting weight decays over time — re-vote periodically to keep it at full strength.

Advanced

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.

Advanced

Security model

Encrypted vault

AES encryption with a password-derived key; the vault is sealed whenever the wallet locks.

No telemetry of keys

Only public data (account names, balances, chain queries) leaves the machine.

Offline signing

Transactions can be signed on an air-gapped machine and broadcast from another device.

Reproducible builds

Source code is public, so binaries can be rebuilt and compared.

Note

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.

Advanced

Backup & recovery

  1. 01
    Export keys

    Export each private key and store it offline — paper, metal backup or an encrypted volume.

  2. 02
    Backup the vault

    Copy the encrypted vault file; it is useless without the vault password.

  3. 03
    Test the restore

    Reinstall on a second machine and import from your backup to confirm it works.

  4. 04
    Owner key hygiene

    Keep the owner key offline and use active for daily operations so a leak can be repaired.

Advanced

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 package
Advanced

Troubleshooting

SymptomCauseFix
exceeded the current CPU usage limitInsufficient CPU bandwidthStake more EOS or rent CPU, then retry
billed RAM exceeds availableNot enough RAM for the actionBuy RAM from the resources page
unsatisfied_authorizationKey does not match the permissionImport the key for the required permission
Transaction expiredSlow endpoint or clock driftSwitch endpoint and sync system time
Cannot connect to APIEndpoint down or blockedSelect another endpoint in settings
Vault will not unlockWrong password or corrupted vaultRestore the vault backup and re-import keys
Reference

Glossary

TermMeaning
AccountHuman-readable on-chain identity controlled by permissions
PermissionNamed authority with a threshold and weighted keys
CPU / NETExecution and bandwidth resources obtained by staking
RAMPermanent state storage traded on an on-chain market
REXResource exchange for lending and renting EOS bandwidth
ProxyAccount that votes for Block Producers on your behalf
msigMulti-signature proposal system of the eosio.msig contract
Chain IDUnique identifier of a specific EOSIO network