Releases: keepkey/keepkey-client
Release list
v0.0.35
KeepKey Client 0.0.35 (Chrome).
Changes since 0.0.34
- Masking (#92):
window.ethereumnow mounts for legacy dApps (respects masking defaults). When masking is ON,window.ethereum/window.xfi/window.solanaare force-clobbered to KeepKey even when MetaMask/Phantom are installed. - Connection (#93): "Vault not running" is surfaced to dApps as a clean error instead of silently hanging.
- Portfolio (fix): donut chart uses canonical brand colors from the discovery service (ETH #627EEA, USDT green, etc.) instead of a hashed palette.
Install
Chrome: unzip keepkey-client-chrome-0.0.35.zip, load unpacked at chrome://extensions (Developer mode).
Firefox build intentionally disabled in this repo.
v0.0.34
KeepKey Client browser extension v0.0.34 (Chrome / Chromium, Manifest V3).
Install
Download keepkey-client-0.0.34-chrome.zip, unzip, then chrome://extensions → enable Developer mode → Load unpacked → select the unzipped folder.
Highlights
- Side-panel UI overhaul — KeepKey-gold design system, scam-token suppression, token auto-discovery, shared AssetIcon, portfolio data layer, asset-detail hero, dust-precision (8-decimal) balances, spinning-KeepKey loaders.
- Non-EVM multi-account — UTXO / Cosmos / Solana account management.
- Connection hardening — durable vault pairing; dApp
eth_requestAccountsnow survives MV3 service-worker eviction (init-on-demand). - Explorer links fixed — EVM sends/swaps now deep-link the txid on the success screen instead of showing a bare hash.
- Test foundation — vitest suite expanded to 91 unit tests (rpcFailover, chainConfig, fetchUtils, fee/spam/derive paths).
Reconciliation
This release reconciles the develop/master divergence and applies #64 (drop the chrome.alarms permission — uses setTimeout for the tx-drop check instead, avoiding a Chrome Web Store re-consent wall). Manifest permissions: storage, tabs, commands, sidePanel.
⚠️ Firefox not included
Firefox builds are intentionally disabled in this version. The dApp approval UI moved to the Chrome-only side panel during the popup→side-panel migration, and a Firefox-specific approval surface (popup shim / sidebar_action) hasn't been built yet — a Firefox build would have no usable approval UI. Chrome/Chromium only until that lands.
Verification
type-check 15/15 · 91/91 unit tests · production build clean · shipped manifest confirmed (v0.0.34, MV3, no alarms).