Author

Topic: Bug report: Simulfund not working (Read 175 times)

legendary
Activity: 3794
Merit: 1375
Armory Developer
November 15, 2018, 11:05:07 AM
#2
Fixed in testing, will be in the RC for 0.96.5
jr. member
Activity: 70
Merit: 2
September 27, 2018, 10:28:24 AM
#1
Continuing poking Armory multisig, this post documents a bug in Armory's Simulfund promissory note feature.

Tested on:
  • latest state of testing branch, compiled from source on linux mint 19
  • 0.96.4 on windows 10

To recreate:
  • Under MultiSig menu, click simulfund Promissory Note
  • In the Create Simulfunding Promissory Note dialog, enter needed fields: Source of Funding, amount, fee, funding destination address:
  • Click continue, and the bug is manifested: nothing happens and the log file has the following error


Code:
(ERROR) Traceback (most recent call last):
  File "/home/testuser/BitcoinArmory/ui/MultiSigDialogs.py", line 3518, in doContinue
    pubKeys = {utxoScrAddr: aobj.binPublicKey65.toBinStr()}
AttributeError: 'NoneType' object has no attribute 'binPublicKey65'

Traceback (most recent call last):
  File "/home/testuser/BitcoinArmory/ui/MultiSigDialogs.py", line 3518, in doContinue
    pubKeys = {utxoScrAddr: aobj.binPublicKey65.toBinStr()}
AttributeError: 'NoneType' object has no attribute 'binPublicKey65'

Though I may be completely wrong, looking at the MultiSigDialogs.py around the break line, it reminds me a lot of the previous bug, because here too there's a failed attempt to go over a range of pubkeys.


Jump to: