Your keys never leave your machine
SimplEOS is built around a strict non-custodial model: an encrypted local vault, offline signing, hardware wallet support and a fully auditable codebase. No servers hold your funds, and no one but you can authorize a transaction.
Six layers of protection
Each layer is independent — breaking one does not expose your key material to the next.
Encrypted local vault
Private keys are generated on your machine and stored in an AES-encrypted vault unlocked by a password only you know. Nothing is uploaded, mirrored or backed up remotely.
Offline transaction signing
Signing happens locally. A signed, serialized transaction is the only thing that ever touches the network — your key material never leaves process memory.
Hardware wallet support
Use a Ledger device so keys remain inside a certified secure element. SimplEOS builds the transaction, the device confirms and signs it on-screen.
Granular EOSIO permissions
Separate owner, active and custom permissions with weights and thresholds, so day-to-day usage never requires your highest-privilege key.
Open, verifiable code
The full source is published under MIT. Releases are tagged and reproducible, so anyone can build the binary and compare it to the published artifact.
No telemetry
Zero analytics, no account fingerprinting, no IP logging. Endpoint requests go only to the API nodes you configure yourself.
From generation to signature
Every step happens inside the desktop application. The chain only ever receives a signed payload — never a secret.
A serialized transaction and its signature. Nothing else: no key, no password, no vault file, no usage data.
- 01
Generation
A key pair is created locally using a cryptographically secure random source.
- 02
Encryption
The private key is encrypted with a key derived from your vault password and written to disk.
- 03
Unlock
Entering the password decrypts the vault in memory for the duration of the session.
- 04
Signing
The transaction is serialized and signed locally, or delegated to a connected Ledger device.
- 05
Broadcast
Only the signed transaction is sent to the API endpoint you selected.
- 06
Lock
Closing or locking the wallet clears decrypted material from memory.
Cryptography in plain terms
Authenticated encryption; tampering with the vault file is detected on unlock.
High iteration count with a per-vault random salt to slow brute-force attempts.
Standard EOSIO signing; keys are compatible with any Antelope tool.
Key material comes from the operating system entropy pool, never a JS pseudo-random source.
One encrypted file on your disk. Back it up like any other sensitive document.
Only read requests and signed transaction broadcasts. No SimplEOS server exists.
Least privilege, by default
EOSIO accounts separate authority into named permissions. Using the right one for the right task is the single most effective way to reduce risk.
owner
Recovery onlyThe root authority of the account. Can replace every other permission and recover control. Keep it offline, on paper, and never load it for daily use.
active
Everyday operationsUsed for transfers, staking, voting and contract actions. This is the permission you normally unlock in the wallet.
custom
Scoped delegationLinked to specific contract actions with its own weight and threshold — ideal for delegating limited rights to a device, bot or team member.
What we defend against
An honest list, including the risks no wallet can remove for you.
Phishing sites & fake installers
MitigatedSimplEOS never asks for your key outside the app. Download only from the official release page and confirm the file hash.
Clipboard and screen capture malware
Partially mitigatedKeys are never displayed unless you explicitly export them. Always re-check the destination account before confirming a transfer.
Compromised API endpoints
MitigatedA malicious node can withhold or delay data but cannot alter a signed transaction or extract a key.
Malware with full OS access
Use hardware walletA fully compromised machine can capture a password as it is typed. A hardware wallet keeps signing outside the reach of the host.
Lost password
Out of scopeThere is no reset. The encrypted vault is worthless without it — this is the trade-off of true self-custody.
Account permission takeover
User configurableIf an attacker obtains the owner key they control the account. Permission weights and thresholds limit exposure of lower-privilege keys.
Habits that keep accounts safe
- Write your owner key and vault password on paper and store them in two separate physical locations.
- Use the active permission for daily transfers; keep the owner key offline and unused.
- Verify the release checksum and publisher signature before installing an update.
- Add a hardware wallet as a key on the active permission before moving significant balances.
- Never paste a private key into a website, chat, support ticket or spreadsheet.
- Review the account's linked permissions and authorized contracts periodically.
Report a vulnerability
If you believe you have found a security issue, please report it privately before any public discussion. Include reproduction steps, the affected version and your environment. We acknowledge reports and keep reporters informed until a fix ships.
Security FAQ
Can the SimplEOS team move my funds or freeze my account?
No. There is no server-side custody, no admin key and no support override. Only a signature produced by your key can authorize an action.
What happens if I lose the computer with the wallet installed?
Your funds live on-chain, not in the app. Install SimplEOS elsewhere and import the same private key or seed to regain access.
Is a hardware wallet required?
No, but it is strongly recommended for meaningful balances: the key stays inside the device's secure element even if your computer is compromised.
How do I verify the download is authentic?
Each release publishes SHA-256 checksums. Compare the hash of your downloaded file with the published value before installing.
Take custody of your keys
Open source, checksum-verifiable and available for Windows, macOS and Linux.