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?

  • 1
    Does it say 'Transaction too large' or 'Transaction too large for fee policy?' They're different errors. – Nick ODell Apr 30 '15 at 0:30
  • It says just says "Transaction too large" – bob Apr 30 '15 at 2:10
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.

  • 1
    Why newer inputs? Wouldn't older inputs have a higher priority? – Nick ODell Apr 30 '15 at 5:08
  • @NickODell Yep, just "picking the better half" so to speak – Wizard Of Ozzie Apr 30 '15 at 5:17
  • 2
    @WizardOfOzzie The older ones are the better ones. – Pieter Wuille Apr 30 '15 at 6:01
  • 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 Apr 30 '15 at 6:46
  • 2
    Priority 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 Apr 30 '15 at 10:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.