REWARD: $250 – Trezor + MM-Geldbörse friert beim Signieren von Transaktionen ein

Home Foren Trezor Wallet REWARD: $250 – Trezor + MM-Geldbörse friert beim Signieren von Transaktionen ein

Ansicht von 11 Antwort-Themen
  • Autor
    Beiträge
    • #656059
      root_s2yse8vt
      Administrator
      Up
      0
      Down
      ::

      Hallo,

      Ich habe eine Trezor-verbundene MetaMask-Wallet, und immer wenn ich versuche, eine Transaktion mit meiner Trezor zu signieren, öffnet sich ein Fenster, in dem ich meine Schlüssel exportiere und die Passphrase eingebe. Dann verschwindet das Fenster und MM friert ein.

      ​

      Ich habe meine MM-Version auf 9.8.4 heruntergestuft. Wenn ich jetzt versuche, eine Transaktion zu unterschreiben, öffnet sich ein Fenster, ich exportiere und gebe die Passphrase ein, und MM friert NICHT ein, sondern die Transaktion steht noch aus, egal wie hoch das Gas ist.

      ​

      Vielleicht ist es auch hilfreich zu sagen, dass dies ein neues Trezor-Gerät ist. Mir ist aufgefallen, dass die Adresse meiner Trezor + MM-Geldbörse nicht in der Trezor Suite erscheint. Die Trezor + MM-Geldbörsenadresse erscheint nur in MM.

      ​

      Ich bin bereit, $250 in ETH an denjenigen zu zahlen, der mir hilft, dieses Problem zu lösen – KEINE DMs. Bitte antworten Sie mit Vorschlägen unten. Ich werde diesen Thread aktualisieren, um den Nachweis der Zahlung zu zeigen, sobald das Problem gelöst ist.

      ​

      Vielen Dank!

    • #656060
      brianddk
      Gast
      Up
      0
      Down
      ::

      Questions before we begin.

      1. Trezor T or Trezor 1?
      2. Is your Trezor Firmware at the latest?
      3. Assuming T1, did you critically examine your passphrase verification on T1?
      4. Are you transacting in ETH, or some other token?
      5. Are you transacting on the ETH chain (id: 1) or some other chain (poly)?
      6. Have you tried [FindETH](https://duckduckgo.com/?q=findeth+site%3Aforum.trezor.io) to get your Suite and MM derivations?

      Regardless of the answers, my first suggestions is to repeat your actions in the following configs:

      * Native OS with Chrome Browser + MM (no other extensions)
      * Native OS with Firefox Browser + MM (no other extensions)
      * Native OS with Brave Browser + MM (no other extensions)

      Like others mention. Probable cause is that you have an „off by one“ on your passphrase between Suite and MM. You may have typed `23UixRYu` in Suite and `23UixRYv` in MM

    • #656061
      cuoyi77372222
      Gast
      Up
      0
      Down
      ::

      There are only a few ways that the address can be different between MetaMask and Suite. It MUST be one (or more) of these:

      #1 You are not using a Trezor account in MetaMask. You are using the default MetaMask account instead of the „connect hardware wallet“ account.

      #2 You are not using the same seed phrase in the Trezor now as you were originally.

      #3 You are not using the same passphrase in the Trezor now as you were originally.

      #4 You did not choose the 1st address from the list in MetaMask when you choose the Trezor account from the long list of addresses.

      Only you can know which one(s) of these points happened, but the fact is it absolutely must be at least one of these that happened.

      And, until the address in MetaMask is the same as the Trezor address, you will not be able to sign a transaction with the Trezor.

    • #656062
      thatsamiam
      Gast
      Up
      0
      Down
      ::

      Regardless of the user error, Trezor software should never freeze or get into infinite loop. This software is managing people’s money so people can be their own bank.

      Trezor is not ready for consumers. This does not help the crypto eco system. We have to worry about hackers but we need to also worry about our own software when we want to do basic transactions.

      I avoid using my Trezor as much as i can. I just don’t trust the software nor the overly complicated UI.

      I am pretty sure this post will get downvited or deleted as has happened in the past when I complained about Trezor.

    • #656063
      NickeaTea
      Gast
      Up
      0
      Down
      ::

      The biggest red flag here to me is you saying that „my Trezor + MM wallet address does not appear in Trezor Suite. The Trezor + MM wallet address only appears in MM.“

      From your post it sounds like you are using hidden wallets with a passphrase. What you are describing makes me think that you may have setup your Trezor + MM wallet account with a mistyped passphrase.

      So you have this happening…

      * You created a hidden wallet within Trezor Suite with a passphrase ‚abcd‘
      * You connected your Trezor to MM to create the hardware wallet MM account but mistyped your passphrase as something like ‚abcdd‘ when you set it up. This resulted in you having a different wallet address than anything that would show up in Trezor Suite when you enter your planned passphrase ‚abcd‘ in Trezor Suite
      * Now whenever you go to perform a transaction with your Trezor + MM account you are entering the passphrase you expect it to be as ‚abcd‘ but in order to perform the transaction the passphrase it needs is ‚abcdd‘ because that is the passphrase that was accidentally used to create the linked account in MM

      I’m no Trezor/Metamask expert, but from the experience I do have this seems like it could be the simplest explanation for the issue you are experiencing. If this is the case, figuring out the ‚typo‘ version of your passphrase would be the challenge to help you solve the issue

    • #656064
      Jhat3k1
      Gast
      Up
      0
      Down
      ::

      Just go into metamask and „reset“ it.

      Don’t delete the entire thing.

      It will say, „this clears transaction history, etc, but not your balances“…or something close to that.

      Do that. Close browser entirely, and try again. Should work.

    • #656065
      TurbulentInternet
      Gast
    • #656066
      Crypto-Guide
      Gast
      Up
      0
      Down
      ::

      Sounds like you are just using the wrong passphrase… (This is extremely common user error ever since the feature was enabled by default)

    • #656067
      Momentary_Horizon
      Gast
      Up
      0
      Down
      ::

      I’ve had this happen before when I’m not connected to the correct hidden wallet.

    • #656068
      port888
      Gast
      Up
      0
      Down
      ::

      For the Trezor confirmation screen issue, try to make a new empty chrome profile, then install Metamask to that profile, and connect your trezor to this, and do all your defi shenanigans from this chrome profile. I find this combo to have the least problem.

      For the wallets not appearing issue, assuming the address you’re saying that do not appear on Trezor Suite have a passphrase on metamask, for Trezor Suite to show your passphrased addresses, you need to add them accordingly under „add a hidden wallet“. By default Trezor Suite only shows the set of non-passphrased address/wallet/account.

    • #656069
      kaacaSL
      Gast
      Up
      0
      Down
      ::

      Hi, you can also contact our Support team that would help you find out what’s the reason for not seeing the same address in Trezor Suite: [https://trezor.io/support/technical/issue/](https://trezor.io/support/technical/issue/)

      Though all the possible causes have been already mentioned here, u/cuoyi77372222 summed it up well.

    • #656070
      [deleted]
      Gast
      Up
      0
      Down
      ::

      [deleted]

Ansicht von 11 Antwort-Themen
  • Du musst angemeldet sein, um auf dieses Thema antworten zu können.