Re: [ANN] Armory Multi-Sig with Simulfunding [BOUNTY 0.03 per bug]
by
helgabutters
on 18/07/2014, 22:15:03 UTC
Sorry for the delay, works been rather busy the past few days so I haven't been able to put in as much time as I'd like. Also, could you give me some insight on which ones I've submitted that are definitely not bugs and a few that you aren't sure of? I'm just trying to gauge what exactly you want and what I can safely not worry about finding/reporting.
1) You can't "importprivkey" as it will always error. I tried both hex and base58
2) There is some calculation error in listaddrunspent. You can see once you hit 3 characters in the string, it will still say 3 once you've put in a fourth and continue counting up from there.
4) If you have a very long wallet description, the "Delete Wallet Options" window gets overly large and it won't show the whole thing. It also can't be resized down at all (This happens on Win and Linux, haven't tested OSX)
5) You can't "verifysignature" as it always interprets the "-----" as an argument for armoryd (and the only compatible signature types have "-----" in them). I've tried in just the command line and in a bash script to no avail. If this is just an issue with my understanding of the command or how to properly give the command the information, please let me know.
Address: mkT61iEMnSSFgoCJkXFqbV9SiMHKnHDktN Message: This is to test armoryd verifysignature for mkT61 Base64 Sign
8 ) This one I'm not sure of the cause. I thought it was originally because the wallet was locked but that isn't the case. One of my wallets if I try to "getledger" or "getledgersimple" I will get an "AttributeError":