Bitcoin Wiki - User contributions [en]

User:Duncan

2023-10-24T07:17:08Z

Duncan:

IRC: dunxen

Twitter: [https://twitter.com/dunxen dunxen]

GitHub: [https://github.com/dunxen dunxen]

Keybase: [https://keybase.io/dunxen dunxen]

Bech32 adoption

2021-11-13T14:51:45Z

Duncan:

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Yes|Since 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Yes|Since 2.2.0}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Planned|Planned around activation}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|Depends on python-bitcointx}} || {{Evaluating|??}} ||
|-
| Blockstream Green || {{Yes}} || {{Yes}} || {{Yes|Mobile 3.7.6+, Desktop 1.0.4+}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47]
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{No|Currently not planned}} || https://twitter.com/SamouraiWallet/status/1415788631491497985?s=20
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Planned}} || {{Planned}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Planned|Planned before activation}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|Dependent on BitcoinJ}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Planned|Before activation}} || {{Planned|After activation}} || https://twitter.com/MuunWallet/status/1415692517690023937
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Sparrow Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/SparrowWallet/status/1415632270434705408
|-
| Specter Wallet || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/_benkaufman/status/1431293856675508228
|-
| C-Lightning || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} ||
|-
| Fully Noded || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Since v0.2.26}} || https://twitter.com/FullyNoded/status/1438652812410298370
|-
| [https://github.com/unchained-capital/caravan Caravan] || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} ||
|-
| AQUA || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| LND || {{Yes}} || {{Yes}} || {{Planned|Planned: via btcsuite}} || {{Evaluating|??}} ||
|-
| Exodus || {{Yes}} || {{Yes}} || {{Planned|Planned before activation, depends on bitcoinjs}} || {{No|Not yet planned}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: after Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Planned|Planned: at activation}} || {{Planned|Planned: at activation}} || [https://twitter.com/darosior/status/1432371465815568390 Announced at Surfin' Bitcoin]
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockstream Jade + Blockstream Green || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned}} || Bech32m sending support as of [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 GDK 0.0.47] available via Blockstream Green mobile apps 3.7.6+ and desktop app 1.0.4+
|}

=== Web Wallets / Wallet Service Providers ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Full native segwit support on v2 platform, no plans to add native segwit support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9, Taproot: https://blog.bitgo.com/taproot-support-for-bitgo-wallets-9ed97f412460
|-
| blockchain.com web|| {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://twitter.com/Pellicceama/status/1436324051803414535
|-
| Fireblocks || {{Yes}} || {{Yes}} || {{Planned|Nov 18, 2021}} || {{Planned|Planned for 2022}} ||
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://blog.bitmex.com/introducing-bech32-deposits-on-bitmex-to-deepen-bitcoin-integration-lower-fees/
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Planned}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BSDEX || {{Yes}} || {{No}} || {{Evaluating|??}} || {{No}} ||
|-
| CardCoins.co || {{Yes}} || No deposits || {{Yes}} || No deposits || https://twitter.com/CardCoinsCo/status/1452680654030872589
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.zendesk.com/hc/en-us/articles/360018072678-Why-are-there-2-BTC-deposit-addresses-to-choose-from-
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Yes}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Planned|Planned}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://paxful.com/support/en-us/articles/360011766520-Can-I-Withdraw-Bitcoin-from-Paxful-Wallet-to-My-External-Wallet-
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| River.com || {{Yes}} || {{Yes}} || {{Planned|Planned before Activation}} || {{Evaluating|??}} ||
|-
| Square CashApp || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

To investigate bech32 capability, you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code> or look up the addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

