You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
A user reported he is not able to get his funds out of a Counterwallet multisig composed out of 3 armory addresses.
Apparently Armory doesn't support signing transaction formats from other applications. Their developer said "Counterwallet can implement Armory's transaction format, so Armory should be able to treat it like signing any other Armory transaction."
Can this be done? If not, can we add a message somewhere that multisig with Armory is currently not supported?
NOTE: I've been trying to test this myself but can't get Armory to work :/. Address balance keeps getting reset to 0 (even after rebuild and rescan). For some reason Armory can't find the transactions associated with the addresses in the wallet :(. If needed I can provide the full report from the user who reported the multisig issue
A user reported he is not able to get his funds out of a Counterwallet multisig composed out of 3 armory addresses.
Apparently Armory doesn't support signing transaction formats from other applications. Their developer said "Counterwallet can implement Armory's transaction format, so Armory should be able to treat it like signing any other Armory transaction."
Can this be done? If not, can we add a message somewhere that multisig with Armory is currently not supported?
NOTE: I've been trying to test this myself but can't get Armory to work :/. Address balance keeps getting reset to 0 (even after rebuild and rescan). For some reason Armory can't find the transactions associated with the addresses in the wallet :(. If needed I can provide the full report from the user who reported the multisig issue
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: