<blockquote>
  <p>Is there a way to set custom change address (segwit preferable) in bitcoin core via config or some parameter (not via GUI). </p>
</blockquote>

<p>Not in 0.15 I believe, you would have to create a raw transaction manually with the change being sent to the address you wanted. Better support for segwit addresses is coming in 0.16</p>

<blockquote>
  <p>Is there a way how to report this to core developers</p>
</blockquote>

<p>Yes, you can submit bug reports to the issue tracker on GitHub here: <a href="https://github.com/bitcoin/bitcoin/issues" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues</a></p>

CC BY-SA 3.0
2018-01-08T00:17:08.810Z
2018-01-08T00:17:08.810Z
meshcollider
<p>We generated segwit addressess via <code>addwitnessaddress</code> command in v0.15 core client. Therefore receiving funds to our segwit addresses.</p>

<p>When spending those segwit UTXO, wallet creates a standard change address starting with 1. <strong>Is there a way to set custom change address (segwit preferable) in bitcoin core via config or some parameter</strong> (not via GUI). We wanted to contribute to segwit addoption, but this behavior is contraproductive. Any thoughts how to solve this?</p>

<p>The other problem is related to coin control feature on segwit addresses:
I used coin control feature to consolidate UTXO and send it to a single address (saving data on the blockchain becasue no change was created). However when using the wallet with segwit addresses it does not calculate size of transaction correctly - causing dust change. </p>

<p><a href="https://i.sstatic.net/5HkiK.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/5HkiK.png" alt="enter image description here"></a></p>

<p>Is there a way how to report this to core developers or any plans to solve this with core v16.?</p>

<address><segregated-witness>
How to set custom segwit change address in v0.15 Core via config
user1059931
# How to set custom segwit change address in v0.15 Core via config

(Asked by: username_0 on 2017-12-21)

We generated segwit addressess via `addwitnessaddress` command in v0.15 core client. Therefore receiving funds to our segwit addresses.

When spending those segwit UTXO, wallet creates a standard change address starting with 1. **Is there a way to set custom change address (segwit preferable) in bitcoin core via config or some parameter** (not via GUI). We wanted to contribute to segwit addoption, but this behavior is contraproductive. Any thoughts how to solve this?

The other problem is related to coin control feature on segwit addresses:
I used coin control feature to consolidate UTXO and send it to a single address (saving data on the blockchain becasue no change was created). However when using the wallet with segwit addresses it does not calculate size of transaction correctly - causing dust change.

[![enter image description here](https://i.sstatic.net/5HkiK.png)](https://i.sstatic.net/5HkiK.png)

Is there a way how to report this to core developers or any plans to solve this with core v16.?

**Tags:** address, segregated-witness


---

## 1 answers

### Answer by username_1 on 2018-01-08. Score: 2

> Is there a way to set custom change address (segwit preferable) in bitcoin core via config or some parameter (not via GUI).

Not in 0.15 I believe, you would have to create a raw transaction manually with the change being sent to the address you wanted. Better support for segwit addresses is coming in 0.16

> Is there a way how to report this to core developers

Yes, you can submit bug reports to the issue tracker on GitHub here: <https://github.com/bitcoin/bitcoin/issues>


---

