Bitcoin Wiki - User contributions [en]

Signet

2024-02-28T15:03:09Z

Kalle: /* External links */

'''Signet''' ([[BIP 0325]]) is a new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

NOTE: signet (VI) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267

===Fetch and compile signet===

<pre>
$ git clone https://github.com/bitcoin/bitcoin
$ cd bitcoin
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki BIP-325]

===Faucets===

* https://signetfaucet.com/
* https://alt.signetfaucet.com (the same [https://signetfaucet.bublina.eu.org here])

Faucet source code, if you want your own:

* https://github.com/stepansnigirev/tinyfaucet.git (python)
* https://github.com/jsarenik/bitcoin-faucet-shell (POSIX shell)

===Block explorers===

* https://explorer.bc-2.jp/
* https://mempool.space/signet
* https://ex.signet.bublina.eu.org

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon -wallet="test"
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "THE_REAL_PUBKEY",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>THE_REAL_PUBKEY</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -regtest stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir -wallet="test"
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we're going to get an issuer up and running to mine blocks.

We'll need to provide a value for <code>nbits</code> which is the mining target and is inversely proportional to the difficulty. This will allow us to set the average time between mined blocks.

We can use the <code>calibrate</code> command to give us the <code>nbits</code> for an average mining time of 10 min (600 s):

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli" calibrate --grind-cmd="./bitcoin-util grind" --seconds=600
</pre>

Referring to our <code>nbits</code> value with the variable <code>$NBITS</code>, we need to specify <code>--set-block-time</code> when mining the first block in a new signet:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --set-block-time=$(date +%s)
</pre>

This will create an address, and then mine the first block to that address. (Note that you may need to create a wallet first.)

To keep the mining ongoing from there, aiming for blocks arriving every 10 minutes on average, we can run:

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --ongoing
</pre>

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

===Example Script===

A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2022-09-19T14:02:50Z

Kalle:

'''Signet''' ([[BIP 0325]]) is a new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

NOTE: signet (VI) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267

===Fetch and compile signet===

<pre>
$ git clone https://github.com/bitcoin/bitcoin
$ cd bitcoin
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki BIP-325]

===Faucets===

* https://signetfaucet.com/
* https://alt.signetfaucet.com (the same [https://signetfaucet.bublina.eu.org here])

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)
* https://github.com/jsarenik/bitcoin-faucet-shell (POSIX shell)

===Block explorers===

* https://explorer.bc-2.jp/
* https://mempool.space/signet
* https://ex.signet.bublina.eu.org

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon -wallet="test"
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "THE_REAL_PUBKEY",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>THE_REAL_PUBKEY</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -regtest stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir -wallet="test"
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we're going to get an issuer up and running to mine blocks.

We'll need to provide a value for <code>nbits</code> which is the mining target and is inversely proportional to the difficulty. This will allow us to set the average time between mined blocks.

We can use the <code>calibrate</code> command to give us the <code>nbits</code> for an average mining time of 10 min (600 s):

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli" calibrate --grind-cmd="./bitcoin-util grind" --seconds=600
</pre>

Referring to our <code>nbits</code> value with the variable <code>$NBITS</code>, we need to specify <code>--set-block-time</code> when mining the first block in a new signet:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --set-block-time=$(date +%s)
</pre>

This will create an address, and then mine the first block to that address. (Note that you may need to create a wallet first.)

To keep the mining ongoing from there, aiming for blocks arriving every 10 minutes on average, we can run:

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --ongoing
</pre>

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

===Example Script===

A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2021-02-23T03:02:54Z

Kalle: /* External links */

'''Signet''' ([[BIP 0325]]) is a new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

NOTE: signet (IV) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267

===Fetch and compile signet===

<pre>
$ git clone https://github.com/bitcoin/bitcoin
$ cd bitcoin
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki BIP-325]

===Faucets===

* https://signetfaucet.com/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/
* https://mempool.space/signet

==Custom Signet==

'''NOTE:''' Until it is merged into master branch, you may first need to check-out (or merge) the code referred in https://github.com/bitcoin/bitcoin/pull/19937 in order to get the script <code>contrib/signet/miner</code>.

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon -wallet="test"
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "THE_REAL_PUBKEY",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>THE_REAL_PUBKEY</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -regtest stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir -wallet="test"
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we're going to get an issuer up and running to mine blocks.

We'll need to provide a value for <code>nbits</code> which is the mining target and is inversely proportional to the difficulty. This will allow us to set the average time between mined blocks.

We can use the <code>calibrate</code> command to give us the <code>nbits</code> for an average mining time of 10 min (600 s):

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli" calibrate --grind-cmd="./bitcoin-util grind" --seconds=600
</pre>

Referring to our <code>nbits</code> value with the variable <code>$NBITS</code>, we need to specify <code>--set-block-time</code> when mining the first block in a new signet:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --set-block-time=$(date +%s)
</pre>

This will create an address, and then mine the first block to that address. (Note that you may need to create a wallet first.)

