Ethereum · ETH
An Ethereum wallet whose key is on another device
Every dApp you already use, answering the standard Web3 API, with the key on a machine that has no network. The transaction is decoded, checked and shown to you twice: in the browser, and again on the device that actually signs it.
A drop-in wallet, not a plugin to learn
It announces itself over EIP-6963, so sites list it beside the wallets they already offer. Transactions, personal_sign, EIP-712 typed data and EIP-5792 batched calls all go through the same optical ceremony.
The calldata is read before you sign
An approval, a transfer, a swap: the call is decoded into what it does and who it lets spend, with the known-phishing list checked from a snapshot that ships with the extension - no lookup, no leak of where you are going.
A local model, not a cloud service
A small model runs on your machine to flag a request that does not look like what it claims to be. It never leaves the device and it never gates: it explains, you decide, and the offline device still shows the truth.
Allowances you can take back
A token allowance you granted once can be revoked from the wallet, through the same review and the same offline signature.
Ethereum wallet: questions people ask
Is it a MetaMask alternative?
It answers the same standard interface, so dApps treat it as an ordinary wallet. The difference is where the key is: on a separate device with no network, instead of in the browser.
Does every dApp work with it?
It implements the standard Web3 provider API and announces itself over EIP-6963, which is how modern sites discover wallets. Nearly two hundred real sites are driven end to end by the test suite on every release.
What about typed data and batched calls?
EIP-712 typed data is decoded field by field on the offline device, and EIP-5792 batched calls are shown as the list of calls they are.
Is it free and open-source?
Yes, both the extension and the Vault, with reproducible builds published for the stores.
