Skip to main content
deleted 23 characters in body
Source Link
Pieter Wuille
  • 109.7k
  • 9
  • 202
  • 318

Simply, There's no big difference for users justbetween the two. The fee is lower while using native Segwit address (bech32), and the address format differs.

let's get back toLet's look at the motivations of bech32 address authors:

  • oldOld addresses (base58) needsneed a lot of space in QR codes, as it cannot use the alphanumeric mode.
  • The mixed case in (old addresses) base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud.
  • base58Base58 addresses have double SHA256 checksum which is slow and have no error-detection guarantees.
  • Base58 decoding is complicated and relatively slow.

also, aAnother good reason I found,: recently there were too many forks forof Bitcoin source and almost all these new cryptocurrencies were using the same address prefix, so the mess was all over. andwhich resulted in people were mistakenly sending BitcoinBTC to these addresses.

Simply, There's no big difference for users just the fee is lower while using native Segwit address (bech32) and address format.

let's get back to the motivations of bech32 address authors:

  • old addresses (base58) needs a lot of space in QR codes, as it cannot use the alphanumeric mode.
  • The mixed case in (old addresses) base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud.
  • base58 addresses have double SHA256 checksum which is slow and have no error-detection guarantees.
  • Base58 decoding is complicated and relatively slow.

also, a good reason I found, recently there were too many forks for Bitcoin source and almost all new cryptocurrencies were using the same address prefix, so the mess was all over. and people were mistakenly sending Bitcoin to these addresses.

There's no big difference for users between the two. The fee is lower while using native Segwit address (bech32), and the address format differs.

Let's look at the motivations of bech32 address authors:

  • Old addresses (base58) need a lot of space in QR codes, as it cannot use the alphanumeric mode.
  • The mixed case in (old addresses) base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud.
  • Base58 addresses have double SHA256 checksum which is slow and have no error-detection guarantees.
  • Base58 decoding is complicated and relatively slow.

Another good reason: recently there were many forks of Bitcoin and almost all these new cryptocurrencies were using the same address prefix, which resulted in people mistakenly sending BTC to these addresses.

Source Link
Tailer
  • 3.7k
  • 1
  • 17
  • 36

Simply, There's no big difference for users just the fee is lower while using native Segwit address (bech32) and address format.

let's get back to the motivations of bech32 address authors:

  • old addresses (base58) needs a lot of space in QR codes, as it cannot use the alphanumeric mode.
  • The mixed case in (old addresses) base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud.
  • base58 addresses have double SHA256 checksum which is slow and have no error-detection guarantees.
  • Base58 decoding is complicated and relatively slow.

also, a good reason I found, recently there were too many forks for Bitcoin source and almost all new cryptocurrencies were using the same address prefix, so the mess was all over. and people were mistakenly sending Bitcoin to these addresses.