https://en.bitcoin.it/w/api.php?action=feedcontributions&user=Jeremyrubin&feedformat=atomBitcoin Wiki - User contributions [en]2024-03-29T13:25:58ZUser contributionsMediaWiki 1.30.0https://en.bitcoin.it/w/index.php?title=Taproot_Uses&diff=68481Taproot Uses2021-03-08T20:34:08Z<p>Jeremyrubin: </p>
<hr />
<div>This page is an index of projects using Taproot in an interesting way. Please update with links.<br />
<br />
Phases Key:<br />
<br />
* Implemented: Real running code without major known deficiencies.<br />
* Spec: A detailed document describing how something should work.<br />
* Prototype: A component of something is built or a toy-level implementation.<br />
* Idea: A description of something which could be built.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Description !! Phase (Implemented, Spec, Prototype, Idea)<br />
|-<br />
| Taproot Ring Signatures || https://github.com/jonasnick/taproot-ringsig || Ring Signatures over all Taproot outputs. || Prototype<br />
|-<br />
| LNP Node || https://github.com/LNP-BP/lnp-node || Run the lightning network. || Implemented<br />
|-<br />
| Bitcoin Pro || https://github.com/pandoracore/bitcoin-pro || Issue RGB assets. || Implemented<br />
|-<br />
| The Farcaster Project || https://github.com/farcaster-project || Atomic Swaps || Implemented<br />
|-<br />
| MyCitadel Wallet || https://github.com/mycitadel/mycitadel-node || Send and receive bitcoins and RGB assets. || Implemented<br />
|-<br />
| Bitcoin Core Wallet Descriptor Support || https://github.com/bitcoin/bitcoin/pull/21365#issuecomment-792972451 || Handle Taproot descriptors for trees of key-only scripts. || Prototype/Implemented<br />
|-<br />
| Lightning in a Taproot World || https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-December/002375.html || Description of LN with Taproot. || Idea<br />
|-<br />
| Multi-Hop Locks from Scriptless Scripts || https://github.com/ElementsProject/scriptless-scripts/blob/master/md/multi-hop-locks.md || Description of LN with Taproot || Spec, No Implementation<br />
|-<br />
|}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Taproot_Uses&diff=68480Taproot Uses2021-03-08T19:18:53Z<p>Jeremyrubin: </p>
<hr />
<div>This page is an index of projects using Taproot in an interesting way. Please update with links.<br />
<br />
Phases Key:<br />
<br />
* Implemented: Real running code without major known deficiencies.<br />
* Spec: A detailed document describing how something should work.<br />
* Prototype: A component of something is built or a toy-level implementation.<br />
* Idea: A description of something which could be built.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Description !! Phase (Implemented, Spec, Prototype, Idea)<br />
|-<br />
| Taproot Ring Signatures || https://github.com/jonasnick/taproot-ringsig || Ring Signatures over all Taproot outputs. || Prototype<br />
|-<br />
| LNP Node || https://github.com/LNP-BP/lnp-node || Run the lightning network. || Implemented<br />
|-<br />
| Bitcoin Pro || https://github.com/pandoracore/bitcoin-pro || Issue RGB assets. || Implemented<br />
|-<br />
| The Farcaster Project || https://github.com/farcaster-project || Atomic Swaps || Implemented<br />
|-<br />
| MyCitadel Wallet || https://github.com/mycitadel/mycitadel-node || Send and receive bitcoins and RGB assets. || Implemented<br />
|-<br />
| Bitcoin Core Wallet Descriptor Support || https://github.com/bitcoin/bitcoin/pull/21365#issuecomment-792972451 || Handle Taproot descriptors for trees of key-only scripts. || Prototype/Implemented<br />
|}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Taproot_Uses&diff=68479Taproot Uses2021-03-08T19:18:38Z<p>Jeremyrubin: </p>
<hr />
<div>This page is an index of projects using Taproot in an interesting way. Please update with links.<br />
<br />
Phases Key:<br />
<br />
* Implemented: Real running code without major known deficiencies.<br />
* Spec: A detailed document describing how something should work.<br />
* Prototype: A component of something is built or a toy-level implementation.<br />
* Idea: A description of something which could be built.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Description !! Phase (Implemented, Spec, Prototype, Idea)<br />
|-<br />
| Taproot Ring Signatures || https://github.com/jonasnick/taproot-ringsig || Ring Signatures over all Taproot outputs. || Prototype<br />
|-<br />
| LNP Node || https://github.com/LNP-BP/lnp-node || Run the lightning network. || Implemented<br />
|-<br />
| Bitcoin Pro || https://github.com/pandoracore/bitcoin-pro || Issue RGB assets. || Implemented<br />
|-<br />
| The Farcaster Project || https://github.com/farcaster-project || Atomic Swaps || Implemented<br />
|-<br />
| MyCitadel Wallet || https://github.com/mycitadel/mycitadel-node || Send and receive bitcoins and RGB assets. || Implemented<br />
| Bitcoin Core Wallet Descriptor Support || https://github.com/bitcoin/bitcoin/pull/21365#issuecomment-792972451 || Handle Taproot descriptors for trees of key-only scripts. || Prototype/Implemented<br />
|}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Taproot_Uses&diff=68471Taproot Uses2021-03-06T23:53:44Z<p>Jeremyrubin: </p>
<hr />
<div>This page is an index of projects using Taproot in an interesting way. Please update with links.<br />
<br />
Phases Key:<br />
<br />
* Implemented: Real running code without major known deficiencies.<br />
* Spec: A detailed document describing how something should work.<br />
* Prototype: A component of something is built or a toy-level implementation.<br />
* Idea: A description of something which could be built.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Description !! Phase (Implemented, Spec, Prototype, Idea)<br />
|-<br />
| Taproot Ring Signatures || https://github.com/jonasnick/taproot-ringsig || Ring Signatures over all Taproot outputs. || Prototype<br />
|}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Taproot_Uses&diff=68470Taproot Uses2021-03-06T23:50:56Z<p>Jeremyrubin: This page is an index of projects using Taproot in an interesting way. Please update with links.</p>
<hr />
<div>This page is an index of projects using Taproot in an interesting way. Please update with links.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Link !! Description !! Phase (Spec, Prototype, Idea)<br />
|-<br />
| Taproot Ring Signatures || https://github.com/jonasnick/taproot-ringsig || Ring Signatures over all Taproot outputs.<br />
|}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Signet&diff=68301Signet2020-12-16T01:53:32Z<p>Jeremyrubin: /* Custom Signet */</p>
<hr />
<div>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.<br />
<br />
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>.<br />
<br />
==Differences==<br />
<br />
* Default Bitcoin network protocol listen port is 38333 (instead of 8333)<br />
* Default RPC connection port is 38332 (instead of 8332)<br />
* A different value of ADDRESSVERSION field ensures no signet Bitcoin addresses will work on the production network. (0x6F rather than 0x00)<br />
* 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]]<br />
* Genesis block has timestamp 1598918400, nonce 52613770, and difficulty 0x1e0377ae.<br />
* Segwit is always enabled<br />
* 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)<br />
<br />
==Why run Signet?==<br />
<br />
* You are an Instructor, and want to run a controlled Bitcoin network environment for teaching purposes.<br />
* You are a Software Developer, and want to test your software.<br />
* You want to try out experimental changes that you want to implement in Bitcoin.<br />
* 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.<br />
* 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).<br />
<br />
==Genesis Block and Message Header==<br />
<br />
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].<br />
<br />
==Getting Started==<br />
<br />
NOTE: signet (IV) was merged into the master branch of Bitcoin Core as of https://github.com/bitcoin/bitcoin/pull/18267<br />
<br />
===Fetch and compile signet===<br />
<br />
<pre><br />
$ git clone https://github.com/bitcoin/bitcoin<br />
$ cd bitcoin<br />
$ ./autogen.sh<br />
$ ./configure<br />
$ make -j5<br />
</pre><br />
<br />
===Create bitcoin.conf file and start up the daemon===<br />
<br />
<pre><br />
$ cd src<br />
$ mkdir signet<br />
$ echo "signet=1<br />
daemon=1" > signet/bitcoin.conf<br />
$ ./bitcoind -datadir=signet<br />
</pre><br />
<br />
===Verify that you're connected===<br />
<br />
<pre><br />
$ ./bitcoin-cli -datadir=signet getconnectioncount<br />
***SHOULD BE MORE THAN ZERO***<br />
$ ./bitcoin-cli -datadir=signet getblockcount<br />
***SHOULD BE MORE THAN ZERO***<br />
</pre><br />
<br />
===Get some coins===<br />
<br />
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.<br />
<br />
====Using online faucet====<br />
<br />
You first need an address<br />
<br />
<pre><br />
$ ./bitcoin-cli -datadir=signet getnewaddress<br />
</pre><br />
<br />
Then go to a faucet, e.g. https://signet.bc-2.jp and enter your address.<br />
<br />
====Using the command line tool====<br />
<br />
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.<br />
<br />
<pre><br />
$ cd ../contrib/signet<br />
$ ./getcoins.sh -datadir=../../src/signet<br />
Payment of 10.00000000 BTC sent with txid c0bfa...<br />
</pre><br />
<br />
===Check that you received the coins===<br />
<br />
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.<br />
<br />
You can immediately see the amount using <code>getunconfirmedbalance</code> i.e.<br />
<br />
<pre><br />
$ cd ../../src # if you were in contrib/signet<br />
$ ./bitcoin-cli -datadir=signet getunconfirmedbalance<br />
</pre><br />
<br />
You can also see info about the transaction that the faucet gave you.<br />
<br />
<pre><br />
$ ./bitcoin-cli -datadir=signet gettransaction THETXID<br />
</pre><br />
<br />
Once it has confirmed, you should see it in <code>getbalance</code>.<br />
<br />
<pre><br />
$ ./bitcoin-cli -datadir=signet getbalance<br />
</pre><br />
<br />
==External links==<br />
<br />
* [https://github.com/bitcoin/bitcoin/pull/18267 Pull request #18267 to Bitcoin Core]<br />
* [https://github.com/rust-bitcoin/rust-bitcoin/pull/291 Pull request #291 to Rust-Bitcoin]<br />
* [https://gist.github.com/kallewoof/98b6d8dbe126d2b6f47da0ddccd2aa5a Github gist explaining how to get started]<br />
<br />
===Faucets===<br />
<br />
* https://signet.bc-2.jp/<br />
<br />
Can also ping @kallewoof on IRC (freenode)/Twitter.<br />
<br />
Faucet source code, if you want your own:<br />
<br />
* https://github.com/kallewoof/bitcoin-faucet.git (node.js and mongodb)<br />
* https://github.com/stepansnigirev/tinyfaucet.git (python)<br />
<br />
===Block explorers===<br />
<br />
* https://explorer.bc-2.jp/<br />
<br />
==Custom Signet==<br />
<br />
'''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/generate.py</code>.<br />
<br />
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.<br />
<br />
===Generating keys used for signing a block===<br />
<br />
The most straightforward way is to simply start up a regtest node and then generating a new key from there.<br />
<br />
<pre><br />
$ cd PATHTOBITCOIN/bitcoin/src<br />
$ ./bitcoind -regtest -daemon -wallet="test"<br />
$ ADDR=$(./bitcoin-cli -regtest getnewaddress)<br />
$ PRIVKEY=$(./bitcoin-cli -regtest dumpprivkey $ADDR)<br />
$ ./bitcoin-cli -regtest getaddressinfo $ADDR | grep pubkey<br />
"pubkey": "THE_REAL_PUBKEY",<br />
</pre><br />
<br />
We need to jot down the privkey (<code>echo $PRIVKEY</code>) and the pubkey (here <code>THE_REAL_PUBKEY</code>).<br />
<br />
===Defining the block script===<br />
<br />
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<br />
* <code>51</code> "1" (signature count)<br />
* <code>21</code> Push 0x21=33 bytes (the length of our pubkey above)<br />
* <code>THE_REAL_PUBKEY</code> (our pubkey)<br />
* <code>51</code> "1" (pubkey count)<br />
* <code>ae</code> <code>OP_CHECKMULTISIG</code> opcode<br />
<br />
Put together, our <code>-signetchallenge</code> value becomes <code>5121...51ae</code>. Where <code>...</code> stands for <code>THE_REAL_PUBKEY</code> (see above).<br />
<br />
===Start up a node (issuer)===<br />
<br />
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).<br />
<br />
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.<br />
<br />
<pre><br />
$ ./bitcoin-cli -regtest stop<br />
$ datadir=$HOME/signet-custom<br />
$ mkdir $datadir<br />
$ echo "signet=1<br />
[signet]<br />
daemon=1<br />
signetchallenge=5121...51ae # fill in THE_REAL_PUBKEY" > $datadir/bitcoin.conf<br />
$ ./bitcoind -datadir=$datadir -wallet="test"<br />
$ ./bitcoin-cli -datadir=$datadir importprivkey $PRIVKEY<br />
</pre><br />
<br />
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.<br />
<br />
===Run issuer===<br />
<br />
Lastly, we start an issuer using <code>bitcoin-util</code>:<br />
<br />
<pre><br />
$ 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<br />
</pre><br />
<br />
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.)<br />
<br />
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.<br />
<br />
===Example Script===<br />
<br />
A full example script can be found at https://en.bitcoin.it/wiki/Signet:Custom:Script<br />
<br />
[[Category:Technical]]<br />
[[Category:Developer]]<br />
<br />
{{Bitcoin Core documentation}}</div>Jeremyrubinhttps://en.bitcoin.it/w/index.php?title=Segwit_support&diff=63480Segwit support2017-06-19T19:11:08Z<p>Jeremyrubin: </p>
<hr />
<div><big><big>'''PLEASE NOTE:''' This list is not yet complete.</big></big><br />
<br />
'''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.'''<br />
<br />
{| class="wikitable"<br />
| {{No}} || doesn't support (but might or might not go along with it with sufficient community support)<br />
|-<br />
| {{Deficient}} || okay with the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Evaluating}} || still evaluating the idea<br />
|-<br />
| {{AccJuly}} || it is a workable solution, provided it is activated before August 1 (and therefore BIP148-compatible)<br />
|-<br />
| {{Wanting}} || positively likes the idea, but considers it to have insufficient community support<br />
|-<br />
| {{Weak}} || better than nothing at all<br />
|-<br />
| {{Acceptable}} || it is a workable solution<br />
|-<br />
| {{Prefer}} || it is what he would choose if it was only up to him and no outside influences<br />
|}<br />
<br />
<!-- README: please keep alphabetically ordered by surname! --><br />
<br />
''Note that support for a given proposal does not mean developers support merging it into Core or any other specific codebase.''<br />
<br />
{| class="wikitable sortable"<br />
! rowspan=2 | Developer<br />
! rowspan=2 | Aff* <!-- Using one year before the the creation date of this page as the benchmark. Do not list yourself as affiliated with a project that you haven't made meaningful contributions to since then. --><br />
! Segwit itself<br />
! colspan=3 | Deployment methods<br />
! colspan=2 | Hardfork bundles (Silbert agreement)<br />
|-<br />
! [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]<br />
|-<br />
| Karl-Johan Alm || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Bryan Bishop || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| ฿tcDrak || Core || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Andrew Chow || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Wang Chun || [[F2Pool]] || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{Acceptable}} || {{AccJuly}} ||<br />
|-<br />
| Matt Corallo || Core || {{Prefer}} || {{No}} || || {{Acceptable}} || {{No|LOL}} ||<br />
|-<br />
| Johnathan Corgan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Luke Dashjr || Core || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No}} || {{Deficient}}<br />
|-<br />
| Christian Decker || c-lightning || {{Prefer}} || {{Acceptable}} || || || || <br />
|-<br />
| Nicolas Dorier || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{AccJuly}} || ||<br />
|-<br />
| Thaddeus Dryja || lit || {{Prefer}} || {{No}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Marco Falke || Core || {{Prefer}} || {{Deficient}} || {{Prefer}} || {{Deficient}} || ||<br />
|-<br />
| Mark Friedenbach || BIP 68/112 || {{Prefer}} || {{Prefer}} || {{No}} || {{AccJuly}} || {{No|LOL}} || {{No|Nope}}<br />
|-<br />
| Pavel Janik || Core || {{Prefer}} || {{No}} || {{Acceptable}} || {{No}} || {{No}} || {{No}}<br />
|-<br />
| Thomas Kerin || Core || {{Prefer}} || {{Wanting}} || {{Prefer}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Johnson Lau || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || ||<br />
|-<br />
| Eric Lombrozo || || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{AccJuly}} || {{No}} || {{No}}<br />
|-<br />
| Greg Maxwell || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Alex Morcos || Core || {{Prefer}} || {{Deficient}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| nopara73 || TumbleBit || {{Weak}} || {{Wanting}} || {{Prefer}} || || ||<br />
|-<br />
| Laolu "roasbeef" Osuntokun || lnd || {{Prefer}} || || || || {{No}} ||<br />
|-<br />
| Jeremy Rubin || Core || {{Prefer}} || {{Deficient}} || {{No}} || {{AccJuly}} || {{No}} || {{No}}<br />
|-<br />
| Pavol "stick" Rusnak || Trezor || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{AccJuly}} || {{No}} || {{No}}<br />
|-<br />
| Rusty Russell || c-lightning || {{Prefer}} || {{Prefer}} || || || ||<br />
|-<br />
| Gregory Sanders || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Weak}} || {{No}} ||<br />
|-<br />
| Jonas Schnelli || Core || {{Prefer}} || {{Wanting}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Patrick Strateman || Core || {{Prefer}} || || || || {{No}} || {{No}}<br />
|-<br />
| Paul Sztorc || || {{Prefer}} || {{Deficient}} || {{Wanting}} || {{AccJuly}} || {{Evaluating}} || {{No}}<br />
|-<br />
| Amir Taaki || libbtc || {{Acceptable}} || {{Prefer}} || || || {{No}} || {{No}} <br />
|-<br />
| Jorge Timon || Core || {{Prefer}} || {{No}} || {{Prefer}} || {{Deficient}} || {{No}} || {{No}}<br />
|-<br />
| Peter Todd || Core || {{Prefer}} || {{Acceptable}} || || || ||<br />
|-<br />
| Warren Togami || Elements || {{Prefer}} || {{Prefer}} || {{Acceptable}} || || ||<br />
|-<br />
| Wladimir van der Laan || Core || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Acceptable}} || {{No}} || {{No}}<br />
|-<br />
| Leo Wandersleb || Mycelium || {{Prefer}} || {{Prefer}} || {{Acceptable}} || {{Weak}} || {{No}} || {{No}}<br />
|-<br />
| Pieter Wuille || Core || {{Prefer}} || || || || {{No}} ||<br />
|}<br />
<br />
* "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.<br />
<br />
<hr><br />
<br />
'''When adding companies below, sources for each position MUST be provided.'''<br />
<br />
{| class="wikitable sortable"<br />
! rowspan=2 | Company <br />
! rowspan=2 | Service<br />
! Segwit itself<br />
! colspan=3 | Deployment methods<br />
! colspan=2 | Hardfork bundles (Silbert agreement)<br />
|-<br />
! [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]<br />
|-<br />
| Abra || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||<br />
|-<br />
| Bitcoin India || exchange/miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| 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"/><br />
|-<br />
| Bitfinex || exchange || {{Acceptable}}<ref name="coindance" /> || {{Acceptable}} || || || ||<br />
|-<br />
| Bitfury || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}} || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||<br />
|-<br />
| 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" /> ||<br />
|-<br />
| 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}}<br />
|-<br />
| Bitpay || wallet || {{Prefer}}<ref name="bccore_swadoption"/> || {{No}} || || {{Prefer}} || {{Prefer}}<ref name="silbert" /> ||<br />
|-<br />
| 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> ||<br />
|-<br />
| Bitrefill || merchant || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| 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"/> || || || ||<br />
|-<br />
| Bitstamp || exchange || || || || || ||<br />
|-<br />
| Bittylicious || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref>[https://twitter.com/Bittylicious_/status/867305106668224513 Bittylicious answer on Twitter]</ref> || || || ||<br />
|-<br />
| Blockchain.info || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> || <br />
|-<br />
| blockonomics || || {{Prefer}} || {{Prefer}}<ref>[https://twitter.com/blockonomics_co/status/851738251509497856 blockonomics announcement on Twitter]</ref> || || || ||<br />
|-<br />
| 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"/> ||<br />
|-<br />
| Ciphrex || wallet / dev stack || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||<br />
|-<br />
| Coinbase || wallet || {{Acceptable}}<ref name="bccore_swadoption"/> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> || <br />
|-<br />
| CoinGate || exchange || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| CoinJar || wallet || || {{Evaluating}}<ref>[https://twitter.com/GetCoinJar/status/875581525730787329 CoinJar answer on Twitter]</ref> || || || ||<br />
|-<br />
| Coinkite || || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| coinomi || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| DigitalBitbox || wallet(hardware) || {{Prefer}} || {{Acceptable}} || {{Prefer}}|| || ||<br />
|-<br />
| Échange de Montréal || exchange || {{Prefer}}<ref name="echangedemontreal" /> || {{Prefer}}<ref name="echangedemontreal" /> || || ||<br />
|-<br />
| Electrum || wallet || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| Kraken || exchange || || || || || ||<br />
|-<br />
| LightningASIC || miner || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| OneHash || betting || {{Prefer}}<ref>[https://blog.onehash.com/sick-of-presidential-election-3f1a2defbbbf OneHash, "Sick of presidential election ?!"]</ref> || || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||<br />
|-<br />
| Poloniex || exchange || || || || || ||<br />
|-<br />
| Slushpool || miner || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || || ||<br />
|-<br />
| TheRockTrading || exchange || || {{Evaluating}}<ref>[https://twitter.com/TheRockTrading/status/872464394034315269 @TheRockTrading message on Twitter]</ref> || || || ||<br />
|-<br />
| Vaultoro || exchange || {{Prefer}}<ref name="coindance" /> || {{Acceptable}}<ref name="coindance" /> || || {{AccJuly}} || {{AccJuly}}<ref name="silbert" /> ||<br />
|-<br />
| Walltime || || {{Prefer}}<ref name="coindance" /> || {{Prefer}}<ref name="coindance" /> || || || ||<br />
|-<br />
| Xapo || wallet || {{Prefer}}<ref name="coindance" /> || || || {{Prefer}} || {{Prefer}}<ref>[https://twitter.com/tedmrogers/status/867362691370954752 Tweet by president of Xapo]</ref> || <br />
|-<br />
|}<br />
<br />
<references><br />
<ref name="bccore_swadoption">[https://bitcoincore.org/en/segwit_adoption/ Bitcoin Core's Segwit adoption list]</ref><br />
<ref name="coindance">[https://coin.dance/poli Coin Dance, "Global Bitcoin Political Support & Public Opinion"]</ref><br />
<ref name="silbert">[https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77 Digital Currency Group, "Bitcoin Scaling Agreement at Consensus 2017"]</ref><br />
<ref name="echangedemontreal">[https://twitter.com/echangedemtl/status/875781093261271040 Échange de Montréal on twitter]</ref><br />
</references></div>Jeremyrubin