diff options
| author | Anthony Towns <aj@erisian.com.au> | 2021-06-12 19:15:29 +1000 |
|---|---|---|
| committer | Anthony Towns <aj@erisian.com.au> | 2021-07-02 14:47:16 +1000 |
| commit | 0cbc8674dd642702fca2037fb105d3277381b784 (patch) | |
| tree | bbff69952aa8c62bf70b69fad9948b245b78fc67 | |
| parent | a8787c51ff7835d35de930d54aa8045aac19c129 (diff) | |
| download | bips-0cbc8674dd642702fca2037fb105d3277381b784.tar.xz | |
BIP118: refer to bech32m instead of bech32 for segwit v1 outputs
Thanks to Ben Carman for spotting.
| -rw-r--r-- | bip-0118.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0118.mediawiki b/bip-0118.mediawiki index 9596b95..bb66349 100644 --- a/bip-0118.mediawiki +++ b/bip-0118.mediawiki @@ -194,7 +194,7 @@ Nodes that have not upgraded to support [[bip-0341.mediawiki|BIP 341]] will see As such, nodes are strongly encourage to upgrade in order to fully validate signatures for the new public key type. Non-upgraded wallets can receive and send bitcoin from non-upgraded and upgraded wallets using SegWit version 0 programs, traditional pay-to-pubkey-hash, etc. -Depending on the implementation, non-upgraded wallets may be able to send to SegWit version 1 programs if they support sending to [[bip-0173.mediawiki|BIP173]] Bech32 addresses and do not consider the outputs non-standard, and therefore prevent transaction broadcast. +Depending on the implementation, non-upgraded wallets may be able to send to SegWit version 1 programs if they support sending to [[bip-0350.mediawiki|BIP350]] Bech32m addresses and do not prevent the transaction from being broadcast due to considering the outputs non-standard. == Revisions == |