To verify bech32m readiness, you can look up the mainnet TXID <code>b10c007c60e14f9d087e0291d4d0c7869697c6681d979c6639dbd960792b4d41</code> on which the first output should be addressed as <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqsyjer9e</code>. Note that the superseded bech32 encoding only differs in the last six characters that encode the checksum: <code>bc1pqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqszqgpqyqs_3wf0qm_</code>.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://chainflyer.bitflyer.jp
|-
| Blockbook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://btc3.trezor.io
|-
| blockchain.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.blockchain.com/explorer
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Yes|Ready, but old txns not reindexed yet}} || {{Yes|Ready, but old txns not reindexed yet}} || https://github.com/Blockchair/Blockchair.Support/issues/567#issuecomment-966393097, https://twitter.com/Blockchair/status/1458817396433731585
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| Insight || {{Yes}} || {{Yes}} || {{No}} || {{No}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| Mempool || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Open source explorer, instances include https://mempool.space https://mempool.ninja https://mempool.emzy.de https://mempool.bisq.services https://mempool.bitcoin.ninja https://mempool.bitaroo.net/
|-
| OKLink || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://www.oklink.com
|-
| OXT || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://oxt.me/
|-
| Tradeblock || {{Yes}} || {{Yes}} || {{No}} || {{No}} || https://tradeblock.com/bitcoin
|-
| WalletExplorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://walletexplorer.com/
|-
| Bitcoin Explorer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://bitcoinexplorer.org, https://twitter.com/BitcoinExplorer/status/1425148093977309187
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes|Supported since 1.3.0}} || https://twitter.com/NicolasDorier/status/1432354289599451136, https://twitter.com/NicolasDorier/status/1457527754350415873
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://sbicrypto.com SBICrypto Pool] || {{Yes}} || {{Acceptable|Ready to release at activation}} ||
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Planned|At activation}} || [https://twitter.com/braiins_systems/status/1432376840484794375 Tweet]
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/bitcoin/libbase58 libbase58] || C || {{No}} || n/a || {{No}} || n/a
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354289599451136
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Planned|In Review}} || {{Evaluating|??}} || https://github.com/bcoin-org/bcoin/pull/1038
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/btcsuite/btcutil/pull/202
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Yes|Since v6.0.0}} || {{Acceptable|Supported but needs manual involvement}} || https://github.com/bitcoinjs/bitcoinjs-lib/issues/1522#issuecomment-887468902, https://twitter.com/junderwood4649/status/1459006392086372355
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|??}} || https://github.com/bitcoinj/bitcoinj/commit/183986c9801f10f1bf46bd46621e535973d39ef8
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned|Planned for 2021}} || https://twitter.com/Chris_Stewart_5/status/1459205497463136270
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Yes}} || {{Evaluating|??}} || {{Yes}} || {{Evaluating|??}} || https://twitter.com/RCasatta/status/1423695925252329476
|-
| [https://lightningdevkit.org Lightning Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Yes}} || {{Evaluating|Pending BOLT update}} ||
|-
| [https://bitcoindevkit.org Bitcoin Dev Kit] || Rust || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://docs.rs/bdk
|-
| [https://github.com/ElementsProject/libwally-core libwally-core] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} || {{Yes|Since [https://github.com/ElementsProject/libwally-core/releases/tag/release_0.8.4 0.8.4]}} ||
|-
| [https://github.com/Blockstream/gdk GDK] || C || {{Yes}} || {{Yes}} || {{Yes|Since [https://github.com/Blockstream/gdk/releases/tag/release_0.0.47 0.0.47]}} || {{Evaluating|??}} ||
|-
| [https://github.com/Simplexum/python-bitcointx python-bitcointx] || Python || {{Yes}} || {{Yes}} || {{Planned|WIP}} || {{Planned|WIP}} || https://github.com/Simplexum/python-bitcointx/issues/57
|-
| [https://github.com/dgarage/NBXplorer/ NBXPlorer] || C# || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://twitter.com/NicolasDorier/status/1432354822888431619
|-
| [https://github.com/acinq/bitcoin-kmp Kotlin Multiplatform Bitcoin Library] || Kotlin || {{Yes}} || {{Yes}} || {{Yes}} || {{Planned}} || https://twitter.com/realtbast/status/1458533450919649284
|-
| [https://github.com/libbitcoin Libbitcoin] || C++ || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/chaintope/bitcoinrb Bitcoinrb] || Ruby || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || https://github.com/chaintope/bitcoinrb/wiki/Taproot
|}


=== References ===

[[Category:Software]]

Bech32 adoption

2021-07-10T15:30:08Z

Duncan:

[[Bech32]] is a bitcoin [[address]] format specified by [[BIP 0173]]. It is used for the native segwit version 0 output types, P2WPKH and P2WSH. The upcoming [[Taproot]] softfork will add another output type called Pay to Taproot (P2TR). P2TR outputs and future native segwit versions will be using an updated variant of [[Bech32]], called [[Bech32m]] (specified by [[BIP 0350]]). This page tracks the adoption of [[Bech32]] and [[Bech32m]].

Ideally wallets and services would first support ''sending to'' new addresses. When most wallets and services support sending to the new address type, people are more likely to adopt it for receiving.

The amount of bech32 addresses on the blockchain is tracked on this website: https://p2sh.info/dashboard/db/bech32-statistics?orgId=1

{| class="wikitable"
|-
| {{No}} ||
|-
| {{Evaluating|??}} || Maybe / Haven't checked / placeholder
|-
| {{Planned}} || The developers said they plan to
|-
| {{Acceptable|PR Merged}} || In the case of software, code has been written and merged, and it will be in next release.
|-
| {{Yes}} || Feature has been released
|}

=== Software Wallets ===
{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Bitcoin Core || {{Yes|Since 0.16.0}} || {{Yes|Since 0.16.0}} || {{Yes|Since 0.21.1}} || {{Acceptable|Starting with 22.0}} || Uses P2WPKH as default address since version [https://bitcoin.org/en/release/v0.20.0 0.20.0]. Creating P2TR addresses requires manual import for now.
|-
| Bitcoin Knots || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| bcoin || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Electrum || {{Yes}} || {{Yes}} || {{Yes|Since 4.1.0}} || {{Evaluating|??}} ||
|-
| Armory || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| JoinMarket || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| GreenAddress || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Breadwallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/BRDapp/comments/9xx1hq/as_of_today_brd_fully_supports_native_segwit/
|-
| Samourai Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinomi || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://www.reddit.com/r/Bitcoin/comments/865qn1/coinomi_wallet_beta_has_segwit_support/ reddit source]
|-
| BTC.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Casa || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Mycelium || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://play.google.com/store/apps/details?id=de.schildbach.wallet Bitcoin Wallet for Android] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Wasabi Wallet || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| Trust Wallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://trustwallet.com/blog/trust-wallet-adds-support-for-btc-ltc-bch official blog]
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || [https://twitter.com/GuardaWallet/status/1194270398730448896 twitter announcement]
|-
| Bisq || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || As of v1.5.0 https://bisq.network/blog/bisq-v1.5.0-highlights/
|-
| Muun || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BlueWallet || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Hardware Wallets ===

Hardware wallet manufacturers typically publish a web wallet or browser add-on wallet for use with their hardware. Users can also sometimes connect their hardware wallet to a software wallet like [[Electrum]].

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Trezor Suite || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger Live (desktop app) || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey chrome app || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox Desktop app || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Trezor + Electrum || {{Yes}} || {{Yes}} || {{Planned|Planned: before Activation}} || {{Planned|Planned: before Activation}} || https://twitter.com/pavolrusnak/status/1413790070205734916
|-
| Ledger + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitBox + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| KeepKey + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Archos + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coldcard + Electrum || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Ballet + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Tangem + app|| {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Web Wallets ===

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| Coinapult || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coin.Space || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| BitGo || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Full support on v2 platform, no plans to add support on v1 platform. Also see: https://blog.bitgo.com/native-segwit-addresses-via-bitgos-api-4946f2007be9
|-
| blockchain.info web|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/provoost/status/1037802325874761728
|-
| HolyTransaction || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://coinb.in Coinb.in] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || open source JavaScript implementation
|-
| Guarda Wallet || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/GuardaWallet/status/1194270398730448896
|}

=== Exchanges ===



{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| 1Fox || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://1fox.com/?c=en/content/blog&id=12
|-
| [[AgoraDesk]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Anycoin Direct || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://anycoindirect.eu/en/news/details/segwit-activated
|-
| BitBargain.co.uk || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Bitcoin.de || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitcoinblog.de/2018/08/10/bitcoin-de-aktiviert-segwit-kunden-sparen-gebuehren/
|-
| Bitfinex || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/bitfinex/status/1189164144789983234
|-
| BitMEX || {{yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://blog.bitmex.com/bitmex-enables-bech32-sending-support/
|-
| Bittrex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/gqt1m6/bittrex_does_not_even_support_withdrawals_to/
|-
| Bittylicious || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bittylicious_/status/998881327347888128
|-
| Bitstamp || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.bitstamp.net/article/weve-added-support-bech32-bitcoin-addresses-bitsta/
|-
| Bitso || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/Bitso/status/1203784055340314624?s=20
|-
| Bitwage || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| CEX.IO || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinbase.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/diogorsergio/status/983052769262292992 (Note that Coinbase commerce does not support sending to bech32)
|-
| CoinFalcon || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinfloor || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinfloor.co.uk/hodl/2020/09/16/a-few-updates-from-coinfloor/
|-
| [https://coinmate.io Coinmate.io] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://coinmate.io/blog/important-coinmate-update/
|-
| Coinsbank.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Coinygram || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Flyp.me || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| GDax || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/8c738k/coinbase_gdax_already_allows_sending_to_bc1/
|-
| Gemini || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://np.reddit.com/r/Bitcoin/comments/b66n0v/psa_gemini_is_full_on_with_native_segwit_and_uses/
|-
| Genesis || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Globitex || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| HitBTC || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Hodl Hodl || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@hodlhodl/hodl-hodl-segwit-compatible-exchange-a2231968ac56
|-
| Independent Reserve|| {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.independentreserve.com/bitcoin/investing
|-
| Itbit || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Kraken || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/krakenfx/status/1060306827848470528
|-
| LedgerX || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Liberalcoins || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://liberalcoins.com
|-
| [[LocalBitcoins]] || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/LocalBitcoins/status/1322194709159301120
|-
| Luno || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.luno.com/blog/en/post/luno-launches-support-for-bech32-addresses
|-
| Paxful.com || {{Evaluating|??}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Poloniex.com || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.reddit.com/r/Bitcoin/comments/a3jhcf/you_can_now_withdraw_from_poloniex_to_bech32/
|-
| TheRockTrading.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://twitter.com/TheRockTrading/status/976787499648512003
|-
| Walltime || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://walltime.info
|-
| Purse.io || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| www.bitwala.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Xapo || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}

=== Bitcoin ATM Models ===

Hopefully when a model updates then all its ATMs everywhere will gain that feature. See https://coinatmradar.com/shop/buy-bitcoin-atm/

{| class="wikitable sortable"
|-
! Name !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| GenesisCoin || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| General Bytes || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Depending on configuration. Since version 20190613 https://www.generalbytes.com/en/support/changelog
|-
| Lamassu Douro || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://medium.com/@LamassuSupport/announcing-crafty-chnemu-v7-3-9522fe2868
|}

=== Blockchain Explorers ===

For trying these out you can use mainnet TXIDs <code>4ef47f6eb681d5d9fa2f7e16336cd629303c635e8da51e425b76088be9c8744c</code> and <code>514a33f1d46179b89e1fea7bbb07b682ab14083a276979f91038369d1a8d689b</code>. And addresses <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code> and <code>bc1qc7slrfxkknqcq2jevvvkdgvrt8080852dfjewde450xdlk4ugp7szw5tk9</code>.

Some blockchain explorers can only parse the bech32 address and display it, they don't build an index so users cannot search for bech32 addresses.

See also: https://en.bitcoin.it/wiki/Category:Block_chain_browsers

{| class="wikitable sortable"
|-
! Name !! Display Bech32 !! Index Bech32 !! Display Bech32m !! Index Bech32m !! Notes
|-
| Apirone.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://apirone.com
|-
| bitaps.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitaps.com
|-
| Bitflyer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chainflyer.bitflyer.jp/
|-
| Bitupper Explorer || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://bitupper.com/en/explorer/bitcoin
|-
| blockchain.info || {{Yes}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| Blockchair || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://blockchair.com/
|-
| Blockcypher || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://live.blockcypher.com/btc
|-
| Blockonomics || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://www.blockonomics.co
|-
| Blockpath || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://blockpath.com
|-
| BTC.com || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://BTC.com
|-
| Esplora || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Open source explorer, instances are https://blockstream.info/ and https://www.localbitcoinschain.com/. [https://github.com/Blockstream/esplora/issues/323 Issue] for BIP350 support.
|-
| chaindex || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://chaindex.com/blockchain/
|-
| Insight || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || Open source explorer, instances include https://insight.bitpay.com/
|-
| OXT || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || https://oxt.me/
|-
| Tradeblock || {{No}} || {{No}} || {{Evaluating|??}} || {{Evaluating|??}} || https://tradeblock.com/bitcoin
|}

=== Payment Processors ===



{| class="wikitable sortable"
|-
! Name !! P2WPKH/P2WSH Invoices !! Bech32 Withdrawal addresses !! P2TR Invoices !! Bech32m Withdrawal addresses !! Notes
|-
| [https://apirone.com Apirone] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment notifications, merchant dashboard, plugins for Magento, WooCommerce, OpenCart 2, Opencart 3.x, Virtuemart
|-
| [https://bitaps.com Bitaps] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Payment forwarding API, Wallet API, fault tolerance callback.
|-
| [https://btcpayserver.org BTCPay Server] || {{Yes}} || {{Yes}} || {{Planned|Planned: via NBitcoin before Activation}} || {{Planned|Planned: via NBitcoin before Activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| [https://coingate.com CoinGate] || {{No}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://confirmo.net CONFIRMO] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://cryptochill.com CryptoChill] || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} || Highly customizable Bitcoin and Lightning Network payment gateway. Multi-sig, HD wallets, API, SDK.
|}

=== Mining Pools ===

{| class="wikitable sortable"
|-
! Name !! Payout to Bech32 !! Payout to Bech32m !! Notes
|-
| [https://pool.btc.com/ BTC.com Pool] || {{No}} || {{Evaluating|??}} ||
|-
| [http://ckpool.org/ Ckpool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://kano.is/ KanoPool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=789369.msg53374508#msg53374508 bitcointalk source]
|-
| [http://poolin.com/ Poolin] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5169994.msg52184844#msg52184844 bitcointalk source]
|-
| [https://slushpool.com/ Slush Pool] || {{Yes}} || {{Evaluating|??}} ||
|-
| [https://ukrpool.com/ Ukr Pool] || {{Yes}} || {{Evaluating|??}} || [https://bitcointalk.org/index.php?topic=5124825.msg51358033#msg51358033 bitcointalk source]
|-
| [https://pool.viabtc.com/ ViaBTC Pool] || {{No}} || {{Evaluating|??}} ||
|}

=== Libraries ===

{| class="wikitable sortable"
|-
! Name !! Language !! Send to Bech32 !! Receive to P2WPKH/P2WSH !! Send to Bech32m !! Receive to P2TR !! Notes
|-
| [https://github.com/MetacoSA/NBitcoin NBitcoin] || .NET || {{Yes}} || {{Yes}} || {{Planned|before activation}} || {{Planned|before activation}} || https://twitter.com/NicolasDorier/status/1413693010236170241
|-
| [https://github.com/bcoin-org/bcoin bcoin] || JS || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/btcsuite btcsuite/btcutil] || Go || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/bitcoinjs/bitcoinjs-lib bitcoinjs-lib] || JS || {{Yes}} || {{Yes}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://bitcoinj.github.io/ bitcoinj] || Java || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/bitcoin-s/bitcoin-s-core bitcoin-s] || Scala || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|-
| [https://github.com/rust-bitcoin/rust-bitcoin rust-bitcoin] || Rust || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} || {{Evaluating|??}} ||
|}



=== References ===

[[Category:Software]]

User:Duncan

2021-06-13T19:11:12Z

Duncan:

IRC: dunxen

Twitter: [https://twitter.com/dunxen dunxen]

GitHub: [https://github.com/duncandean duncandean]

Keybase: [https://keybase.io/duncandean duncandean]

User:Duncan

2021-01-04T13:05:03Z

Duncan: Created page with "IRC: sunon Twitter: [https://twitter.com/dunxen dunxen] GitHub: [https://github.com/duncandean duncandean] Keybase: [https://keybase.io/duncandean duncandean]"

IRC: sunon

Twitter: [https://twitter.com/dunxen dunxen]

GitHub: [https://github.com/duncandean duncandean]

Keybase: [https://keybase.io/duncandean duncandean]

Signet

2021-01-03T20:53:57Z

Duncan:

'''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/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==

'''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}}