> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/cryptos/bitcoin-cash.md).

# Bitcoin Cash

Official Website: [bitcoincash.org](https://bitcoincash.org/)

Bitcoin Cash `(BCH)` emerged from a fork of Bitcoin in August 2017, primarily to address scalability concerns by increasing the block size limit — initially from 1 MB to 8 MB, and since raised to 32 MB — allowing more transactions to be processed per block.

This alteration was intended to facilitate faster and cheaper transactions, making it more practical for everyday use. Like Bitcoin, BCH operates on a decentralized network using blockchain technology, but it promotes itself as "Bitcoin with bigger blocks" to differentiate from its predecessor by focusing on broader transaction throughput.

## Addresses

We automatically generate new Bitcoin Cash addresses after each use for better privacy. Previous addresses continue to work.

Bitcoin Cash uses the CashAddr address format. Your receive address begins with `q`, followed by a series of alphanumeric characters. CashAddr addresses are sometimes shown with a `bitcoincash:` prefix; with or without that prefix, the address is the same.

![Bitcoin Cash receive screen in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/bitcoin-cash_01_receive.png)

Bitcoin Cash wallets are derived from the BIP44 account root `m/44'/145'/0'`. The full paths are `m/44'/145'/0'/0/x` for receive addresses and `m/44'/145'/0'/1/x` for change addresses. This is **not** the Electrum `m/0'` scheme that Cake Wallet uses for Electrum-seed Bitcoin and Litecoin wallets.

## Seed format

Cake Wallet creates Bitcoin Cash wallets with a 12-word BIP39 seed by default. Under `Advanced Settings` on the wallet creation screen you can choose a **24-word** BIP39 seed instead, and you can add a seed passphrase.

{% hint style="info" %}
Your BIP39 seed can be shared with your other Cake Wallet currencies as part of a [wallet group](https://docs.cakewallet.com/features/managing-your-wallet/wallet-groups).
{% endhint %}

## Fees

Bitcoin Cash network fees are paid in BCH. Cake Wallet offers three fee levels:

* **Slow**: Cheaper but may take longer to confirm.
* **Medium**: Recommended for most transactions. Balanced speed and cost. This is the default.
* **Fast**: Expensive but confirms quickly.

There is no `Custom` fee option for Bitcoin Cash — that is Bitcoin-only. Bitcoin Cash fees are typically very low.

![Choosing a Bitcoin Cash transaction fee in Cake Wallet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/bitcoin-cash_04_fees.png)

## Coin control

Bitcoin Cash supports [coin control](https://docs.cakewallet.com/features/advanced/coin-control), which lets you choose exactly which coins (unspent outputs) you spend in a transaction. This gives you finer control over your privacy and your fees.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cakewallet.com/cryptos/bitcoin-cash.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.