Your keyhold. One click from any page.
The MERKI extension is planned to carry the same keyhold as the web wallet into the browser toolbar and side panel, with an approval screen you can actually read. It is not released, and nothing here is a download. If someone offers a MERKI extension before this page links to it, it is not ours.
A site asks for a transfer
The panel shows the full recipient, the amount and which key will sign. Nothing moves until you approve it there.
Approve operation
- Site
- example.app
- To
- 0x9a…41c7 (full address shown)
- Amount
- 0.05 ETH
- Signs with
- main key #12
- Then stores
- key #13
Design preview of a planned extension · example values, not account data
Fewer surprises. More reading.
Review every request
Every transaction waits on a screen showing the asking site, the complete target address, the amount and the signing key. Unfamiliar calls and open-ended allowances ask twice.
Stay next to the page
A small toolbar window for a fast check, or the browser side panel while you use a site.
Keep the phrase local
The same encrypted vault as the web wallet: a password unlocks it on that device, the 24-word phrase restores it anywhere.
Made for transactions. Clear about the rest.
One-time keys change which requests a wallet can answer. These are the boundaries the extension will keep.
- Works
- Connecting to sites and approving on-chain transactions, through EIP-6963 discovery and EIP-1193 requests.
- Refused
- Anything signed off chain, such as logins, typed data or permit messages. A one-time key cannot sign arbitrary text safely.
- One signer
- Use the extension or the web wallet for a phrase, never both. Their journals do not see each other.
When it ships
The order is in the roadmap: real keyhold operations in the web wallet first, then an encrypted backup that carries the key journal, then the extension. Announcements come from @merki on X and from this page.