Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

[2.3.2] The TREZOR account can not sign "Multisignature aggregate modification transaction"★ #549

Closed
mizunashi opened this issue Jul 28, 2018 · 1 comment

Comments

@mizunashi
Copy link

mizunashi commented Jul 28, 2018

Expected Behavior

You can add a signer to an existing multi-sig account.

Current Behavior

There is a TREZOR account for the signer of the already existing multi-sig account.
In this case, this TREZOR account can not sign "Multisignature aggregate modification transaction".

You can sign the remittance without problems.

Possible Solution

Bugfix

Steps to Reproduce

  1. Prepare a multi-sig account with TREZOR as the signer.
  2. Add one person to the signer newly.
  3. A signature request arrives for an existing signer, but you can not sign from the TREZOR account and you get an error.

Details

Error message is here.

2018-07-28 9 04 58

@mizunashi mizunashi changed the title [2.3.2] The TREZOR account can not sign "Multisignature aggregate modification transaction" [2.3.2] The TREZOR account can not sign "Multisignature aggregate modification transaction"★ Aug 26, 2018
@cryptoBeliever
Copy link

Same as #612

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

No branches or pull requests

2 participants