Bitcoin Cash address validator
Checked in this browser. The address is not sent to a server.
Public examples
Valid format and checksumBitcoin Cash · CashAddr · P2PKH
CashAddr checksum matches
Parts of this address
- 1Prefix
bitcoincash:“bitcoincash:” — part of the checksum even when left out.
- 2Type
qq = P2PKH, p = P2SH (z / r: token-aware forms).
- 3Payload
pm2qs…vcwv20-byte hash: 76a04053….
- 4Checksum
y22gdx6a8 characters, a 40-bit BCH code. The prefix is included in it even when it is not written.
Details
- Network
- Bitcoin Cash
- Type
- CashAddr · P2PKH
- Encoding
- CashAddr
- Length
- 54 characters · 20 bytes
- Checksum
- matches
Watch out
Nothing specific to this format. The general rule below still holds.
Same address in another form
Legacy form (1… / 3…)
1BpEi6DfDAUFd7GtittLSdBeYJvcoaVgguThe same address in the old format. Bitcoin uses the same legacy format — use it only where a service does not accept CashAddr.
What this does not proveA valid format only means the address is well-formed. It does not show who controls it or that it is the address the recipient gave. Compare the whole address with the source and send a small test amount first.
Format rules
- Starts with
- qpbitcoincash:
- Length
- 42 (+ prefix)
- Encoding
- CashAddr
- Checksum
- 40-bit BCH code
- Typo check
- Full: format and checksum
- Memo / tag
- Not used
What is checked
- CashAddr: the prefix
bitcoincash:(may be left out when written), a type character (q= P2PKH,p= P2SH), the hash and an 8-character checksum (40-bit BCH code). The prefix is part of the checksum. - Legacy BCH addresses look exactly like Bitcoin 1… and 3… addresses; the converter translates both ways.
z…andr…are token-aware forms (CashTokens).
Specification: CashAddr specification
Example above: a test vector printed in the CashAddr specification.
FAQ
Can I send BCH to a 1… address?
It is a valid legacy BCH form, but it looks identical to a Bitcoin address. Use the CashAddr form to make clear which coin is meant.