3
I have over 1400 small transactions in my wallet that add up to a little over 0.2 BTC. I am trying to send them, but keep getting a transaction too large error. I have tried to set a custom transaction fee, but am unable to still send. I am using Bitcoin core v0.10 on Windows. I have looked at this thread but am still unable to find a solution.
How can I combine all the tiny amounts I've received to minimise transaction fees, and do I need to?
3
Your scriptSig is too big! It is limited to 200 kbytes, and you've got 1400 inputs @ 0.2kbyte (best case scenario): 1400x 200 = 280kbyte.
Try using half the inputs (preferably newer inputs) to cut the scriptSig down in size.
1Why newer inputs? Wouldn't older inputs have a higher priority? – Nick ODell – 2015-04-30T05:08:26.887
@NickODell Yep, just "picking the better half" so to speak – Wizard Of Ozzie – 2015-04-30T05:17:53.553
2@WizardOfOzzie The older ones are the better ones. – Pieter Wuille – 2015-04-30T06:01:03.627
1@PieterWuille I personally would try sweeping up the worse (newer) ones to hopefully comprise a fee-free Tx. I'm not disputing the priority being inversely proportional to age; it's more a difference in opinion of how to handle dust, but tbh, I'll defer to you here! – Wizard Of Ozzie – 2015-04-30T06:46:32.203
2Priority is proportional to age, not inversely. And every output spent has its own scriptSig in the txin, which is around 105 bytes total per output spent. – Pieter Wuille – 2015-04-30T10:19:46.757
Thanks for your help. I have been able to send out various smaller sized amounts (0.0004 BTC). I looks like I will have to slowly transfer out the remaining balance in smaller transactions. – bob – 2015-04-30T23:21:33.087
1Does it say 'Transaction too large' or 'Transaction too large for fee policy?' They're different errors. – Nick ODell – 2015-04-30T00:30:50.840
It says just says "Transaction too large" – bob – 2015-04-30T02:10:49.843