-
Notifications
You must be signed in to change notification settings - Fork 72
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
Co-signatory of a (2 of 3) multisig account cannot sign an aggregate bonded tx (for creating a multi-level multisig) #1350
Comments
@AdriaCarrera I created the Multi level multisig account and initiated teh aggregate transaction but i dont see any pop or any confirm button . can you please check |
@bassemmagdy I still can reproduce it. I am taking one multisig account with 2co-signers (ch1, chm2), convert chm2 co-signer into multisig with 2 co-signors (ch3, ch4). Initiating transaction from ch1 and expect to receive aggregate transaction in ch3 and ch4, but unsuccessfully. |
* fix #1350 * update function return type * fix sonarcloud bugs * fix code smell * refactor getMultisigChildren * decrease cognitive complexity * update sdk version * adding unit tests * adding docs * remove logs * adding unit test * adding docs * fix naming typo * fix feedback issues
There is a possible issue in Symbol Desktop Wallet where a multisig enabled account cannot sign an aggregate bonded transaction to become a cosignatory of a multi-level multisig account. Now, I'm not sure if this is an issue in the core code or in the desktop client.
Background:
I'm trying to setup a harvesting node on AllNodes, and as part of the process, I have to sign an aggregate bonded transaction created by an account managed by AllNodes. According to the instruction of AllNodes, I should be able to sign this transaction in Symbol Desktop Client by:
The problem:
There's no "confirm" button. (See screenshot)
This transaction details is also shown for all of my cosignatory accounts; no confirmation button.
Expected behaviour:
Screenshots:
TX Hash in screenshot: C770144F3EFCC5B82F69F9C7B5DD4555798387D7D4904C276109F4512DDECFA7
If more information is needed, I'd be happy to share.
The text was updated successfully, but these errors were encountered: