> For the complete documentation index, see [llms.txt](https://source-code-systems.gitbook.io/pulsarprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://source-code-systems.gitbook.io/pulsarprotocol/readme.md).

# Introduction

![Pulsar Protocol](/files/gYytMdCoAyunLKGDQgfW)

## The treasury-powered reserve protocol for Defi

Pulsar Protocol is built to acquire, manage, and grow a diversified on-chain treasury. It combines the recognizable minting, staking, rebasing, protocol-owned liquidity, and **(3,3)** mechanics pioneered by early Olympus-style protocols with a sharper long-term goal: put protocol-owned capital to productive work and use governed treasury earnings to strengthen the system and reward aligned participation.

PULSAR is the liquid protocol token. When PULSAR is staked, the holder receives **QUASAR**, the staked representation of PULSAR. A future wrapped form of QUASAR may provide a non-rebasing, integration-friendly token for DeFi use.

> **Important:** Pulsar is under development. Token behavior, parameters, accepted mint assets, distribution methods, governance, audits, and contract addresses are not final. Nothing in these docs is a promise of profit or financial advice.

### Start exploring

* [What is Pulsar?](/pulsarprotocol/overview/what-is-pulsar.md)
* [How Pulsar works](/pulsarprotocol/protocol-mechanics/how-pulsar-works.md)
* [PULSAR, QUASAR, and wrapped QUASAR](/pulsarprotocol/protocol-mechanics/tokens.md)
* [Staking and rebasing](/pulsarprotocol/protocol-mechanics/staking-and-rebasing.md)
* [Minting PULSAR](/pulsarprotocol/protocol-mechanics/minting.md)
* [Treasury earnings and distributions](/pulsarprotocol/protocol-mechanics/treasury-earnings.md)


---

# 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://source-code-systems.gitbook.io/pulsarprotocol/readme.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.