Open mammique opened 12 years ago
Hi Camille,
This happens very occasionally for me, too. Unfortunately, it's so rare that I can't reproduce it in order to debug it. In your case, it looks like a block was received just as you were sending the transaction, and maybe that interrupted the process...?
Either way, you don't have to worry. Everything should be smooth with your wallet. The only issue you might run into is if it happens again, you'll think the transaction didn't through and you'll try to send it again (or a different tx) and the network won't accept that, either -- because Armory is trying to spend coins the network thinks your already spent. However, this works itself out after you get 1 confirmation, and everything will be back to normal. If this happens consistently, please let me know.
OK, I'm reassured :-) I tell you if it happens again. Thanks!
Camille.
Hi all, I had a weird warning when sending Bitcoins from an offline wallet recovered from paper backup (I was testing the process). After broadcasting the signed transaction via the watch-only wallet, I had a popup and stdout warning:
Added new blocks to memory pool: 1 Signature 0 is valid! (ERROR) ArmoryQt.py:1922 - Transaction was not accepted by the Satoshi client (ERROR) ArmoryQt.py:1923 - Raw transaction: (ERROR) (PPRINT from /usr/share/armory/ArmoryQt.py:1924)
However the transaction seemed to be validated anyway later on, I made an extra transaction to see if I could reproduce this warning, but everything seemed to go fine this second time... Do I have to worry about my wallet?
Thanks,
Camille.