To keep the mining ongoing from there, aiming for blocks arriving every 10 minutes on average, we can run:

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --ongoing
</pre>

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

===Example Script===

A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2021-02-23T02:59:46Z

Kalle: Removed old pull request links and added link to BIP.

'''Signet''' ([[BIP 0325]]) is a new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

NOTE: signet (IV) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267

===Fetch and compile signet===

<pre>
$ git clone https://github.com/bitcoin/bitcoin
$ cd bitcoin
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki BIP-325]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/
* https://mempool.space/signet

==Custom Signet==

'''NOTE:''' Until it is merged into master branch, you may first need to check-out (or merge) the code referred in https://github.com/bitcoin/bitcoin/pull/19937 in order to get the script <code>contrib/signet/miner</code>.

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon -wallet="test"
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "THE_REAL_PUBKEY",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>THE_REAL_PUBKEY</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -regtest stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir -wallet="test"
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we're going to get an issuer up and running to mine blocks.

We'll need to provide a value for <code>nbits</code> which is the mining target and is inversely proportional to the difficulty. This will allow us to set the average time between mined blocks.

We can use the <code>calibrate</code> command to give us the <code>nbits</code> for an average mining time of 10 min (600 s):

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli" calibrate --grind-cmd="./bitcoin-util grind" --seconds=600
</pre>

Referring to our <code>nbits</code> value with the variable <code>$NBITS</code>, we need to specify <code>--set-block-time</code> when mining the first block in a new signet:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --set-block-time=$(date +%s)
</pre>

This will create an address, and then mine the first block to that address. (Note that you may need to create a wallet first.)

To keep the mining ongoing from there, aiming for blocks arriving every 10 minutes on average, we can run:

<pre>
$ ../contrib/signet/miner --cli="./bitcoin-cli -datadir=$datadir" generate --address $ADDR --grind-cmd="./bitcoin-util grind" --nbits=$NBITS --ongoing
</pre>

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

===Example Script===

A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Main Page

2021-02-09T04:12:53Z

Kalle:

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2021-02-01T04:09:31Z

Kalle:

Main Page

2021-02-01T04:08:30Z

Kalle: Reverted edits by Furunodo (talk) to last revision by Kalle

Signet

2020-10-02T06:14:44Z

Kalle: /* Run issuer */

Signet ([[BIP 0325]]) is a proposed new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start an issuer using <code>bitcoin-util</code>:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/generate.py --cli="./bitcoin-cli -datadir=$datadir" generate 0 --address $ADDR --grind-cmd='./bitcoin-util grind' --block-time=600
</pre>

This will create an address, and then start mining to that address, aiming for blocks arriving every 10 minutes on average. (Note that you may need to create a wallet first.)

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-10-01T10:15:36Z

Kalle:

Signet ([[BIP 0325]]) is a proposed new test network for Bitcoin which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start an issuer using [code]bitcoin-util[/code]:

<pre>
$ ADDR=$(./bitcoin-cli -datadir=$datadir getnewaddress); ../contrib/signet/generate.py --cli="./bitcoin-cli -datadir=$datadir" generate 0 --address $ADDR --grind-cmd='./bitcoin-util grind' --block-time=600
</pre>

This will create an address, and then start mining to that address, aiming for blocks arriving every 10 minutes on average.

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-09-18T06:14:22Z

Kalle: `-signet_*` → `-signet*`

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signetchallenge=<hex></code>, and preferably also at least one seed node using <code>-signetseednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signetchallenge</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signetchallenge=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signetchallenge</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-09-08T06:25:38Z

Kalle: Global network VI

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net VI" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_challenge=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_challenge</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_challenge=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_challenge</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-08-28T09:50:13Z

Kalle:

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net V" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_challenge=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_challenge</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_challenge=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_challenge</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-08-28T07:15:20Z

Kalle: /* Generating keys used for signing a block */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net V" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a regtest node and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -regtest -daemon
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-08-28T07:14:09Z

Kalle: /* Differences */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net V" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-08-28T07:13:42Z

Kalle: Use testnet prefix

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net V" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00; this is the same as testnet)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-08-11T09:14:50Z

Kalle: Update to reflect test net V

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net V" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are *dynamically generated* based on the block challenge, i.e. every signet is different; the header for the current default signet is <code>0x0A03CF40</code> (that is reversed e.g. in Rust variables) (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-18T09:28:11Z

Kalle: /* Getting Started */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-10T07:58:20Z

Kalle: /* Differences */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Header]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-10T07:58:08Z

Kalle: /* Genesis Block and Message Start */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Start]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Header==

All signet networks share the same genesis block, but have a different message header. The message header is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-10T07:57:38Z

