One address with 770 small transactions, Armory and Electrum can't handle - Help

[Moria843]

Have 5+ BTC in one address made up of 770 small transactions. I want to move the entire contents to a new address. Armory will only allow me to send 0.1 BTC at a time (says too many small transactions if I go bigger) and the fees to transfer all 5 BTC would be outrageous. I tried importing into Electrum and when I hit the send key it just sits there and processes forever when I try to send it all. I even tried sending just 0.5 BTC from Electrum and it does the same thing.

Is there a wallet that can handle?

Would importing into an online wallet work better?

[Andre_Goldman]

kip bug Armory ... they deserve it

[swogerino]

Have 5+ BTC in one address made up of 770 small transactions. I want to move the entire contents to a new address. Armory will only allow me to send 0.1 BTC at a time (says too many small transactions if I go bigger) and the fees to transfer all 5 BTC would be outrageous. I tried importing into Electrum and when I hit the send key it just sits there and processes forever when I try to send it all. I even tried sending just 0.5 BTC from Electrum and it does the same thing.

Is there a wallet that can handle?

Would importing into an online wallet work better?

I doubt it would work better but since Electrum and Armory are not working for you, you can try importing in blockchain.info wallet and try from there. That is your only option unless you have a hardware wallet and you move your contents there. In fact it is worth to buy a hardware wallet like the Ledger Nano S if you have more than 5 BTC to get and to protect from any thieves.

[shunyata]

not sure ledger is the solution. they specifically say not to mine to the device because lots of small transactions can take hours to process and possibly overheat and destroy your ledger. blockchain.info import seems better to me. once imported send the coins to your ledger in one transaction.

[-ck]

Your problem may be unfixable with regular wallets. The reason isn't the total number of inputs but the size of the generated transaction. If the transaction ends up being >100kb in size, it's a non-standard transaction meaning most nodes will not accept it and most miners would not mine it. I strongly recommend you break up the sweep into two (or more) smaller transactions to keep it as a standard transaction. Otherwise you'll have to go to great lengths to force software to accept it and find a miner who will happily include a non-standard transaction for you. It doesn't mean the transaction is invalid, it's just that it's rejected for its unnecessary burden on the network and nodes.

[eckmar]

If nothing else works for you, download bitcoin core wallet and use cli to manually create raw transaction and send it to network. That must work for sure

[dellech]

if most of your 770 inputs are very small the problem could be that the fee for including it in a transaction is bigger than the input itself.

a transaction with 770 inputs will be bigger than 100KB (non standard as in ck's response), so do not try to send everything at once.

in Armory I would try to set a really low fee (1 or 2 satoshis per byte) as with the standard value of eg. 200 sat/b the fee for a single input can be as high as 0.0004 BTC, so including any input below that value would be pointless. Armory might be smart enough not letting you spend them.

Only try to send a transaction with such a low fee when the transaction memory pool of the network is nearly empty - I successfully had transactions with only 1 sat/b executed waiting for less than 6 blocks.

consult https://bitcoinfees.21.co/#delay to check how long you expect to wait depending on the fee included. At the time of this writing a tx with a fee of 1 sat/byte should be included within the next 3 blocks