Introduction
Anchor Wallet by Greymass is a non-custodial desktop wallet designed for users and developers who want full control over their digital assets. It supports multiple Antelope-based blockchains (EOS, WAX, Telos, Proton, FIO) and offers advanced features for key management, transaction signing, and dApp integration — all with a strong focus on privacy and transparency.
This documentation covers everything from installation to advanced configuration. No prior blockchain knowledge is required — each section builds from the basics.
Installation
System Requirements
- Windows 10 or later, macOS 11+, or a modern Linux distribution
- At least 200 MB free disk space
- Internet connection for blockchain access
Download
Always download from the official source: anchorwallet.org. Avoid third-party sites or unofficial binaries — they may contain modified code.
Signature Verification
gpg --verify anchor-vX.Y.Z.pkg.asc anchor-vX.Y.Z.pkg
This confirms the file integrity and ensures it was signed by the verified Greymass PGP key.
Initial Setup
When launching Anchor for the first time, you’ll be prompted to configure your environment:
- Select your default blockchain network (e.g., EOS Mainnet)
- Set up your wallet password — encrypts all sensitive data locally
- Import or create an account
All wallet data is stored locally and encrypted. No data is uploaded or tracked.
Managing Accounts
Adding Accounts
You can import existing accounts via private key or connect a hardware wallet such as Ledger. Anchor automatically detects supported devices and offers a step-by-step setup.
Switching Networks
Anchor allows switching between supported blockchains seamlessly. Each network has isolated key storage and configuration, ensuring no accidental cross-chain actions.
Custom Tokens
You can add custom tokens using their contract and symbol — this allows Anchor to display balances for less-known or private tokens.
Transactions
Transactions in Anchor are signed locally using your private keys. They’re never transmitted without explicit approval. Each signing request displays a human-readable breakdown: actions, resources, and fees.
Offline Signing
For maximum security, Anchor supports offline signing. You can generate unsigned transactions, sign them on an isolated machine, and broadcast later.
Multi-Action Transactions
Anchor supports multiple chained actions per transaction, enabling complex operations like staking, transferring, and delegating resources in one go.
Security Practices
Security is the cornerstone of Anchor’s philosophy. Below are key measures implemented to protect users:
- Private keys encrypted locally using OS-native secure storage
- No telemetry, analytics, or hidden network calls
- All binaries are PGP-signed by Greymass
- Open-source transparency — public audits welcomed
Additionally, users can verify the integrity of releases by comparing SHA256 checksums against the official repository.
dApp Integration
Anchor implements the Antelope Signing Request (ASR) protocol, which enables dApps to request signatures securely without ever accessing private keys. Communication happens locally, and each request must be confirmed by the user.
Developers can use libraries like eosio-signing-request or anchor-link to integrate signing flows in their dApps.
The process is standardized and chain-agnostic.
Troubleshooting
If Anchor behaves unexpectedly, here are recommended recovery steps:
- Restart the app and check for updates
- Switch to a different API node in Settings → Network
- Verify you’re on the correct blockchain (e.g., mainnet vs testnet)
- Backup your wallet and reinstall Anchor
If the issue persists, visit the GitHub issue tracker or ask for help in the Greymass Discord.
Advanced Tools
Anchor includes developer-friendly tools like:
- Transaction builder — manually craft and simulate custom transactions.
- Permission viewer — inspect and edit account permission structures.
- Key export/import — move keys securely between devices.
- Resource management — monitor and manage CPU, NET, and RAM usage.
Frequently Asked Questions
Does Anchor store my keys online?
No. All keys are encrypted and stored locally on your device. Anchor never uploads them anywhere.
Is Anchor open source?
Yes. 100% of Anchor’s code is available on GitHub for review and verification.
Can I use Anchor without internet?
Yes — via offline signing mode. You can sign transactions on an air-gapped machine and broadcast later from another device.
Resources & Support
Thank you for using Anchor — a secure, transparent, and community-driven wallet for the Antelope ecosystem.