Say I want to send a number of payments. Sometimes the wallet will use up my entire balance with change just to send some small amount, and this stops me from being able to send additional payments for fifteen minutes or however long it takes to get my full balance back.

Is there any way to avoid this in order to send a bunch of payments in succession? And if not, won't this be a big issue for average people's usage when the GUI is released?


There's no direct way, but there could be a workaround.

The protocol doesn't limit the number of inputs/outputs. So, you could split the first transaction into many outputs where some (or all) of them are going back to yourself. This way, you'd do all your payments at once, and get more than one change output. Yes, you'd pay more fees but you'd then continue with enough unspent outputs to avoid the experience of having most funds locked on every transaction. You could do it with the CLI wallet, too! The transfer command allows for many destinations.

transfer [<mixin_count>] <addr_1> <amount_1> [<addr_2> <amount_2> ... <addr_N> <amount_N>] [payment_id] - Transfer <amount_1>,... <amount_N> to <address_1>,... <address_N>, respectively. <mixin_count> is the number of extra inputs to include for untraceability (from 2 to maximum available)"

|improve this answer|||||
  • 1
    The fees would be less or equal, actually, as far as I know, since you might be able to pay more than one destination from the same input. – user36303 Oct 8 '16 at 11:21
  • 1
    Yes, That's correct. At worst you'll pay the same fees, most likely less. It potentially is more private to combine payments too as it minimizes the successive use of outputs in a short period of time – bigreddmachine Oct 8 '16 at 14:53
  • 1
    Will this be an option with the GUI? Or after RingCT is implemented? – user4 Oct 8 '16 at 15:58
  • It's an option even now, by using the CLI wallet. Not sure how the GUI will handle multiple destinations, though. RingCT has nothing to do with this, but it will reduce fees beause the tx won't have to be split into denominations for ring signatures. And yes, you'd pay the same fees, but I gave the option to split the change into few outputs where you'd pay a fee for each one so additional fee when compared against "normal" sending. – JollyMort Oct 8 '16 at 21:58

Your Answer

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