Kalle: /* Differences */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>), but see [[#Genesis_Block_and_Message_Start]]
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Start==

All signet networks share the same genesis block, but have a different message start. The message start is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-10T07:57:15Z

Kalle: /* Differences */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>), but see #Genesis_Block_and_Message_Start
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Start==

All signet networks share the same genesis block, but have a different message start. The message start is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-09T11:01:30Z

Kalle:

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0x7EC653A5</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Start==

All signet networks share the same genesis block, but have a different message start. The message start is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-05T09:29:00Z

Kalle:

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Start==

All signet networks share the same genesis block, but have a different message start. The message start is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-03-05T09:28:41Z

Kalle: Switch to proposed changes in https://github.com/bitcoin/bips/pull/900

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net IV" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and the genesis nonce using <code>-signet_genesisnonce=<number></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block has timestamp 1534313275, nonce 100123, and difficulty 0x1e2adc28.
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block and Message Start==

All signet networks share the same genesis block, but have a different message start. The message start is the 4 first bytes of the sha256d-hash of the block challenge, as a single script push operation. I.e. if the block challenge is 37 bytes, the message start would be sha256d(0x25 || challenge)[0..3].

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-02-05T14:17:48Z

Kalle: /* External links */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net III" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and the genesis nonce using <code>-signet_genesisnonce=<number></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript and genesis nonce (it is proof of work valid, but does not contain a signet commitment)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is provided (<code>621297</code> for SGNIII), and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/bitcoin/bitcoin/pull/16411 Pull request #16411 to Bitcoin Core]
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Grinding the genesis nonce===

Since the genesis block needs to be proof-of-work valid, we need to actually mine it. This is not a problem though, because Signet difficulty starts out quite low, so it should only take a few seconds.

<pre>
$ ./bitcoin-cli -signet grindblock 512102c60c3940e5REDACTEDbd0148cd51ae
12345
</pre>

The genesis nonce is <code>12345</code>. Together with the block script, this defines our new Signet network!

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae
signet_genesisnonce=12345" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-02-05T14:16:20Z

Kalle: /* Faucets */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net III" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and the genesis nonce using <code>-signet_genesisnonce=<number></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript and genesis nonce (it is proof of work valid, but does not contain a signet commitment)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is provided (<code>621297</code> for SGNIII), and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

Faucet source code, if you want your own:

* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)
* https://github.com/stepansnigirev/tinyfaucet.git (python)

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Grinding the genesis nonce===

Since the genesis block needs to be proof-of-work valid, we need to actually mine it. This is not a problem though, because Signet difficulty starts out quite low, so it should only take a few seconds.

<pre>
$ ./bitcoin-cli -signet grindblock 512102c60c3940e5REDACTEDbd0148cd51ae
12345
</pre>

The genesis nonce is <code>12345</code>. Together with the block script, this defines our new Signet network!

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae
signet_genesisnonce=12345" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2020-01-04T02:13:29Z

Kalle: /* Getting Started */

Signet ([[BIP 0325]]) is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net III" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and the genesis nonce using <code>-signet_genesisnonce=<number></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript and genesis nonce (it is proof of work valid, but does not contain a signet commitment)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is provided (<code>621297</code> for SGNIII), and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.19
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $ADDR | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Grinding the genesis nonce===

Since the genesis block needs to be proof-of-work valid, we need to actually mine it. This is not a problem though, because Signet difficulty starts out quite low, so it should only take a few seconds.

<pre>
$ ./bitcoin-cli -signet grindblock 512102c60c3940e5REDACTEDbd0148cd51ae
12345
</pre>

The genesis nonce is <code>12345</code>. Together with the block script, this defines our new Signet network!

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae
signet_genesisnonce=12345" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-08-19T04:15:14Z

Kalle:

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net III" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and the genesis nonce using <code>-signet_genesisnonce=<number></code>, and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript and genesis nonce (it is proof of work valid, but does not contain a signet commitment)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is provided (<code>621297</code> for SGNIII), and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Grinding the genesis nonce===

Since the genesis block needs to be proof-of-work valid, we need to actually mine it. This is not a problem though, because Signet difficulty starts out quite low, so it should only take a few seconds.

<pre>
$ ./bitcoin-cli -signet grindblock 512102c60c3940e5REDACTEDbd0148cd51ae
12345
</pre>

The genesis nonce is <code>12345</code>. Together with the block script, this defines our new Signet network!

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae
signet_genesisnonce=12345" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> and <code>signet_genesisnonce</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-07-16T04:25:17Z

Kalle: /* Using the command line tool */

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net II" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript (and is thus not actually valid)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is <code>0</code>, and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. You can optionally provide a path to <code>bitcoin-cli</code> using <code>--cmd=[path]</code> and a compatible faucet using <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>. The script attempts to autodetect these if left out.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-07-11T12:12:53Z

Kalle: /* Start up a node (issuer) */

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net II" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript (and is thus not actually valid)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is <code>0</code>, and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. It takes the path to <code>bitcoin-cli</code> and an optional <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh ../../src/bitcoin-cli -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

Note: if you run into errors above, you may have a different signet running, which is blocking the ports. Either stop that, or set port and rpcport in the <code>$datadir/bitcoin.conf</code> file under the <code>[signet]</code> section and try again from the <code>bitcoind</code> part above.

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-07-11T03:44:18Z

