First of all: Amazing work done by Armory Dev's!
I am working with the Daemon (extending it at moment to support Tx Offline Signing, and Broadcasting)
And i got a Little problem at the moment, maybe some of the Devs can point me to the right direction to get it working.
The Broadcast is nearly ready to use in ArmoryD, the problem I got is:
New Transaction Requests over the same SourceAddress of the previous Tx will fail until the BDM gets notified about Confirmations
from BitcoinD.
Its like he want to spent the same TxInputs and then the Tx will fail in Broadcast. I saw ArmoryQT maintaining a combinedLedger.
(appending ZeroConf Ledger Entries to the combinedLedger)
But I have not see any relation to the BDM with the combinedLedger (maybe i am missing something, Its the first Project i am touching python.)
Or How ArmoryQT get it working to not fail on next Tx’s when the previous Tx’s isn’t already +1 Confirmation?
It seems to me that ArmoryQt “makes in some way a manual sync” to be able to realize a next TX.
Any point to direct me where I can follow the needs?
Thanks!
poOkie, I'm not sure what exactly the problem. It sounds like you might be running into the issue of making multiple offline tx and trying to sign them without first broadcasting one of them. Armory currently can't handle this situation, and you will have to create-sign-broadcast a tx before you can create the next tx (you can create the next tx, though it will probably be invalid).
Btw, there's a script the in extras directory called "cli_sign_txdp.py" which has example code for you. You may have found that, or may have already reimplemented it. Just wanted you to see it.