> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/blink-payment-methods/on-chain/what-are-the-different-types-of-bitcoin-on-chain-addresses.md).

# What are the different types of Bitcoin on-chain addresses?

Bitcoin on-chain addresses come in different formats, each with its own prefix. Here are the most common formats and their respective prefixes:

* Legacy addresses: start with "1"
* SegWit addresses: start with "3"
* Native SegWit addresses: start with "bc1" (Most common bitcoin on-chain address)

It's important to note that while different address formats may look different, they are all valid Bitcoin addresses and can be used to send and receive Bitcoin. However, some wallets and services may only support certain address formats, so it's important to verify which formats are supported before sending or receiving Bitcoin.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://faq.blink.sv/blink-payment-methods/on-chain/what-are-the-different-types-of-bitcoin-on-chain-addresses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.