Kalle: /* Differences */

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net II" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* Address prefixes are different: pubkey=<code>0x7D</code> (125), p2sh=<code>0x57</code> (87), privkey=<code>0xD9</code> (217)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript (and is thus not actually valid)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is <code>0</code>, and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. It takes the path to <code>bitcoin-cli</code> and an optional <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh ../../src/bitcoin-cli -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-07-10T12:57:48Z

Kalle:

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net II" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no testnet Bitcoin addresses will work on the production network. (<code>0x7D</code> rather than <code>0x00</code>)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript (and is thus not actually valid)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is <code>0</code>, and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

There is a command line tool you can use to get coins directly to your instance of Signet, assuming you are on the default network. You can also use the faucet online with an address of yours.

====Using online faucet====

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

====Using the command line tool====

The tool is in <code>contrib/signet</code> and is called <code>getcoins.sh</code>. It takes the path to <code>bitcoin-cli</code> and an optional <code>--faucet=[url]</code> followed by any number of arguments to <code>bitcoin-cli</code>.

<pre>
$ cd ../contrib/signet
$ ./getcoins.sh ../../src/bitcoin-cli -datadir=../../src/signet
Payment of 10.00000000 BTC sent with txid c0bfa...
</pre>

===Check that you received the coins===

Check your faucet transaction confirming at e.g. https://explorer.bc-2.jp and then send coins around to people and/or use signet for testing your wallet/etc.

You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.

<pre>
$ cd ../../src # if you were in contrib/signet
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance
</pre>

You can also see info about the transaction that the faucet gave you.

<pre>
$ ./bitcoin-cli -datadir=signet gettransaction THETXID
</pre>

Once it has confirmed, you should see it in <code>getbalance</code>.

<pre>
$ ./bitcoin-cli -datadir=signet getbalance
</pre>

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Signet

2019-07-10T08:05:54Z

Kalle: Created page with "Signet is a proposed new test network for the Bitcoin block chain which adds an additional signature requirement to block validation. Signet is similar in nature to test..."

Signet is a proposed new test network for the Bitcoin [[block chain]] which adds an additional signature requirement to block validation. Signet is similar in nature to [[testnet]], but more reliable and centrally controlled. There is a default signet network ("Signet Global Test Net II" as of this writing), but anyone can run their own signet network at their whim.

Run bitcoind with the <code>-signet</code> flag to use the default global signet (or put <code>signet=1</code> in the <code>bitcoin.conf</code> file). If you wish to use a [[#Custom Signet|custom signet]], you need to provide the block challenge (aka the block script) using <code>-signet_blockscript=<hex></code> and preferably also at least one seed node using <code>-signet_seednode=<host>[:<port>]</code>.

==Differences==

* Default Bitcoin network protocol listen port is 38333 (instead of 8333)
* Default RPC connection port is 38332 (instead of 8332)
* A different value of ADDRESSVERSION field ensures no testnet Bitcoin addresses will work on the production network. (<code>0x7D</code> rather than <code>0x00</code>)
* The protocol message header bytes are <code>0xF0C7706A</code> (instead of <code>0xF9BEB4D9</code>)
* Genesis block is generated based on the signet blockscript (and is thus not actually valid)
* Segwit is always enabled
* Additional consensus requirement that the coinbase witness commitment contains an extended signet commitment, which is a script satisfying the block script (usually a k-of-n multisig)

==Why run Signet?==

* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.
* You are a Software Developer, and want to test your software.
* You want to try out experimental changes that you want to implement in Bitcoin.
* You want to test long-term running software and don't want to deal with tens of thousands of block reorgs, or days of no blocks being mined, as is the case with Testnet.
* You want an easy way to test double spends (signet plans to include support for automated double spends, where you provide two conflicting transactions and they are mined in order, with a reorg happening between them).

==Genesis Block==

Each signet network has its own genesis block. The coinbase signature of the genesis block for a signet network with the blockscript <code>S</code> is calculated as
<pre>
sha256(sha256(S))
</pre>
and the output is simply
<pre>
OP_RETURN
</pre>

The nTime is <code>1534313275</code>, the nonce is <code>0</code>, and the nBits (difficulty target) is <code>0x1e2adc28</code> (POW limit <code>00002adc28cf53b63c82faa55d83e40ac63b5f100aa5d8df62a429192f9e8ce5</code>).

==Getting Started==

===Fetch and compile signet===

<pre>
$ git clone https://github.com/kallewoof/bitcoin.git signet
$ cd signet
$ git checkout signet-0.18
$ ./autogen.sh
$ ./configure
$ make -j5
</pre>

===Create bitcoin.conf file and start up the daemon===

<pre>
$ cd src
$ mkdir signet
$ echo "signet=1
daemon=1" > signet/bitcoin.conf
$ ./bitcoind -datadir=signet
</pre>

===Verify that you're connected===

<pre>
$ ./bitcoin-cli -datadir=signet getconnectioncount
***SHOULD BE MORE THAN ZERO***
$ ./bitcoin-cli -datadir=signet getblockcount
***SHOULD BE MORE THAN ZERO***
</pre>

===Get some coins===

You first need an address

<pre>
$ ./bitcoin-cli -datadir=signet getnewaddress
</pre>

Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.

Then see your transaction be confirmed at an explorer, e.g. https://explorer.bc-2.jp.

==External links==

* [https://github.com/kallewoof/bitcoin/pull/4 WIP pull request]
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]

===Faucets===

* https://signet.bc-2.jp/

Can also ping @kallewoof on IRC (freenode)/Twitter.

===Block explorers===

* https://explorer.bc-2.jp/

==Custom Signet==

Creating your own signet involves a couple of steps: generate keys used for signing, define the block script, start up a node running on the new signet, and import the private key in order to sign blocks.

===Generating keys used for signing a block===

The most straightforward way is to simply start up a signet instance and then generating a new key from there.

<pre>
$ cd PATHTOBITCOIN/bitcoin/src
$ ./bitcoind -signet -daemon
$ ADDR=$(./bitcoin-cli -signet getnewaddress)
$ PRIVKEY=$(./bitcoin-cli -signet dumpprivkey $ADDR)
$ ./bitcoin-cli -signet getaddressinfo $PRIVKEY | grep pubkey
"pubkey": "02c60c3940e5REDACTEDbd0148cd",
</pre>

We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>02c60...</code>).

===Defining the block script===

The block script is just like any old Bitcoin script, but the most common type is a k-of-n multisig. Here we will do a 1-of-1 multisig with our single pubkey above. Our script becomes
* <code>51</code> "1" (signature count)
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)
* <code>02c60c3940e5REDACTEDbd0148cd</code> (our pubkey)
* <code>51</code> "1" (pubkey count)
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode

