-
I've been doing an atomic swap with someone sending the BCH from coinbase. The wallet was displaying to the BCH sender a BCH address of type CashAddr for the lockaddress. The sender which was using co…
-
if you set "use cashaddr format" in preferences, cashaddr format is used even in BTC wallet.
obviously legacy format should be used always for BTC wallet regardless of setting in prefs.
-
## Environment Details
* **OS:** MacOS
* **Node Version:** v14.18.1
* **Yarn Version:** v1.22.17
* **BitGoJS Version:** 14.1.2
* **BitGo Environment:** testnet
## Expected Behavior
I shou…
-
This is a work-in-progress draft specification of the REST API
Let's discuss.
To simplify interactions, all exchange will be done via POST (probably except for wait.. responses, for which I gues…
-
As seen in the cashaddr spec, cashaddr is supposed to have the bottom 3 bits of the version byte be an indicator of the size of the address. This means that valid version bytes can be like, 0x04 (ind…
-
Bitcoin cash introduced a CashAddrs in 2018. Its a new encoding (only userfacing) for their addresses to avoid mistakes (by introducing checksums and better distinguishability from BTC addresses) ([r…
-
Addresses in wallet files use legacy addresses.
I sometimes need to find which wallet an address belongs to and I use
```bash
#> grep -irl ~/.electron-cash/wallets
```
which necessitates manu…
-
Right now the receiving format goes as follows: `Bitcoincash:[Legacy]`, which is frankly quite an odd format among wallets: most wallets either generate `BITCOINCASH:[cashaddr]`, or just `[legacy]` wi…
-
Hello,
Are you going to implement new address format validation?
https://github.com/bitcoincashorg/spec/blob/master/cashaddr.md
-
Currently the spec uses version byte to indicate a testnet paycode, which is incongruous with how we do cashaddrs.
Shouldn't we just use `paycodetest:` prefix instead?