[Bitcoin Client Feature Request] Option to explicitly set change bitcoin address

qdoop

member

Activity: 119

Merit: 112

_copy_improve_

Quote from: justusranvier on June 19, 2013, 02:12:05 AM

Quote from: qdoop on June 19, 2013, 12:27:34 AM

...................................
So far there is not any option to control the change address used by the client.

The feature you are describing is called coin control.

Quote from: Cyberdyne on June 19, 2013, 12:41:34 AM

...............

The problem will go away when deterministic wallets are implemented in the reference client instead of just in Armory and Electrum.

Thanks for the response and letting me know about coin control feature.
To tell you the truth i suspected there would exist similar requests.

The feature I request is just to be able to explicitly set the change address through a cmd line option and/or jsonrpc method.
That would be minimal, easily tested but greatly useful for the average user as Cyberdyne also pointed.

In my opinion the coin features you mentioned although great should not go main stream because would add to much complexity.
Also are partially redundant because of the rawtransaction API methods.
Reference client should include only the absolutely necessary features and nothing more leaving space for a market of full featured clients

justusranvier

legendary

Activity: 1400

Merit: 1013

Quote from: qdoop on June 19, 2013, 12:27:34 AM

I have been working with the bitcoin-qt client for some time.

Taking consideration of the recent changes in transaction fee policy
I started wondering of a feature easy to implement and test with major impact.

So far there is not any option to control the change address used by the client.

The feature you are describing is called coin control.

Quote from: Cyberdyne on June 19, 2013, 12:41:34 AM

It would be good if the client could be told to never automatically generate a new address, but only do so when you manually ask it to.

That way your backups will always work.

The problem will go away when deterministic wallets are implemented in the reference client instead of just in Armory and Electrum.

Cyberdyne

hero member

Activity: 630

Merit: 500

I think it would definitely result in less lost coins, if the client could be restricted to say 100 addresses, which it must reuse for change.

It would be good if the client could be told to never automatically generate a new address, but only do so when you manually ask it to.

That way your backups will always work.

qdoop

member

Activity: 119

Merit: 112

_copy_improve_

I have been working with the bitcoin-qt client for some time.

Taking consideration of the recent changes in transaction fee policy
I started wondering of a feature easy to implement and test with major impact.

So far there is not any option to control the change address used by the client.

Being able to do so:
1) Would greatly reduce the number of addresses some one has to track.
2) Could help reduce resource usage and improve tracking of transactions
3) Would extend the validity of wallet backups and reduce lost coins

I am well aware of the security and privacy concerns behind currently avoiding to do so.

That's why i speak for an option.
Of course for security reason the permitted range of addresses should be limited to the ones in current wallet

If you find this worthy i would be glad to help implement it and hear your opinion.

Topic: [Bitcoin Client Feature Request] Option to explicitly set change bitcoin address (Read 1800 times)