Home Fora KeepKey Keepkey ist nach dem letzten Firmware-Upgrade und dem Auslaufen der Chrome-Erweiterung durcheinander geraten

Viser 10 svartråde
  • Forfatter
    Indlæg
    • #188974
      root_s2yse8vt
      Keymaster
      Up
      0
      Down

      Ich habe seit ein paar Jahren einen Keepkey im Kühlhaus aufbewahrt. Kürzlich habe ich ihn herausgeholt, nur um herauszufinden, dass es keine einfache Möglichkeit gibt, auf meine Münzen zuzugreifen. Ich hatte eine Reihe von verschiedenen Münzen (btc, bch, eth) für meine Kinder, Schwester, Mutter, etc.

      Nach ein paar Stunden Arbeit habe ich herausgefunden, dass Shapeshift die Google-Chrome-App abgeschaltet hat und es unmöglich gemacht hat, sich mit ihr zu verbinden. Ich habe es von mehreren Rechnern mit unterschiedlichen Betriebssystemen aus versucht. Am weitesten kam ich, als ich die PIN eingab, um festzustellen, dass die Konten ewig geladen wurden. Sie wurden auch dann nicht geladen, wenn ich sie über Nacht laden ließ.

      Schließlich aktualisierte ich die Firmware und gelangte in die Wallet über [beta.shapeshift.io](https://beta.shapeshift.io), nur um festzustellen, dass die Kontonamen, die zuvor in der Chrome-App eingestellt waren, verloren gegangen sind. Alles ist jetzt “Konto Nr. 1”, “Konto Nr. 2” und so weiter.

      Jetzt weiß ich nicht mehr, welche Münzen zu wem gehören.

      Gibt es eine Möglichkeit, die Firmware wieder auf eine ältere Version zurückzusetzen? Wie würde ich vorgehen und zu welcher Version muss ich zurückkehren, bevor Shapeshift alles durcheinander gebracht hat?

      Gibt es eine Möglichkeit, eine kompatible alte Google-Chrome-Erweiterung zu installieren, die mit einer alten Keepkey-Firmware funktioniert?

      Ich danke Ihnen im Voraus für Ihre Zeit. Die Lösung dieses Problems bedeutet die Welt für mich, wie Sie sich vorstellen können:)

    • #188975
      User
      Gæst
      Up
      0
      Down

      I decided to give up on identifying which wallet/account belonged to whom and will do some guessing and some asking instead.

      I salvaged the balances as described in this post [https://www.reddit.com/r/keepkey/comments/gok41d/keepkey_derivation_path/gc1c1li?utm_source=share&utm_medium=web2x&context=3](https://www.reddit.com/r/keepkey/comments/gok41d/keepkey_derivation_path/gc1c1li?utm_source=share&utm_medium=web2x&context=3)

      I imported the keepkey seed into:

      Eletrum for BTC – derivation path: m/44'/0'/0′ (incrementing the X in m/44'/0'/x' to find different accounts)

      [myetherwallet.com](https://myetherwallet.com) for ETH – derivation path: m/44'/0'/0′ (incrementing the X in m/44'/60'/x'/0 to find different accounts)

      I'm about to do Electron for BCH. Derivation path yet to figure out

    • #188976
      User
      Gæst
      Up
      0
      Down

      We all experience this. It's terrible. As long as you have your 12 word seeds you can easily purchase another Hardwallet and use that same 12 words.

      Main question here is, what happens when shapeshift dies? This beats the purpose of a Hardwallet!

      I've been using my Keepkey since early 2017 every update gets worst. I've recently moved all my coins to another more trustworthy brand that's completely offline.

      Good luck!

    • #188977
      User
      Gæst
      Up
      0
      Down

      I have same issue I found I can connect to shapeshift with Android phone using Chrome browser

    • #188978
      User
      Gæst
      Up
      0
      Down

      Okay, there's a lot to unpack here. I'll try to answer them in no particular order:

      > Is there a way to install a compatible old google chrome extension that will work with an old keepkey firmware?

      Answer is yes it is possible. I've done it. See my [KKClient fork here](https://github.com/greatwolf/KKClient)

      >Is there a way to revert the firmware back to an older version? How would I go about it and which version do I need to revert to before shapeshift messed it up?

      Yes there is a way to revert back to an older firmware. You can do this by using [python-keepkey command-line interface](https://github.com/keepkey/python-keepkey) and downloading an older firmware [release here](https://github.com/keepkey/keepkey-firmware/releases). And then using the command:

      python.exe keepkeyctl firmware_update -f firmware.keepkey.bin

      First thing, before doing any of this, make sure you have a backup of your seed safe somewhere. In case something goes wrong and the firmware loading wipes your device you don't lose your funds.

      Second, even if you do revert back to the old version, I don't think it'll help you solve anything. If I understand correctly your main issue is that you've lost the names of the account label for coins that's in the chrome extension.

      That information isn't stored on your KeepKey device. It's actually stored as encrypted metadata using api.blockcypher.com RESTful api database. The key used to encrypt the metadata is derived from the seed in your KeepKey while the metadata is stored with blockypher.com.

      Now the problem is that the shapeshift `masterapikey` that the chrome extension uses is defunc'ed. ie. blockcypher is rejecting that `masterapikey` and it's also one of the reasons the chrome app fails to load properly. That `masterapikey` is use to create child apikeys on the fly that's then used to store the encrypted metadata for that particular seed.

      But there could still be a silver-lining here. From my testing, even though the shapeshift `masterapikey` no longer works, the child apikeys previously created from that may still be valid. If it is you can manually fish out the encrypted metadata information by making REST request to it using something like apitester.com.

      It can be found under ‘Settings' -> ‘Contact Support' called Api Token but to do that you need to get the Chrome App to load successfully in the first place. It's a bit of a catch-22.

      But the short of it is, yes it is possible to get Chrome App working again but you'll have to make changes to the extension source to fix the loading issues. For this it'll help if you already know javascript, know how REST request works or already have some development knowledge.

    • #188979
      User
      Gæst
      Up
      0
      Down

      my KK got emptied on this upgrade. had to use seed keys to get coins back and set it up as new one.

    • #188980
      User
      Gæst
      Up
      0
      Down

      Fuuuuuuuuck!

    • #188981
      User
      Gæst
      Up
      0
      Down

      I can’t even wipe my keepkey.No link that works!!
      This device is now junk.Shameful.

    • #188982
      User
      Gæst
      Up
      0
      Down

      This is reason for a lawsuit.
      Please keep us posted on your progress.

    • #188983
      User
      Gæst
      Up
      0
      Down

      Just reuse you seed words once you have updated your device and connect via Android chrome

    • #188984
      User
      Gæst
      Up
      0
      Down

      Hey u/besnadlesen – Please reach out to our support team to troubleshooting this issue at: https://shapeshift.zendesk.com/hc/en-us/requests/new

Viser 10 svartråde
  • Du skal være logget ind for at svare på dette indlæg.