> For the complete documentation index, see [llms.txt](https://docs.pstake.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pstake.finance/satdrop/satdrop-details/how-to-get-psats.md).

# How to get pSats?

pSats is the name for points in the context of SatDrop. Let's understand a few important things about pSats first.

* For total transparency, pSats are just balances in a database (not onchain tokens) associated with a particular wallet address.
* pSats are also non-transferable.
* pSats can be converted into $PSTAKE tokens at the end of each season

There are three key ways of receiving pSats:

1. Complete onchain and offchain tasks
2. Unlock badges for exclusive rewards
3. Refer a fren or more

### pSats Calculation Formula

$$
pSats Earned = pSats (task) \* Multiplier
$$

Continue reading ahead to find out about what Multiplier is and how it works.


---

# 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.pstake.finance/satdrop/satdrop-details/how-to-get-psats.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.