Put together, our <code>-signet_blockscript</code> value becomes <code>512102c60c3940e5REDACTEDbd0148cd51ae</code>.

===Start up a node (issuer)===

For the network to be useful, it needs to be generating blocks at decent intervals, so let's start up a node that does that (it may be useful to also use that node as a seed node for other peers).

Note that we are importing <code>$PRIVKEY</code> at the end; any node that needs to issue blocks must import the privkey we generated above, or it will fail to sign blocks.

<pre>
$ ./bitcoin-cli -signet stop
$ datadir=$HOME/signet-custom
$ mkdir $datadir
$ echo "signet=1
[signet]
daemon=1
signet_blockscript=512102c60c3940e5REDACTEDbd0148cd51ae" > $datadir/bitcoin.conf
$ ./bitcoind -datadir=$datadir
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY
</pre>

===Run issuer===

Lastly, we start the issuer script located in <code>contrib/signet</code>.

<pre>
$ cd ../contrib/signet
$ ./issuer.sh 540 ../../src/bitcoin-cli -datadir=$datadir
- checking node status
- 23:51:01: node OK with 0 connection(s)
- 23:51:01: mining at maximum capacity with 540 second delay between each block
- 23:51:01: hit ^C to stop
- 23:51:01: generating next block
- 23:51:08: mined block 1 0000321422407052c06fef1eacbee402571787c9828051981adfbb5d50a2330a to 0 peer(s); idling for 540 seconds
</pre>

This script will keep on mining blocks every 540 seconds (actually it will take about 60 seconds to generate a block after the difficulty has stabilized, so you should be seeing one block every 600 seconds) until you hit ctrl-C. It may be a good idea to run this in a screen, so you can check back on it occasionally.

You may also want to run the issuer with a lower idle time initially, so you get some mature coinbase outputs faster.

Next is to have your friends/colleagues/etc join the network by setting the <code>signet_blockscript</code> to the same as above, and connecting to your node.

[[Category:Technical]]
[[Category:Developer]]

{{Bitcoin Core documentation}}

Main Page

2018-05-18T03:00:09Z

Kalle:

Main Page

2018-05-18T01:47:53Z

Kalle:

