Supported Address Formats

Suggest Edits

What address formats do you support?

Some digital assets use multiple address formats following changes to network protocols such as the ETH Merge or BTC SegWit upgrade. Zero Hash offers support for multiple address formats in both the Production (PROD) and Certification (CERT) environments. Please note the particular address formats supported in the Zero Hash PROD and CERT environments that are described below:

Bitcoin (BTC)

Zero Hash supports all address formats for BTC including the following:

  • Testnet Addresses: The Zero Hash CERT environment supports BTC addresses that begin with characters “m” or “n” (6F in hexadecimal).
  • Legacy Addresses: The Zero Hash PROD environment supports legacy BTC addresses that begin with a "1".
  • Bech32/Native SegWit Addresses: The Zero Hash PROD environment supports Bech32 (Native SegWit) address format for BTC including addresses that begin with “bc1” as well as p2sh SegWit addresses that start with characters “3”.

Please note that Zero Hash does not support BTC addresses that are all uppercase (e.g. 3J98T1WPEZ73CNMQVIECRNYIWRNQRHWNLY). Zero Hash only supports legacy and SegWit BTC addresses that are checksummed (e.g. 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy).

Bitcoin Cash (BCH)

  • Cash Addresses: The Zero Hash PROD environment supports the CashAddr BCH address format. This address format is designed to help distinguish between BCH and BTC more clearly.

Ethereum (ETH) and ERC20

  • Testnet Addresses: As of the Ethereum Merge, the Zero Hash CERT environment only supports Goerli test network addresses. Addresses that are associated with Ropsten or other ETH test networks are not supported and cannot be used in CERT.

Litecoin (LTC)

  • Testnet Addresses: The Zero Hash CERT environment supports LTC addresses that begin with characters “m” or “n” (6F in hexadecimal).
  • Legacy Addresses: The Zero Hash PROD environment supports legacy addresses that begin with an "L" for LTC.
  • Bech32/Native SegWit Addresses : The Zero Hash PROD environment supports Bech32 (Native SegWit) address format for LTC including addresses that being with “ltc1” as well as SegWit (P2SH) addresses that start with characters “3” or “M”.

Updated 28 days ago