Errors on creating transactions

[btcpop.co]

I've some inputs on p2sh addresses and I'm not able to spend them.

Was really a pain to move coins from a wallet with 7500+ Inputs when there 3 Inputs that causes issues...

Code:

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 930, in createTxAndBroadcast
    ustx = self.validateInputsGetUSTX()
  File "/usr/lib/armory/ui/TxFrames.py", line 884, in validateInputsGetUSTX
    lockTime=TheBDM.getTopBlockHeight())
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2501, in createFromTxOutSelection
    return self.createFromPyTx(thePyTx, pubKeyMap, txMap, p2shMap)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2429, in createFromPyTx
    sequence=txin.intSeq, inputID=count))
  File "/usr/lib/armory/armoryengine/Transaction.py", line 1218, in __init__
    raise KeyDataError('Must give pubkey map for singlesig USTXI!')
KeyDataError: Must give pubkey map for singlesig USTXI!

Code:

(ERROR) Traceback (most recent call last):
  File "/usr/lib/armory/ui/TxFrames.py", line 930, in createTxAndBroadcast
    ustx = self.validateInputsGetUSTX()
  File "/usr/lib/armory/ui/TxFrames.py", line 884, in validateInputsGetUSTX
    lockTime=TheBDM.getTopBlockHeight())
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2501, in createFromTxOutSelection
    return self.createFromPyTx(thePyTx, pubKeyMap, txMap, p2shMap)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2447, in createFromPyTx
    return self.createFromUnsignedTxIO(ustxiList, dtxoList, pytx.lockTime)
  File "/usr/lib/armory/armoryengine/Transaction.py", line 2345, in createFromUnsignedTxIO
    raise ValueError('Supplied inputs are less than the supplied outputs')
ValueError: Supplied inputs are less than the supplied outputs

Inputs are on the BCH chain and are still viewable on blockexplorers, I did several rescans and also full rebuilds.
As those are p2sh addresses its not trivial to just export the privkey and spend via another wallet.

[droark]

Is this a Bcash transaction? If so, Armory doesn't support Bcash, and only supported it just enough at its creation to allow people to temporarily send transactions, or otherwise move their funds to a wallet that will support it. I don't know offhand if Armory is able to craft functional transactions anymore. I'm guessing not, especially with the upcoming fork.

[goatpig]

What version are you using?

[btcpop.co]

0.96.4-Beta

@Droak no not Bcash, but Bitcoin Cash transactions and they work with Armory, I provided a ( non clean and not optimal ) hack for BitcoinABC so Armory can connect and keeps connected, but even without, it would work to create and sign transactions, you would just need to manual broadcast the raw transaction.

Edit:
I built my self and also tried the latest .deb ( armory_0.96.4_amd64_gcc4.7_noasm.deb )

[goatpig]

You are showing 2 errors, are both of these happening together?

[btcpop.co]

You are showing 2 errors, are both of these happening together?

No, depends on what inputs I select in coin control... I've 3 inputs left 1 shows the first error and the other 2 the 2nd error.
I tried them also 1 by 1.

It's a huge wallet with currently 56k addresses, It had over 7500 Inputs when I started to move out ( Moved them to p2pkh addresses for easier splitting on the possible split happening today ).

I'm still receiving on that wallet else I would be okay to send it to you so you could easier debug, I don't care too much about the 3 inputs stuck, just annoying to move in the feature as I always would need to do coin control and deselect the inputs with issues.

I could try to import the privkeys in a new armory wallet and see if it will work then, but not sure if armory would "create" the p2sh version then or just p2pkh...

[goatpig]

1) When are these tx failing? At signing? At creation? Are these offline transactions?

2) The second error seems to have to do with the use of the MAX feature. Try turning that off, see if you can create the tx.

I'm still receiving on that wallet else I would be okay to send it to you so you could easier debug

Depending on when the bugs occur, I could possibly fix this with just a watching only wallet.

I could try to import the privkeys in a new armory wallet and see if it will work then, but not sure if armory would "create" the p2sh version then or just p2pkh...

Import aren't scanned for p2sh schemes, only p2pkh.

[btcpop.co]

1) When are these tx failing? At signing? At creation? Are these offline transactions?

2) The second error seems to have to do with the use of the MAX feature. Try turning that off, see if you can create the tx.

I'm still receiving on that wallet else I would be okay to send it to you so you could easier debug

Depending on when the bugs occur, I could possibly fix this with just a watching only wallet.

I could try to import the privkeys in a new armory wallet and see if it will work then, but not sure if armory would "create" the p2sh version then or just p2pkh...

Import aren't scanned for p2sh schemes, only p2pkh.

creation and offline wallets.
Inputs are on the BCH chain but that shouldn't matter ( would just matter when debugging with a watch only copy ).

[goatpig]

First, you should try the current state of the testing branch. If that fails, I can at least fix the errors at tx creation with the WO wallet or the public keys for the relevant outputs. Otherwise try to these tx without using the MAX feature.

[btcpop.co]

First, you should try the current state of the testing branch. If that fails, I can at least fix the errors at tx creation with the WO wallet or the public keys for the relevant outputs. Otherwise try to these tx without using the MAX feature.

I'll try tomorrow, currently busy with other work.