Addition to coderrr's Coin Control features branch

[CIYAM]

I understand that coderrr's branch provides control over the addresses chosen to "send from" when performing a "sendtoaddress" and changes the RPC for "sendtoaddress" to the following:

sendtoaddress <bitcoinaddress>[:<sendfromaddress1>[,<sendfromaddress2>[,...]]]

From the perspective of being able to control the addresses I think it should also be possible (at least through RPC) to optionally specify the address to send change to. Syntax of the RPC command could be as follows:

sendtoaddress <bitcoinaddress>[:<sendfromaddress1>[,<sendfromaddress2>[,...]][;<changeaddress>]]

Also - any ideas when/whether the coderrr branch will be merged into the main trunk?

[1714036566]

1714036566

[1714036566]

1714036566

[1714036566]

1714036566

[1714036566]

1714036566

[mb300sd]

I think a better solution would be to have the send from address option added to sendmany, its basically what I do in the GUI when I want to control the change, just add yourself as a second recipient and calculate the exact change.

[CIYAM]

it's 3 "r"s man, come on!

Oops - fixed the topic.  

[CIYAM]

I think a better solution would be to have the send from address option added to sendmany, its basically what I do in the GUI when I want to control the change, just add yourself as a second recipient and calculate the exact change.

Haven't really looked into sendmany yet but if it will do the job then that would be fine also (am only wanting the functionality), however, calculating the change manually (and the fee?) is not really what I'd want to be doing (in my case I actually just want the sendfrom and changeto to be the same address).

[CIYAM]

Let me try to further explain why I want this feature (and I really don't care exactly what form or exactly which RPC command is modified to support it) - I am wanting to use the blockchain as a "true" ledger for a specific address (i.e. that can be publicly audited without having to try and chase up "change" addresses and without using inputs from any other address).

I am so far surprised that no-one seems to be interested in this (for things such as Bitcoin100) and (if the feature actually does get added) will be creating a "project management" package for the CIYAM software platform that will integrate with bitcoind to work with such "non-anonymous" addresses.

[Gavin Andresen]

Let me try to further explain why I want this feature (and I really don't care exactly what form or exactly which RPC command is modified to support it) - I am wanting to use the blockchain as a "true" ledger for a specific address (i.e. that can be publicly audited without having to try and chase up "change" addresses and without using inputs from any other address).

I am so far surprised that no-one seems to be interested in this (for things such as Bitcoin100) and (if the feature actually does get added) will be creating a "project management" package for the CIYAM software platform that will integrate with bitcoind to work with such "non-anonymous" addresses.

I have a -noprivacy patch that I use for the Faucet that accomplishes what you want, sending any change back to the funding address.

It isn't part of the core code because it doesn't play nicely with other features (accounts and listtransactions, for example). See https://github.com/gavinandresen/bitcoin-git/tree/noprivacy

[CIYAM]

Thanks Gavin - I will take a look at that patch (although I really hope something that accomplishes this can get into the core code).

[CIYAM]

It isn't part of the core code because it doesn't play nicely with other features (accounts and listtransactions, for example). See https://github.com/gavinandresen/bitcoin-git/tree/noprivacy

I took a good look at the diff (https://github.com/gavinandresen/bitcoin-git/compare/master...noprivacy#diff-0) but (due to my lack of understanding) can't see how this causes problems with accounts and listtransactions - if it's not too much trouble could you give me an example of the kind of problem it introduces (so perhaps I can try and consider coming up with something similar that won't have the same problem)?

[Red Emerald]

I am so far surprised that no-one seems to be interested in this (for things such as Bitcoin100) and (if the feature actually does get added) will be creating a "project management" package for the CIYAM software platform that will integrate with bitcoind to work with such "non-anonymous" addresses.

If you don't want to patch anything, you can use a client like blockchain.info to handle the key. It will return change to the spending address.

If you want to never put the private keys on an online computer, Armory's watching wallets would be safe to distribute for auditing and the change addresses would be deterministic.  It's probably best to use that bitcoind patch though.