There is quite a bit of online material regarding the rationale for this e.g.
The mixed case in base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud. The double SHA-256 checksum is slow and has no error-detection guarantees. Most of the research on error-detecting codes only applies to character-set sizes that are a prime power, which 58 is not
For future proofing, it would be good if the spec and examples here could align with current implementations, or there will end up being different competing serializations of the same terms
melvincarvalho
commented
3 years ago
In the spec, the bitcoin base58 encoding comes up a number of times
However, bitcoin itself, considers base58 to be legacy, and has moved to bech32
Adoption is noted here:
https://en.bitcoin.it/wiki/Bech32_adoption
There is quite a bit of online material regarding the rationale for this e.g.
For future proofing, it would be good if the spec and examples here could align with current implementations, or there will end up being different competing serializations of the same terms