greatwolf/kkclient

Chrome application that communicates with KeepKey hardware-wallet.

kkclient's Issues

Conflicting Application: There is another application running that conflicts with keepkey client

Version 87.0.4280.88 (Official Build) (64-bit)

KeepKey v7.1.0 not being detected

I upgraded my KeepKey to firmware 7.1.0 (on bootloader 2.0.0) and KKClient is no longer detecting the device.

Here is what I see in Chrome's console:

Keepkey Chrome Application Wallet: 6.6.4
Background.js:332 timer done
Background.js:259 looking for HID devices...
Background.js:269 []
Background.js:279 looking for WebUsb devices...
Background.js:287 [{"device":0,"manufacturerName":"KeyHodlers, LLC","productId":2,"productName":"KeepKey - NTICompass Inc.","serialNumber":"<serial goes here>","vendorId":11044,"version":256}]
Background.js:289 Initializing WebUsb KeepKey
Background.js:292 dispatching
Background.js:9626 WebUsb connecting Object
Background.js:9431 WebUsb openDevice Object
Background.js:9439 WebUsb setConfiguration Object handle: {handle: 1, productId: 2, vendorId: 11044}
Background.js:9445 WebUsb setConfiguration failed
Background.js:9446 Error setting device configuration.

Then later on, I see:

sending message
Background.js:13406 device --> proxy: [Features]
 {
    "vendor": "keepkey.com",
    "major_version": 7,
    "minor_version": 1,
    "patch_version": 0,
    "bootloader_mode": null,
    "device_id": "<my device id>",
    "pin_protection": true,
    "passphrase_protection": false,
    "language": "english",
    "label": "NTICompass Inc.",
    "coins": [],
    "initialized": true,
    "revision": "64306231346639333963346166663838306237383364303437616436396238643631623036616638",
    "bootloader_hash": "9bf1580d1b21250f922b68794cdadd6c8e166ae5b15ce160a42f8c44a2f05936",
    "imported": false,
    "pin_cached": false,
    "passphrase_cached": false,
    "policies": [
        {
            "policy_name": "ShapeShift",
            "enabled": true
        },
        {
            "policy_name": "Pin Caching",
            "enabled": true
        },
        {
            "policy_name": "Experimental",
            "enabled": false
        },
        {
            "policy_name": "AdvancedMode",
            "enabled": false
        }
    ],
    "model": "K1-14AM",
    "firmware_variant": "KeepKey",
    "firmware_hash": "d8b2b43eada45ded399f347289750a7083081186b37158b85eab41a38cbc6e50",
    "no_backup": false,
    "typeName": "Features"
}
Background.html:1 Unchecked runtime.lastError: The message port closed before a response was received.

This is working on a previous firmware version, but not this one.

Monero support?

Hi, is there any possibility of Monero (XMR) being supported in the future with custom firmware? The KeepKey firmware page on GitHub has Monero disabled in the CMakeLists for the original Trezor source and the CMake flags. I was able to build custom firmware with Monero enabled (merged Monero related updates from the Trezor source) and was able to get it pushed and running on the KeepKey but I have no way of interacting with it.

Sending bug

I'm a long-time user of this client, thanks for it, but suddenly I've run into a (new?) issue.

When I go to my main BTC account, there was also a very small Bitcoin Gold balance displayed. The problem is that now when I try to send BTC it will not send the transaction because it thinks its above my balance, which is false. When I click the 'Send Maximum' button it shows the balance of the Bitcoin Gold and not the BTC. So this bug is causing the BTC and BTG balance to be swapped, and thus prevents me from sending BTC.

In order to solve this issue, I tried transferring all Bitcoin Gold to another wallet. But after that the Bitcoin Gold balance just displays 0 (zero), and the maximum BTC I can send is also 0 now. So this didnt help at all.

In the account overview screen my BTC balance is displayed correct, and also in the header of the sending page. So it seems just the maximum variabele that gets set incorrectly.

bitcoinfees.earn.com API is giving bad data on fees

bitcoinfees.earn.com API is giving bad data on fees

Problem: url: 'https://bitcoinfees.earn.com/api/v1/fees/recommended', is old data and incorrect fees for current market conditions on 20 April 2021.

Rather use a new provider and configure for url: 'https://mempool.space/api/v1/fees/recommended', (from https://mempool.space/api)

Chrome Error: window.localStorage is not available in packaged apps. Use chrome.storage.local instead.

Version 87.0.4280.88 (Official Build) (64-bit)