Custody
Keys stay local
Private keys, recovery phrases, decrypted vault records, and approval authority are never returned to a website or MCP client.
Local Web3 wallets
Give websites and coding agents a wallet without giving them the keys.
Hronaut lets compatible dapps and MCP coding agents request EVM, Solana, and Tron account access, simulation, signing, and submission through a locally encrypted vault and trusted Hronaut approval.
Product and source review: August 31, 2026
Access
Scoped per task
A wallet must be attached to the workspace, and its address remains hidden until the current top-level origin receives permission.
Mainnet
A person approves
Mainnet signing and sending always require explicit approval in trusted Hronaut chrome.
Separate request from 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, estimates fees, and binds approval to the exact request hash, wallet, workspace, origin, tab navigation, and expiry. A mutation invalidates that approval.
Two compatible surfaces
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
Create only the account and authority each workspace 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 network presets with editable public RPC endpoints, or enter a custom network. Public endpoints may be rate-limited and their operators remain part of the trust boundary.
- 3
Attach a workspace
Only wallets attached to that isolated workspace are eligible. Website permission is additionally 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 an 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 remain available. Recovery material is shown only through trusted Hronaut UI and is not automatically copied, logged, placed in browser storage, or returned through MCP.
Approval and automation
Default to ask. Automate only an independently bounded low-risk environment.
Always human
Mainnet and unclear intent
Mainnet operations, unknown or undecodable actions, unlimited approvals, new contracts or programs, blind or raw messages, recovery export, and permission or vault changes always require a person.
Narrow automation
Eligible EVM testnets and local chains
Bounded approval can be configured only when Hronaut independently attests an allowlisted EVM testnet chain ID, or pairs a known local-chain ID with a loopback RPC. Policies can cap destinations, methods, amounts, fees, time, and operation counts.
Still human today
Solana and Tron public testnets
Solana and Tron public-testnet signing still requires a person until the adapters can bind an independently verified network fingerprint into the request. A user-entered “testnet” label is never sufficient.
Know the limits
Local custody does not make the operating system, RPC, or approval harmless.
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.
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 hardware signing or an existing external account is required.
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 letting a website or coding agent request an action.