Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RuntimeError('DataError: Encountered invalid prevhash') when signing with Trezor One #12

Closed
goodc0re opened this issue Feb 5, 2022 · 7 comments

Comments

@goodc0re
Copy link

goodc0re commented Feb 5, 2022

Actual behavior

RuntimeError('DataError: Encountered invalid prevhash')
when signing a spending tx with Trezor One

Steps to reproduce

Electrum Firo 4.1.5.1
Trezor One latest fw 1.10.5
Spend multiple old utxos that were masternode payouts and sign with Trezor One

@DNS
Copy link

DNS commented Nov 13, 2022

Probably related to this: #9
Also: https://firo.org/id/guide/common-problems.html

@goodc0re
Copy link
Author

The solution on the linked guide suggests to "select a maximum of five inputs". I am getting errors trying to spend just single inputs. Right-click on one single utxo, spend .. and it will result in errors signing. I am freezing all those to remember which ones I can't spend.
There are some utxos I can send out as a single utxo, sometimes even 2 together, rarely 3, and some I can not send out at all.

I also have utxos that were not masternode payouts that I can not move even on their own. (See other github issues I logged.)

@DNS
Copy link

DNS commented Mar 14, 2023

Seems the problem on the Trezor. Probably the hardware timed out early.

@goodc0re
Copy link
Author

Now the question is, will this issue be fixed before the Lelantus utxos on Trezor become unspendable at block height 1223500 due to migration to Spark?

@justanwar
Copy link
Member

@goodc0re I believe you are talking about Lelantus joinsplits to Trezor addresses? Those are still usable as inputs even after the migration window closes.

@justanwar
Copy link
Member

@goodc0re What is the current version of your Trezor One? Is it still unspendable?

@goodc0re
Copy link
Author

The masternode payouts have been spendable,

the only issues that remain unresolved at this time are #35 and #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants