Topic: Advantage of coin control, response to Mike Hearn (Read 4707 times)

Coin Control is more fun!



Keep the output to less than 10k (or about 62 unspent) and you have no fee too.

Why I want coin control:

I understand keypairs.

I understand (on a basic level) how the blockchain and transactions work.

I do not understand the abstractions such as "accounts" built on bitcoin that the client imposes on me. They are neither something from the financial world nor something from the cryptography world. I can't see how they are useful and frankly I don't WANT TO learn how to use them.

I think a more sophisticated "accounting" system on top of the raw protocol could be useful if you are building a payment processing system on top of Bitcoin. I, as an end user, expect to do transactions very rarely and to spend a lot of time preparing whenever I have to make a transaction. Such as installing the newest client and downloading the blockchain.

So, what I want is:

1. The ability to import privkeys, preferably in many formats.
2. The ability to make raw transactions.

What I would like on top of those:

3. All kinds of "are you really really sure" warnings for anything that would be broadcast over to the network. Maybe even a configurable delay so that I could back out if I notice I made a mistake.

I do not want to keep any kind of a hot wallet, thank you very much. And I think the addressess (pubkeys) are a very useful thing to know, so I can check my balances from any third party service.

I do not want to run a node continuously.

100 day old 0.01 BTC is the smallest then, and 10 minute old 144 BTC is largest. If I have 19 dust, I should use 20 bitcoin days. Going to the extremes, I'd need 2000 day old 0.01 BTC, or 2880 BTC if I want it next block.

The Wiki has a technical explanation, but I'll try to simplify it. You must multiply number of satoshi's (10^-8 BTC) by number of confirmations and divide that by the total number of bytes to get priority. If the priority is greater than a 1 day 1 BTC coin (144 confs * 10^8 / 250 bytes), it can be free.

Now in reality, since compressed keys can be used, a transaction can be less than 250 bytes (min 225 for a standard one-input two-output tx).
Also, the number of bytes added by one more input varies greatly. Compare
http://blockchain.info/tx/8be6d23b774c9a5934c3a1927754e3fca4c98d6d95de7666a7f12df1d06f9b31
with
http://blockchain.info/tx/27bf16c3febd2c668ac867e378ca3fd9880a16cb969d4d54015553ed64416e95
to see what I mean. Both have 2 inputs and 2 outputs, yet there's a 64-byte difference between them.

If you give yourself a good cushion, though, you'll be fine. The easiest way is to use one bitcoin-day per input. If you're spending a dust tx, make sure you have 2 bitcoin-days. If you're spending 10 dust tx's, use 11 bitcoin-days. All bitcoin-days are created equal (except some days have more blocks than others; this is near-negligible). A 20-day 0.05 BTC has the same priority as a 1 day 1 BTC input.

Caveat: never create a sub-0.01 BTC output, no matter the priority.

I hope that was clear enough. If not, ask away!


P.S. The fee rules are not set in stone. Some miners have custom fee rules, and the rules in the reference client may soon change.

Would you have an easy chart on how this works? Say, for every day (or 144 block) equivalent of 1 BTC, how many SatoshiDICE dust inputs can be spent for free. Will this also convert to, for example, a 1 block old 144 BTC? And a 6 block old (1 hour) 24 BTC. 2 block old 72 BTC. 3 block old 48. 12 block old 12 BTC. etc?

If you never reuse addresses, it is identical.  I wouldn't think of it as controling each satoshi... every time you receive X BTC, that's like an $X-bill (if $1/BTC) now sitting in your wallet.  When you want to give someone 10 BTC (assuming X is more than 10), you sign a transaction that uses that $X-bill as input, and has two outputs:  assigning 10 BTC to their address, and assigning X-10 to a change address you own.  Now they have a 10-BTC bill in their wallet, and you have an (X-10)-BTC bill in your wallet.  The original bill is "spent" (never to be used again).

Really, your signature allows you to destroy X-BTC bills, and create new bills with new owners equal in size to the original (anything left over is claimed by the miner that mines the transaction as a fee).  Armory coin control basically says "I only want to use bills from these N addresses, no others".  The intent was to give users control over what addresses are linked when you create transactions.  Some people want more than that, and want to control individual bills... Armory doesn't have that.

The age of inputs is a factor in calculating transaction priority. With a 1 week old 1 BTC coin, you can spend 5+ SatoshiDICE dust inputs for free.

free to send

no taint 

I actually like Coin Control, so I can play SatoshiDice using only one address, and using only the inputs from that address, to make the bet, to set the change address to the same, to win or to lose (and collect dust), to bet again (consolidates dust) ... Of course, if you play that way, unless you wait long enough for the required blocks to achieve high priority and have a large number of coins for that purpose, you might end up always paying the transaction fee.

http://www.youtube.com/watch?v=U74s8nFE7No

This isn't exactly what i was suggesting.

Expert mode can still have a reasonably nice GUI, like CoinControl.

This indeed.  Documentation can be found here.

Debug console. The warning is replaced by the fact that using it is hard.

It does ?

I dont't see an "EXPERT MODE" button with a big, red, scary warning (YOU MIGHT LOSE UR MONIES !!!!!!!!!) anywhere.

How do I enable it ?

Bitcoin already has an expert mode, and has had it for a while now.

ever tried http://brainwallet.org? Thanks for the $30. 
(not sure if it is safe, though)

quoted you here: https://bitcointalksearch.org/topic/addresses-linked-by-default-potential-privacy-risk-in-standard-client-others-163757     
"Addresses Linked by Default - Potential Privacy Risk in Standard Client & Others"

I second the expert mode. Pop up a big scary warning message when a user enables it, but let the user decide.

For me, coin control is mostly a privacy thing. You're always told not to reuse addresses, but if you then make a payment a bunch of different addresses are combined for the input. Everybody can see that those belong to the same wallet then. Parse the blockchain and one can group those addresses by the wallets. If one address of those can be mapped to a user, all others are automatically mapped too.

It's like having accounts with three or four different banks and while you can define which account receives funds you're unable to say which bank(s) will pay a bill.

As for change, there could be some default/expert options:
1. directly back to the source
2. if several source addresses are used, offer a drop-down list
3. offer a list with all your addresses
4. generate a random new address

There are efficient integer linear programming solutions for most problem cases, at least for some sensible objectives (like "minimize priority subject to meeting the free relay criteria").

Actually deciding what you want to be your objective is AI-complete though.

Coin control is pretty much the only way to spend dust transactions. E.g. SatoshiDICE dust can be pruned if it is added to a large input and then spent.
Coin control is pretty much the best way to avoid associating addresses that should stay separate.

As for the first one, finding the optimal transaction is (I think) NP-complete. Assuming it can be brute-forced (throw every input-combination together, select best one), I think these would be my priorities, in order:

• Lowest fee
• Use most dust inputs (dust is hard to spend, pruning is good)
• Use youngest coins (aged coins are a resource)
• Smallest size

Currently I just use createrawtransaction and pick a good-looking set of inputs.

The best of both worlds would be to invent a protocol for trustless P2P mixing that would allow a user to consolidate UTXOs as part of the mixing process.