{| id="mp-topbanner" style="width:100%; background:#ff0000; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#ff0;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em;">Upgrade Complete</div>
'''Report issues on #bitcoin-wiki on freenode.'''
|}
{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2018-05-17T03:30:34Z

Kalle:

{| id="mp-topbanner" style="width:100%; background:#ff0000; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#ff0;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em;">Scheduled Upgrade</div>
'''The server will undergo extended maintenance 24:00 UTC (midnight leading into Friday). Expect downtime and breakage. Report issues on #bitcoin-wiki on freenode.'''
|}
{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2018-05-15T23:40:50Z

Kalle:

{| id="mp-topbanner" style="width:100%; background:#ff0000; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#ff0;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em;">Upgrade Postponed</div>
'''The scheduled upgrade has been postponed temporarily. A new scheduled date will appear here soon.'''
|}
{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2018-05-15T23:14:54Z

Kalle:

{| id="mp-topbanner" style="width:100%; background:#ff0000; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#ff0;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em;">Scheduled Upgrade!</div>
'''The server is undergoing maintenance. Expect downtime and possibly temporary breakage for the next couple of hours.'''
|}
{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Main Page

2018-05-15T07:27:20Z

Kalle: Notice about scheduled maintenance

{| id="mp-topbanner" style="width:100%; background:#ff0000; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#ff0;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em;">Scheduled Upgrade!</div>
'''The server will undergo extended maintenance May 16 2018 at 1:00 am UTC. Expect downtime and possibly temporary breakage.'''
|}
{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bitcoin]] Wiki,</div>
<div style="top:+0.2em; font-size:95%;">for all your Bitcoin information needs.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] pages. Established April 14, 2010.</div>
'''This wiki is maintained by the Bitcoin community.'''
|}

| style="width:39%;" |<center>{{ERN}}</center>
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bitcoin.org/ Bitcoin.org]</span>
|<span class="plainlinks">[[Forums]]</span>
|<span class="plainlinks">[[IRC channels|Chatrooms]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bitcoin</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">FAQ</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_FAQ}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
* '''[[BW:About|About]]''' - Information on this site.
* '''[http://dump.bitcoin.it/ Dumps]''' - Backup this wiki.
</noinclude>__NOTOC____NOEDITSECTION__

Segwit support

2017-06-22T02:57:24Z

Kalle:

<big><big>'''PLEASE NOTE:''' This list is not yet complete.</big></big>

'''Developers/businesses: Please add a row for yourself in the applicable table to reflect your positions. If for some reason you don't already have a wiki account that can edit the page, make an account and ask luke-jr for help if you get caught in the anti-spam.'''

{| class="wikitable"
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)
|-
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support
|-
| {{Evaluating}} || still evaluating the idea
|-
| {{AccJuly}} || it is a workable solution, provided it is activated before August 1 (and therefore BIP148-compatible)
|-
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support
|-
| {{Weak}} || better than nothing at all
|-
| {{Acceptable}} || it is a workable solution
|-
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences
|}

__TOC__

==Developers==



''Note that support for a given proposal does not mean developers support merging it into Core or any other specific codebase.''

{| class="wikitable sortable"
! rowspan=2 | Developer
! rowspan=2 | Aff* 
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| Karl-Johan Alm || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Bryan Bishop || || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| ฿tcDrak || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Andrew Chow || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Wang Chun || [[F2Pool]] || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Acceptable}} || {{AccJuly}} ||
|-
| Matt Corallo || Core || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||
|-
| Johnathan Corgan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Luke Dashjr || Core || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No}} || {{Deficient}}
|-
| Christian Decker || c-lightning || {{Prefer}} || {{Acceptable}} || || || ||
|-
| Nicolas Dorier || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{AccJuly}} || ||
|-
| Thaddeus Dryja || lit || {{Prefer}} || {{No}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Marco Falke || Core || {{Prefer}} || {{Deficient}} || {{Prefer}} || {{Deficient}} || ||
|-
| Mark Friedenbach || BIP 68/112 || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No|LOL}} || {{No|Nope}}
|-
| Pavel Janik || Core || {{Prefer}} || {{No}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Thomas Kerin || Core || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}
|-
| Johnson Lau || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||
|-
| Eric Lombrozo || || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Greg Maxwell || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Alex Morcos || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| nopara73 || TumbleBit || {{Weak}} || {{Wanting}} || {{Prefer}} || || ||
|-
| Laolu "roasbeef" Osuntokun || lnd || {{Prefer}} || || || || {{No}} ||
|-
| Jeremy Rubin || Core || {{Prefer}} || {{Deficient}} || {{No}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Pavol "stick" Rusnak || [[TREZOR]] || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{AccJuly}} || {{No}} || {{No}}
|-
| Rusty Russell || c-lightning || {{Prefer}} || {{Prefer}} || || || ||
|-
| Gregory Sanders || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| Jonas Schnelli || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Patrick Strateman || Core || {{Prefer}} || || || || {{No}} || {{No}}
|-
| Paul Sztorc || || {{Prefer}} || {{Deficient}} || {{Wanting}} || {{AccJuly}} || {{Evaluating}} || {{No}}
|-
| Amir Taaki || libbtc || {{Acceptable}} || {{Prefer}} || || || {{No}} || {{No}}
|-
| Jorge Timon || Core || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}
|-
| Peter Todd || Core || {{Prefer}} || {{Acceptable}} || || || ||
|-
| Warren Togami || Elements || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||
|-
| Wladimir van der Laan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Leo Wandersleb || Mycelium || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{AccJuly}} || {{No}}
|-
| Pieter Wuille || Core || {{Prefer}} || || || || {{No}} ||
|}

* "affiliation" is an optional field for the company or project the individual is associated with, that most qualifies the person to comment on the matter and is not meant as a company or project endorsement of the individual's position.

==Businesses==

'''When adding companies below, sources for each position MUST be provided.'''

