-
Notifications
You must be signed in to change notification settings - Fork 12
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
[BUG] IsPayToColdStaking tries to parse empty rawTX with Trezor api #9
Conversation
Currently testing Win 10 produces the following error: |
This is probably caused by a recent change in trezorlib. |
Okay the application now launches (python 3.9) after running "pip install trezor==0.11.1" (installed version was 0.12.2) however does not connect to any servers. Also attempted downgrading to python 3.8 and following packages with same result: The latest binary connects ok and I've disabled firewall etc and however I can't get either this branch or "master branch" or "2019_cold_staking_ledger" to connect so possibly something wrong with my config. |
I've also tried the "PyQt-5.9" release on Python 3.7.0 with the same result: https://github.com/PIVX-Project/PET4L/archive/v0.1.0-c.zip The wallet is able to check for new version and prompt for update so network stack seems fine however errors connecting to RPC server so perhaps there another dependency issue (binary version connects fine to same servers). 2020-11-12 18:52:07 : Checking PET4L version... |
Mhm quite strange. Maybe an issue with either Anyway... I tested this with Trezor Model T on a Windows VM, and it works here. I've built binaries and uploaded them here for testing: |
Great work @random-zebra ! I've tested the binary and was able to send the full balance from address #1 to address #2. I'll also test on the original wallet and report back if any issues. Thanks for your help! |
Glad it worked! Cheers 🥃 |
Just tested the binary with Ledger Nano S and address 0 is correct however subsequent addresses differ from Ledger Live so any balances in change addresses previously used by Ledger Live transactions are not displayed. This may be due to Ledger Live using path m/44'/77'/0' as opposed to Trezor etc which uses m/44'/119'/0'. Perhaps an option is needed to select the correct path. |
@jp-solutionz have you switched |
Closes #8