Local Web3 wallets
Give websites and coding agents a wallet without giving them the keys.
Compatible dapps and MCP coding agents can request EVM, Solana, and Tron account access, simulation, signing, and submission. Keys stay in a locally encrypted vault, and approval happens in trusted Hronaut UI.
Product and source review: August 31, 2026
Request is not approval
An agent or website can ask. It cannot approve its own request.
Hronaut normalizes the request, validates the signer and network, decodes known actions, simulates when supported, and estimates fees. Approval is bound to the exact request hash, wallet, workspace, origin, tab navigation, and expiry. Any change to the request invalidates that approval.
Two ways in
Use the same local account from a dapp or an MCP workflow.
Websites
Standards-oriented browser providers
Hronaut exposes EIP-1193 and EIP-6963 for EVM, Solana Wallet Standard with narrow legacy compatibility, and TIP-6963 plus a narrow Tron compatibility surface. It does not pretend to be MetaMask, Phantom, or TronLink.
Coding agents
Narrow MCP wallet operations
Agents can list accessible public descriptors, read balances, prepare and simulate a transaction, request signing or submission, read request status, and cancel pending work. There is no key, vault-export, raw-RPC, or approval tool.
Onboarding and networks
Give each workspace only the account and authority it needs.
- 1
Choose a wallet type
Generate or import a managed account, add a watch-only address, or designate a dedicated agent wallet. Keep separate recovery material per chain family, unless you deliberately accept a larger blast radius.
- 2
Select the exact network
Start from curated EVM, Solana, and Tron presets with editable public RPC endpoints, or enter a custom network. Public endpoints may be rate-limited, and their operators stay part of the trust boundary.
- 3
Attach a workspace
Only wallets attached to that isolated workspace are eligible. Website permission is further scoped to the top-level HTTP or HTTPS origin, account, chain, and capability.
- 4
Start with valueless accounts
Use a local chain or testnet first, confirm the decoded action and fee, and keep independent recovery material before funding any account.
Encrypted vault
Managed signing fails closed when secure storage is unavailable.
Wallet records use authenticated XChaCha20-Poly1305 encryption. Windows, macOS, and Linux secure keyrings wrap the vault key through Electron safe storage. Linux basic_text, an unknown backend, or no secure keyring requires an Argon2id-derived passphrase key; Hronaut never silently treats basic_text as secure storage.
If neither protection mode can initialize, managed signing is disabled while watch-only accounts stay available. Recovery material is shown only in trusted Hronaut UI. It is never automatically copied, logged, placed in browser storage, or returned through MCP.
Approval and automation
Default to ask. Delegate only one exact, short-lived agent path.
Mainnet default
Trusted approval for each request
Website requests, messages and raw signing, unknown or undecodable actions, unlimited approvals, new contracts or programs, Solana and TRON mainnet, and any request outside an exact policy always require a person.
Agent-only exception
Short-lived EVM Bypass Approve policy
A dedicated EVM agent wallet can bypass its per-request dialog only after the user creates a policy bound to one workspace, configured network, origin, destination, and method, with per-transaction native, token, and fee limits, native-currency session and daily limits, successful simulation, at most 100 operations, and an expiry within seven days.
Configured, requested, and RPC-reported chain IDs must agree, but that is not independent proof that a malicious RPC is honest.
Authority stays human
An agent cannot grant the exception
The user must grant the initial wallet permission and create or change the Bypass Approve policy in trusted Hronaut UI. An agent cannot grant itself permission or create, approve, or broaden that policy.
Other narrow automation
Eligible EVM testnets and local chains
Bounded approval can also be configured for allowlisted EVM testnet chain IDs or a known local-chain ID paired with a loopback RPC. Configured and RPC-reported chain IDs must agree, but that is not independent proof of endpoint honesty. Solana and Tron public-testnet signing still requires a person; a user-entered “testnet” label is never sufficient.
Know the limits
Local custody does not make the operating system, RPC, or approval harmless.
- What Hronaut cannot stop. Hronaut cannot protect against a compromised operating system, same-user malware, malicious Electron or Chromium code, external screen or input capture, a dishonest RPC, or a person approving a misleading but accurately displayed request. JavaScript and Electron also cannot guarantee deterministic memory erasure.
- What is not integrated. Hronaut does not integrate WalletConnect, Reown, hosted custody, hosted relays, hardware wallets, external wallets, MetaMask SDK, Phantom SDK, or TronLink SDK. Use another wallet when you need hardware signing or an existing external account.
Start with a disposable account
Connect one valueless wallet to one scratch workspace.
Open Settings → Wallets, choose the chain and network, attach only the intended workspace, and review every permission before a website or coding agent requests an action. Before you fund anything, audit Hronaut's security boundary.