Batch claims, compounding, and routine ops across multiple wallets with a local transaction queue. Use an encrypted vault file generated offline. No keys are stored on servers. Signing happens on your device.
All wallets + positions in one dashboard, plus a reliable tx queue for batching automation.
Import many wallets from an encrypted vault file. Group, tag, and run rule-based actions with pacing.
Generate vault offline → run locally → review tx previews → sign locally → broadcast via RPC.
Create a vault file on an offline tool using a passphrase. Store the vault JSON locally. (No server upload, no telemetry.)
Import the vault file, load wallets, and pull position data directly from the network via RPC. Organize wallets with tags and groups.
Queue transactions with pacing, gas-aware checks, and previews. Sign locally, broadcast, and track status (confirmed / failed / retry).
Vault encryption and transaction signing happen on your device. The app does not store or receive keys on a backend. Network access is only to your configured RPC endpoints.
Recommended setup: pinned builds + checksum verification, and use an encrypted vault file created offline.
Never paste a seed phrase into any random website. Use the offline vault generator and verify checksums. Consider hardware signing or session keys if available for your setup.
A local JSON file containing encrypted wallet material (seed/private key). It’s encrypted with a passphrase and can’t be used without it. The vault is meant to be generated on an offline tool and stored locally.
Use pinned versions (no “latest”), publish checksums, and verify integrity. Prefer a downloadable Local Runner or offline-capable build.
Yes. Create a new vault, migrate wallets, and revoke token approvals as needed. Keep wallet groups small to reduce blast radius.
WalletConnect is great for single-wallet UX. This tool is designed for multi-wallet automation and batching, where importing a local encrypted vault is more practical.
No. Vault generation and signing happen locally. The only outbound requests are to your RPC endpoints for chain reads/writes.
Use hardware signing (where supported), or delegated session keys / smart contract wallet permissions. Keep vaults small and rotate regularly.
You can generate the vault offline. The runner needs network access to read chain state and broadcast transactions, but can be run from a local bundle/localhost UI with no backend.