Bitcoin Forum

Everyone, who mine on P2Pool or solo, or use many faucets, sometimes hit a wall: how to send many coins in one transaction and not pay huge fee?
I hit this problem, when I sent few hundred transactions to exchange and kill them wallet for week :P
Because most of altcoins not have coin control form latest Bitcoin Core client, so I wrote .net app that use RPC calls to access wallet and create transactions as you like.
First, you need to enable RPC access to your coin. Edit *coin.conf file in data directory, it will need:
If we not know default RPC port of coin just add:
If we have daemon not on local machine, we need allow remote RPC address to our machine
If you have encrypted wallet, you need open it b4 you can sign transaction.

Typical usage:
- enter ip:port of daemon (in example: 127.0.0.1:8223), press connect
- press "get inputs"
- sort inputs by age, value or how you like
- check inputs you want to use - value will calculate in lower box and in 1st output
- enter proper output address, you can put more than one (by default it is one output... BTC address to me, a little suggestion :D)
- sum of all outputs must be less or equal to inputs. If less - what`s left will be tx fee!
- then press "prepare", wait
- press "sign", wait
- press "send", wait
- after this input will be cleared

All RPC calls are in output window, so you can see and check them.

For many coins sending tx witch 0 fee is possible for older coins (mined long time ago).
To make one big input, you need do few times a loop:
- choose one address
- send 10-20 inputs to it
- loop till you have one input
If we send full many inputs to one address, we not create new one in wallet every transaction (no change every time). So one backup is enough :)
Then just create new wallet and send this one tx to it, you will have much lighter wallet file :)

App is available on my OneDrive (link in signeture), zip has no password. Sources are included ofc.
App on github:
Source: https://github.com/Rav3nPL/CoinControl
Zip: https://github.com/Rav3nPL/CoinControl/archive/master.zip

last update: https://bitcointalk.org/index.php?topic=929954.msg10769808#msg10769808

I hope it will help many users :)

Some screens:
http://i.snag.gy/qa1nQ.jpg
http://i.snag.gy/v5DPu.jpg
http://i.snag.gy/Bl8tu.jpg

is this really the right section ? . .

Wat?

indeed , weird this is that its comming from a legendary member :p

In fact, cant find better place for it.
Pls point it (a new place) and/or message moderator to move...   ::)

Source?

ocminer pool quick!!!

I have my abacus ready!!

Source in zip.

Dupmed it into github too: https://github.com/Rav3nPL/CoinControl

Small but good update :)
"listunspent" command is no longer logged. It makes log window 10000x faster for big number of outputs - no more "app not responding".

Nice piece if work rav3n_pl.

will look at it, some of these wallet daemons really piss me off with their shinanigans  :)

As this has been done in .NET it should hopefully be portable to MONO for linux, would be nice :-)

Regards
Cryptcollector

Mono support .net 4.5 so it should be no problem.
I used 4.0 because of Windows XP ;]

Is there a way to check multiple inputs at once? E.g. if I want to make a tx with like 200 inputs do I have to click each one?

I recommend to use up to 30 inputs, 200 will make really huge tx.
No, I did not implement any "mass select" option.
Loaded TXes are in order of their TXID, I`m sorting them to older first and select to value (or number of inputs) I desire.
I can add a numeric and a button to select first xx inputs. It would be useful for you?

I'd appreciate that. It will make this software quite helpful for my particular use case.

Done.
Added buttons: select all, deselect all, select 1st xxx rows (limit 500, default 30).
Also added display address of input.
http://i.snag.gy/lQkvp.jpg
Enjoy :)

Thank you. Unfortunately, even 500 wasn't enough for my task. It turned out faster to just send many smaller transactions straight from the wallet. So never mind.

500 inputs make about 90kb transaction, it is HUGE.
100`000 bytes is standard transaction limit.
You would have huge troubles to broadcast and accept it - standard configuration on node just drop transactions like that.

Small updates:
- need .Net 4,5 now
- updated newtosoft.json library
- pull unconfirmed outputs
- speedup in drawing (hide elements to avoid system redraws)

Have fun :)