> For the complete documentation index, see [llms.txt](https://docs.onto.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onto.app/basics/assets-management/bitcoin-legacy-and-segwit-addresses.md).

# Bitcoin - Legacy and Segwit Addresses

There are four most common types of Bitcoin address formats:

1. **P2PKH** addresses that begin with the number **"1"**\
   **Example:** *1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2*<br>
2. **P2SH** addresses starting with the number **"3"**\
   **Example:** *3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy*<br>
3. **Bech32** addresses, also known as "bc1 addresses" starting with **"bc1"**\
   **Example:** *bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq* \
   Bech32 is supported by most software and hardware wallets, but only a few exchange platforms. Bech32 is more efficient with block space.
4. **Taproot (P2TR)** addresses, also called Taproot or Bech32m, are the latest and most advanced format in Bitcoin. These addresses are case-insensitive and begin with bc1p. They improve scalability, flexibility, privacy, and security, but they are opt-in and not yet commonly supported, much like SegWit. \
   **Example:** *bc1p5d7rjq7g6r4jdyhzks9smlaqtedr4dekq08ge8ztwac72sfr9rusxg3297*&#x20;

<br>


---

# 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.onto.app/basics/assets-management/bitcoin-legacy-and-segwit-addresses.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.