{| class="wikitable sortable"
! rowspan=2 | Company
! rowspan=2 | Service
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| Abra || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Bitcoin India || exchange/miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| BitcoinReminder.com || service || {{Prefer}}<ref name="bitcoinreminder_com">[https://bitcoinreminder.com/informations/poli BitcoinReminder.com's position on scaling proposals]</ref> || {{Prefer}}<ref name="bitcoinreminder_com"/> || {{Acceptable}}<ref name="bitcoinreminder_com"/> || {{Weak}}<ref name="bitcoinreminder_com"/> || {{No|LOL}}<ref name="bitcoinreminder_com"/> || {{No}}<ref name="bitcoinreminder_com"/>
|-
| Bitfinex || exchange || {{Acceptable}}<ref name="coindance" /> || {{Acceptable}} || || || ||
|-
| Bitfury || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}} || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Bitmain || miner || {{AccJuly}}<ref name="bitmain">[https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip148/ Bitmain's plot against BIP148]</ref> || {{No}} || || {{AccJuly}} || {{AccJuly}}<ref name="bitmain" /> ||
|-
| Bitonic/BL3P.eu || exchange || {{Prefer}}<ref name="bitonic">[https://bitonic.nl/en/news/138/our-position-on-scaling-proposals Bitonic's position on scaling proposals]</ref> || {{Prefer}}<ref name="bitonic"/> || {{Acceptable}}<ref name="bitonic"/> || {{Weak}}<ref name="bitonic"/> || {{No|LOL}}<ref name="bitonic"/> || {{No}}
|-
| Bitpay || wallet || {{Prefer}}<ref name="bccore_swadoption"/> || {{No}} || || {{Prefer}} || {{Prefer}}<ref name="silbert" /> ||
|-
| Bitrated || reputation || {{Acceptable}}<ref name="bitrated">[https://twitter.com/bitrated/status/876805892003553281]</ref> || {{Acceptable}}<ref name="bitrated" /> || {{Prefer}}<ref name="bitrated" /> || {{AccJuly}}<ref name="bitrated" /> || {{No}}<ref name="bitrated" /><ref>[https://medium.com/@shesek/why-i-dont-support-the-compromise-efforts-9d73a8cce6be Why I don’t support horse-trading compromises for Bitcoin protocol development]</ref> ||
|-
| Bitrefill || merchant || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| Bitsquare || exchange || {{Prefer}} || {{Prefer}}<ref name="bitsquare">[https://forum.bitsquare.io/t/bitsquare-will-support-uasf-bitcoin-not-bitmaincoin/2265 Bitsquare will support UASF Bitcoin not BitMainCoin]</ref> || {{Acceptable}}<ref name="bitsquare"/> || || || ||
|-
| Bitstamp || exchange || || || || || ||
|-
| Bittylicious || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref>[https://twitter.com/Bittylicious_/status/867305106668224513 Bittylicious answer on Twitter]</ref> || || || ||
|-
| Blockchain.info || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| blockonomics || || {{Prefer}} || {{Prefer}}<ref>[https://twitter.com/blockonomics_co/status/851738251509497856 blockonomics announcement on Twitter]</ref> || || || ||
|-
| Bustabit|| gambling || {{Prefer}}<ref name="bustabit">[https://www.bustabit.com/statement-on-forks Bustabit Statement on Bitcoin Forks]</ref> || {{Acceptable}}<ref name="bustabit"/> || || || {{AccJuly}}<ref name="bustabit"/> ||
|-
| Ciphrex || wallet / dev stack || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||
|-
| Coinbase || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| CoinGate || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| CoinJar || wallet || || {{Evaluating}}<ref>[https://twitter.com/GetCoinJar/status/875581525730787329 CoinJar answer on Twitter]</ref> || || || ||
|-
| Coinkite || || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| coinomi || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| DigitalBitbox || wallet(hardware) || {{Prefer}} || {{Acceptable}} || {{Prefer}}|| || ||
|-
| Échange de Montréal || exchange || {{Prefer}}<ref name="echangedemontreal" /> || {{Prefer}}<ref name="echangedemontreal" /> || || ||
|-
| Electrum || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| Kraken || exchange || || || || || ||
|-
| LightningASIC || miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| OneHash || betting || {{Prefer}}<ref>[https://blog.onehash.com/sick-of-presidential-election-3f1a2defbbbf OneHash, "Sick of presidential election ?!"]</ref> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Poloniex || exchange || || || || || ||
|-
| Slushpool || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||
|-
| TheRockTrading || exchange || || {{Evaluating}}<ref>[https://twitter.com/TheRockTrading/status/872464394034315269 @TheRockTrading message on Twitter]</ref> || || || ||
|-
| Vaultoro || exchange || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||
|-
| Walltime || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||
|-
| Xapo || wallet || {{Prefer}}<ref name="coindance" /> || || || {{Prefer}} || {{Prefer}}<ref>[https://twitter.com/tedmrogers/status/867362691370954752 Tweet by president of Xapo]</ref> ||
|-
|}

<references>
<ref name="bccore_swadoption">[https://bitcoincore.org/en/segwit_adoption/ Bitcoin Core's Segwit adoption list]</ref>
<ref name="coindance">[https://coin.dance/poli Coin Dance, "Global Bitcoin Political Support & Public Opinion"]</ref>
<ref name="silbert">[https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77 Digital Currency Group, "Bitcoin Scaling Agreement at Consensus 2017"]</ref>
<ref name="echangedemontreal">[https://twitter.com/echangedemtl/status/875781093261271040 Échange de Montréal on twitter]</ref>
</references>

Segwit support

2017-06-14T23:52:57Z

Kalle:

<big><big>'''PLEASE NOTE:''' This list is not yet complete.</big></big>

'''Developers: Please add a row for yourself to reflect your positions. If for some reason you don't already have a wiki account that can edit the page, make an account and ask luke-jr for help if you get caught in the anti-spam.'''

{| class="wikitable"
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)
|-
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support
|-
| {{Evaluating}} || still evaluating the idea
|-
| {{AccJuly}} || it is a workable solution, provided it is activated before August 1 (and therefore BIP148-compatible)
|-
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support
|-
| {{Weak}} || better than nothing at all
|-
| {{Acceptable}} || it is a workable solution
|-
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences
|}



''Note that support for BIP148 does not mean developers support merging it into Core.''

{| class="wikitable sortable"
! rowspan=2 colspan=2 | Developer & affiliation* 
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| ฿tcDrak || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Bryan Bishop || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Andrew Chow || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Matt Corallo || Core || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||
|-
| Johnathan Corgan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Luke Dashjr || Core || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No}} || {{Deficient}}
|-
| Christian Decker || Core || {{Prefer}} || {{Acceptable}} || || || ||
|-
| Nicolas Dorier || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{AccJuly}} || ||
|-
| Marco Falke || Core || {{Prefer}} || {{Deficient}} || {{Prefer}} || {{Deficient}} || ||
|-
| Mark Friedenbach || BIP 68/112 || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No|LOL}} || {{No|Nope}}
|-
| Pavel Janik || Core || {{Prefer}} || {{No}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}
|-
| Thomas Kerin || Core || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}
|-
| Johnson Lau || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||
|-
| Eric Lombrozo || || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{Weak}} || {{No}} || {{No}}
|-
| Greg Maxwell || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Alex Morcos || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| Pavol "stick" Rusnak || Trezor || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Rusty Russell || c-lightning || {{Prefer}} || {{Prefer}} || || || ||
|-
| Gregory Sanders || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||
|-
| Jonas Schnelli || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Jorge Timon || Core || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}
|-
| Peter Todd || Core || {{Prefer}} || {{Acceptable}} || || || ||
|-
| Warren Togami || Elements || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||
|-
| Wladimir van der Laan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|-
| Leo Wandersleb || Mycelium || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}
|-
| Pieter Wuille || Core || {{Prefer}} || || || || {{No}} ||
|-
| Karl-Johan Alm || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}
|}

* "affiliation" is an optional field for the company or project the individual is associated with, that most qualifies the person to comment on the matter and is not meant as a company or project endorsement of the individual's position.

<hr>

<big><big>'''PLEASE NOTE:''' This list is not yet complete, nor completely vetted by the parties listed for accuracy.</big></big>

{| class="wikitable sortable"
! rowspan=2 colspan=2 | Company
! Segwit itself
! colspan=3 | Deployment methods
! colspan=2 | Hardfork bundles (Silbert agreement)
|-
! [https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP 141] !! [https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki BIP 148] !! [https://github.com/bitcoin/bips/blob/master/bip-0149.mediawiki BIP 149] !! [https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki BIP 91] || Segwit2x || [https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014445.html COOP]
|-
| Bitfury || miner || {{Prefer}} || {{Acceptable}} || || || {{AccJuly}} ||
|-
| Coinbase || wallet || {{Prefer}} || {{Evaluating}} || {{Weak}} || || {{AccJuly}} ||
|-
| Xapo || wallet || {{Prefer}} || {{Evaluating}} || || || {{AccJuly}} ||
|-
| Blockchain.info || wallet || {{Prefer}} || {{Evaluating}} || {{Weak}} || || {{AccJuly}} ||
|-
| Kraken || exchange || {{Prefer}} || {{Acceptable}} || || || {{AccJuly}} ||
|-
| Bitstamp|| exchange || {{Prefer}} || {{Acceptable}} || || || {{Acceptable}} ||
|-
| Bitfinex|| exchange || {{Prefer}} || {{Acceptable}} || || || {{Acceptable}} ||
|-
| Bitpay|| wallet || {{Prefer}} || {{No}} || || || {{Prefer}} ||
|-
| Localbitcoins|| exchange || {{Prefer}} || {{Acceptable}} || {{Weak}} || || {{AccJuly}} ||
|-
| Poloniex|| exchange || {{Prefer}} || {{Wanting}} || || || {{AccJuly}} ||
|-
| Bitmain|| miner || {{No}} || {{No}} || || || {{Prefer}} ||
|-

|}