<p>I've found this project:
<a href="https://github.com/oskyk/cashaddress" rel="nofollow noreferrer">https://github.com/oskyk/cashaddress</a> , checked the accounts generated by it using <code>validateaddress</code> of my wallet, seems working fine!</p>

CC BY-SA 3.0
2018-01-24T13:46:24.290Z
2018-01-24T13:46:24.290Z
0x49D1
<p>I think GDAX (now Coinbase Pro) just remove the <code>bitcoincash:</code> prefix before displaying to users. I can confirm this from my Bitcoin Cash deposit address <code>q...</code>.</p>

<p>I remember reading that technically the prefix is part of the address, and depending on the implementation, some wallet may not be able to recognize it. While I'm sure Coinbase has done thorough research, I'd just make <code>usecashaddr=0</code> for the Bitcoin-ABC wallet</p>

CC BY-SA 4.0
2018-07-25T00:24:55.357Z
2018-07-25T00:24:55.357Z
Will Gu
<p>They should use those:</p>

<ul>
<li><p>cashaddr.org</p></li>
<li><p>cashaddr.bitcoincash.org</p></li>
<li><p>cashaddress.github.io</p></li>
</ul>

<p>Or, you can use the <a href="https://github.com/bitcoincashjs/bchaddrjs" rel="nofollow noreferrer">CashAddrJS</a> library to convert between them (<a href="https://github.com/bitcoincashjs/bchaddrjs/dist" rel="nofollow noreferrer">Here</a> are the browser JS).</p>

<p>Unfortunately there's no RPC command to convert addresses. Sorry!</p>

CC BY-SA 3.0
2018-01-25T06:27:36.910Z
All that external hosts/services are nice with one security concern: my project must be secure with NO data from "untrusted" external resources (they even are HTTP, so no even MITM attack shield). Who knows, may be that fellows will start to generate their own addresses and my users will happily send the money to that generated addresses... But JS library is another good option (I've used https://github.com/oskyk/cashaddress , rechecked the source: no external web requests, everything is done locally). Your answer answers my initial question, thanks!
0x49D1
CC BY-SA 3.0
2018-01-24T15:53:09.740Z
2018-01-24T16:01:50.017Z
2018-01-24T16:01:50.017Z
MCCCS
<p>Several days ago our bitcoin cash core wallet started to generate addresses using the new format: <code>bitcoincash:q......</code> . That's nice and differs from the bitcoin blockchain generated addresses, but some of our users have problems with the new address formats: not all the online exchangers supports the new format and mark it as invalid. 
Is there an ability to show the user his OLD format address alongside with new one? So that we need some kind of convertor between cashaddr/legacy address format standards (maybe that's silly, sorry), or do it via wallet RPC API?</p>

CC BY-SA 3.0
2018-01-24T15:44:16.817Z
"Several days ago our bitcoin cash core wallet..." Bitcoin ABC?
MCCCS
<bitcoin-cash><base58><bech32-address>
Cashaddr (bech32) to legacy address format convertor for Bitcoin Cash
0x49D1
# Cashaddr (bech32) to legacy address format convertor for Bitcoin Cash

(Asked by: username_0 on 2018-01-24)

Several days ago our bitcoin cash core wallet started to generate addresses using the new format: `bitcoincash:q......` . That's nice and differs from the bitcoin blockchain generated addresses, but some of our users have problems with the new address formats: not all the online exchangers supports the new format and mark it as invalid.
Is there an ability to show the user his OLD format address alongside with new one? So that we need some kind of convertor between cashaddr/legacy address format standards (maybe that's silly, sorry), or do it via wallet RPC API?

**Tags:** bitcoin-cash, base58, bech32-address

> **Comments:**
> **username_1**: "Several days ago our bitcoin cash core wallet..." Bitcoin ABC?  

---

## 3 answers

### Answer by username_1 on 2018-01-24. Score: 3 | Accepted answer

They should use those:

* cashaddr.org
* cashaddr.bitcoincash.org
* cashaddress.github.io

Or, you can use the [CashAddrJS](https://github.com/bitcoincashjs/bchaddrjs) library to convert between them ([Here](https://github.com/bitcoincashjs/bchaddrjs/dist) are the browser JS).

Unfortunately there's no RPC command to convert addresses. Sorry!

> **Comments:**
> **username_0**: All that external hosts/services are nice with one security concern: my project must be secure with NO data from "untrusted" external resources (they even are HTTP, so no even MITM attack shield). Who knows, may be that fellows username_2 start to generate their own addresses and my users username_2 happily send the money to that generated addresses... But JS library is another good option (I've used https://github.com/oskyk/cashaddress , rechecked the source: no external web requests, everything is done locally). Your answer answers my initial question, thanks!  

---

### Answer by username_0 on 2018-01-24. Score: 3

I've found this project:
<https://github.com/oskyk/cashaddress> , checked the accounts generated by it using `validateaddress` of my wallet, seems working fine!


---

### Answer by username_2 on 2018-07-25. Score: 0

I think GDAX (now Coinbase Pro) just remove the `bitcoincash:` prefix before displaying to users. I can confirm this from my Bitcoin Cash deposit address `q...`.

I remember reading that technically the prefix is part of the address, and depending on the implementation, some wallet may not be able to recognize it. While I'm sure Coinbase has done thorough research, I'd just make `usecashaddr=0` for the Bitcoin-ABC wallet


---

