> For the complete documentation index, see [llms.txt](https://docs.sating.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sating.io/sating.io-basics/the-main-sating-page/sating-search-types/alpha-sats.md).

# Alpha Sats

Alpha sats are the first sat in each bitcoin.  These sats always end in at least 8 zeros.

By removing the last 8 zeros you have the bitcoin number.  For example, 1947612000000000 is the first sat in bitcoin number 19476120.\
\
Here is some math to calculate number of Alpha sats compared to Uncommons.

* 1st 210,000 blocks, 50 BTC per block = 210,000 Uncommons and 10,500,000 Alpha (All Uncommons are also Alpha)&#x20;
* 2nd 210,000 blocks, 25 BTC per block = 210,000 Uncommons and 5,250,000 Alpha (All Uncommons are also Alpha)&#x20;
* 3rd 210,000 blocks, 12.5 BTC per block = 210,000 Uncommons and 2,625,000 Alpha (105,000 Uncommons are also Alpha)&#x20;
* 4th 210,000 blocks, 6.25 BTC per block = 210,000 Uncommons and 1,312,500 Alpha (52,500 Uncommons are also Alpha)

We are near the end of that 4th phase with another halving expected next year. So when the 6.25 BTC phase ends there will be...

840,000 Uncommons \
577,600 Uncommons that are also Alpha \
19,687,500 Alpha/Bitcoin

Already we can see how Alpha sats can make Uncommons more valuable.

In the next 210,000 Uncommon blocks after these, only 26,250 will also be alpha so this combination will continue to become more rare as time goes on. Also, the number of Alpha continues to drop. There will only be 656,250 new Bitcoin in the 4-ish years it takes to create these 210,000 blocks.


---

# 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:

```
GET https://docs.sating.io/sating.io-basics/the-main-sating-page/sating-search-types/alpha-sats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
