I've been having some trouble with bitcoind and Armory and my online wallet isn't loading (I may submit another post later on addressing this issue). In the event that I can't find a solution what is the safest/easiest way to move my coins from my offline cold storage wallet?
Thanks in advance.

Tried sending from Electrum but got this message:

error: The transaction was rejected by network rules.  (16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation))

I imported my Armory addresses into a watch only Electrum wallet and my Plain Base 58 Private Keys into an offline Electrum wallet.
I then made a transaction and signed it offline but get the above error immediately after trying to broadcast.

I seemed to be running into this problem with Armory too. I could sign the transaction offline but when I went to broadcast it to the bitcoin network it rejected it and the transaction never showed up blockexplorer.info. I had made a few successful transactions in Armory earlier in the day.

Any suggestions or ideas?

Thanks.

Thanks for your help Goatpig.

I'm using Armory wallet 0.91.2. with a watching online and cold storage offline setup.

I was able to make a couple of successful bitcoin transactions from Armory but then something went wrong and the network started rejecting my new ones. I was able to create new transactions but they weren't being confirmed and when I searched for the TxID I couldn't find that the network had even picked them up. (I remember a pre-broadcast pop up box about Armory padding and was unsure how to answer. I think I answered 'No' sometimes and 'Yes' other times)  Then I started having bitcoind problems.

I had Armory running bitcoind in the background on a linux OS but bitcoind is no longer working and I get the ": Error opening block database.
Do you want to rebuild the block database now?." error message when opening my online Armory. I haven't rebuilt the block database yet as my CLI/Linux skills aren't the best.
Does this mean I'd have to download the entire blockchain again?

---------------------------------------------------------------

Here's part of the debug log:
ActualTimespan = 1156544  before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 1209600    nActualTimespan = 1156544
Before: 1c0f675c  000000000f675c00000000000000000000000000000000000000000000000000
After:  1c0eba64  000000000eba64df7df7df7df7df7df7df7df7df7df7df7df7df7df7df7df7df
*** System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
Loaded 40319 blocks from external file in 10793ms
Reindexing block file blk00001.dat...
ProcessBlock: ORPHAN BLOCK, prev=00000000000064ac7c1b57c1d3b4fd3a3aeb2f26c96c2dde853eef230a271048
ProcessBlock: ORPHAN BLOCK, prev=00000000000069cf03c847d7d1d58b44474021b31dc65a8e83fd3a08e60a768c
ProcessBlock: ORPHAN BLOCK, prev=0000000000001a86c6e9a3bcf7fd86b054879fc31345ec032b6495fecbc7ab9b
ProcessBlock: ORPHAN BLOCK, prev=00000000000013aa7f91d6578c8f8db27611f00e7979e5bd2a763c01bc54d55e
(lots more of these orphan blocks here) then...
msghand thread interrupt
opencon thread interrupt
addcon thread interrupt
ProcessBlock: ORPHAN BLOCK, prev=00000000000054347fe0994fd78eb7cb7b619e62a0cb64d8f552688d50f9beb2
Flush(false)
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended               0ms
StopNode()
dumpaddr thread stop
net thread interrupt
Flushed 1358 addresses to peers.dat  48ms
2017-03-27 00:57:03

2017-03-27 00:57:03 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200)
2017-03-27 00:57:03 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014
2017-03-27 00:57:03 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-03-27 00:57:03 Default data directory /home/xxxx/.bitcoin
2017-03-27 00:57:03 Using data directory /home/xxxx/.bitcoin/
2017-03-27 00:57:03 Using at most 125 connections (1024 file descriptors available)
2017-03-27 00:57:03 Using 4 threads for script verification
2017-03-27 00:57:03 Using wallet wallet.dat
2017-03-27 00:57:03 init message: Verifying wallet...
2017-03-27 00:57:03 ERROR: CDBEnv::Open : Error -30974 opening database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2017-03-27 00:57:03 Moved old /home/xxxx/.bitcoin/database to /home/xxxx/.bitcoin/database.1490576223.bak. Retrying.

-------------------------------------------------


Yes, I saw my balance in Electrum and was even able to crate a transaction online with Electrum and sign a transaction on the offline cold storage Electrum wallet after importing my Armory private keys.The transaction was rejected by the network when I tried to broadcast it from online Electrum. I got this error message: "error: The transaction was rejected by network rules.  (16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation))"


Thanks again!

If you have private key of your bitcoin address you can import that key to bitcoin mobile wallet or online sites like spectrocoin, you will able to access your coins within few minutes without downloading blockchain.

I strongly advise you to update everything. You are using dated and obsolete software.

As for your transactions failing to broadcast, there has been a few changes to signature serialization in the past to reduce malleability. While any Armory pre 0.92 can sometimes create properly serialized signatures, it will more often than not create invalid ones.

Around the time these serialization rules were added, there was a few bots grabbing the bad transactions and reserializing the signatures to the proper format as a public service. I don't know that these bots are active anymore. At any, you will have a hard time broadcasting anything with that setup.

0.92.3 had a x86 release for Windows and can sign for up to 0.95.1. I don't have these so you will have to look for them on your own.
0.93.2 offline bundles are available in x86 for Ubuntu and RPi armv7.

You should still update your Bitcoin node regardless.


I do not know, I have no idea what Electrum is doing with those keys. You should ask them directly.