-
Notifications
You must be signed in to change notification settings - Fork 60
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
Python3 Bug prevents signing multisig txs #18
Comments
By the way, the above xpub is taken from BIP32 specification document |
@kyuupichan I've pushed up a branch and verified the above function works in both python2 and python3. Please pull down this branch and test when you get a chance. Working on adding unit tests. |
@ngmiller I've checked out the branch and things seem fine. Multisig txs are signed fine in Electron Cash but as I point out elsewhere there is a SIGHASH_FORKID problem when sending it. I've not had time to examine in detail, but my suspicion is a firmware bug. It could be an Electron Cash bug too though. If you want to know how to reproduce that I can write an explanation. |
Are you certain multisig txs are being signed with SIGHASH_FORKID when the coin is BCH? |
@kyuupichan We are looking into the SIGHASH_FORKID as a separate issue, since the specific function you mentioned in this issue has been addressed. I am working on this today. |
Problem is simple to reproduce:
The bug is tools.py/b58decode getting confused between strings and binary types. I suggest replacing with the trezorlib implementation that I've verified works fine.
That is unlikely to be the only function in that file with such a bug; please add tests for them
The text was updated successfully, but these errors were encountered: