Thanks to @ayrat555 I was prompted to find a better solution for supporting crypto currencies. Currency, in ISO standard world, formally refers to currencies registered in ISO 4217 and this standard, while supporting private-use currency codes, does not easily support crypto currencies. There are name clashes and standards non-compliance with several well-known "unofficial ISO currency codes" like:
Crypto
Unofficial ISO Code
ISO Conflict
Bitcoin
XBT
Conflicts with ISO 4217 because BT stands for Bhutan.
Ethereum
ETH
Conflicts with ISO 4217 because ET stands for Ethiopia.
Bitcoin Cash
XBC
Is identical to the ISO 4217 code for the European Unit of Account 9.
Solana
SOL
Is identical to the ISO 4217 code for the official currency of Peru.
ISO 24165 provides a new standard and the Digitial Token Identifier Foundation provides a global registry of digital tokens that conforms to ISO 24165 and also provides a downloadable JSON file of the data.
Therefore there is now a mechanism to support crypto (and other Digital tokens).
Thanks to @ayrat555 I was prompted to find a better solution for supporting crypto currencies. Currency, in ISO standard world, formally refers to currencies registered in ISO 4217 and this standard, while supporting private-use currency codes, does not easily support crypto currencies. There are name clashes and standards non-compliance with several well-known "unofficial ISO currency codes" like:
ISO 24165 provides a new standard and the Digitial Token Identifier Foundation provides a global registry of digital tokens that conforms to ISO 24165 and also provides a downloadable JSON file of the data.
Therefore there is now a mechanism to support crypto (and other Digital tokens).
Implementation will support:
String.CharsandCldr.Charsprotocols