Skip to content
This repository was archived by the owner on Nov 23, 2023. It is now read-only.

Fix Signing of Multisig Testnet Transactions#100

Closed
nickfogle wants to merge 1 commit intotrezor:masterfrom
nickfogle:master
Closed

Fix Signing of Multisig Testnet Transactions#100
nickfogle wants to merge 1 commit intotrezor:masterfrom
nickfogle:master

Conversation

@nickfogle
Copy link

@nickfogle nickfogle commented Jan 10, 2018

This addresses the "Invalid network value" error described in #81 (comment).

When using https://connect.trezor.io/4/connect.js and attempting to sign a multisig testnet transaction, HDNode.fromBase58() isn't passed any network data and defaults to mainnet.

34756250-84eafc9a-f597-11e7-91f1-fd2ae52ea757

Fixes "Invalid network version" where multisig testnet transactions defaulted to mainnet.
@karelbilek
Copy link
Contributor

nice fix! thx

@nickfogle
Copy link
Author

Hi @karel-3d, any idea when this fix might make it to production? We're currently supporting multisig signing on testnet by loading the popup folder with this fix locally and installing a modified chrome extension to whitelist our domain.

Do you think it would be faster to just create a PR to get our domain whitelisted rather than waiting for this PR to be merged? Thanks!

@prusnak
Copy link
Member

prusnak commented Jan 31, 2018

@szymonlesisz Please review and merge and deploy to v4 if it's OK

@prusnak
Copy link
Member

prusnak commented Feb 1, 2018

Merged and deployed to https://connect.trezor.io/4/

@nickfogle Could you please test if that works for you? Please reopen if there are outstanding problems.

@prusnak prusnak closed this Feb 1, 2018
@nickfogle
Copy link
Author

Thanks @prusnak! I just sent a transaction over testnet and it's working great!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants