<p>SegWit has to be activated on the network first. Signaling will start on the 15th of November. When there is a difficulty period where 95% of the blocks signal readiness for SegWit, it will be activated after another two weeks of fallow.</p>

<p>Creating SegWit transactions before it is activated on the network can lead to complete loss of funds.</p>

<p>After it has been activated, you can use SegWit by providing the sender a SegWit address (similar to a P2SH address). Likewise, to send a SegWit transaction, the recipient has to generate a SegWit address for your use.</p>

<p>This means that only wallets that already support SegWit will be recipients of SegWit transactions.</p>

CC BY-SA 3.0
2016-10-30T13:22:38.830Z
Is segwit address always p2sh-address? Or are new standard output scripts allowed by new client software? I see TX_WITNESS_V0_KEYHASH and TX_WITNESS_V0_SCRIPTHASH constants in sources but are they used?
amaclin
CC BY-SA 3.0
2016-10-30T23:17:38.143Z
They are standard, relayed, and accepted, but there is no way to specify an address for them directly.
Pieter Wuille
CC BY-SA 3.0
2017-05-05T23:02:19.100Z
Only ~35% of the network supports it currently ([source](https://blockchain.info/charts/bip-9-segwit))…
Geremia
CC BY-SA 3.0
2016-10-28T16:55:29.890Z
2016-10-28T16:55:29.890Z
Murch
<p>Bitcoin Core 13.1 includes the segregated witness (segwit) soft-fork. <a href="https://github.com/bitcoinknots/bitcoin/blob/v0.13.1.knots20161027/doc/release-notes.md" rel="noreferrer">The release notes</a> say:</p>

<blockquote>
  <p>Segregated witness (segwit) is a soft fork that, if activated, will allow transaction-producing software to separate (segregate) transaction signatures (witnesses) from the part of the data in a transaction that is covered by the txid.</p>
</blockquote>

<p>How do I activate segwit in Bitcoin Core 13.1? I couldn't find a command-line option for enabling it.</p>

<bitcoin-core><segregated-witness>
How do I enable segwit in Bitcoin Core 13.1?
Geremia
# How do I enable segwit in Bitcoin Core 13.1?

(Asked by: username_0 on 2016-10-28)

Bitcoin Core 13.1 includes the segregated witness (segwit) soft-fork. [The release notes](https://github.com/bitcoinknots/bitcoin/blob/v0.13.1.knots20161027/doc/release-notes.md) say:

> Segregated witness (segwit) is a soft fork that, if activated, will allow transaction-producing software to separate (segregate) transaction signatures (witnesses) from the part of the data in a transaction that is covered by the txid.

How do I activate segwit in Bitcoin Core 13.1? I couldn't find a command-line option for enabling it.

**Tags:** bitcoin-core, segregated-witness


---

## 1 answers

### Answer by username_1 on 2016-10-28. Score: 7 | Accepted answer

SegWit has to be activated on the network first. Signaling will start on the 15th of November. When there is a difficulty period where 95% of the blocks signal readiness for SegWit, it will be activated after another two weeks of fallow.

Creating SegWit transactions before it is activated on the network can lead to complete loss of funds.

After it has been activated, you can use SegWit by providing the sender a SegWit address (similar to a P2SH address). Likewise, to send a SegWit transaction, the recipient has to generate a SegWit address for your use.

This means that only wallets that already support SegWit will be recipients of SegWit transactions.

> **Comments:**
> **username_2**: Is segwit address always p2sh-address? Or are new standard output scripts allowed by new client software? I see TX_WITNESS_V0_KEYHASH and TX_WITNESS_V0_SCRIPTHASH constants in sources but are they used?  
> **username_3**: They are standard, relayed, and accepted, but there is no way to specify an address for them directly.  
> **username_0**: Only ~35% of the network supports it currently ([source](https://blockchain.info/charts/bip-9-segwit))…  

---

