> For the complete documentation index, see [llms.txt](https://pegasys.gitbook.io/pegasys-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pegasys.gitbook.io/pegasys-docs/technical-details/pegasys-network.md).

# PegaSys Network

PegaSys’s principle vision is to allow Bitcoin holders to earn native yield on their capital in a passive, non-custodial manner. We aim to achieve this by aggregating liquidity from depositors, provisioning it to the Lightning Network in numerous ways, and distributing the accrued fees back to our depositors. By using idle Bitcoin to enable cheaper (less “hops”) and higher value (more channel capacity) transactions on Lightning, in addition to providing native yield to depositors, PegaSys is mutually beneficial to Bitcoin and Lightning users.

<figure><img src="/files/nO1GXPAq9STITwatoLvr" alt=""><figcaption><p>Network Architecture</p></figcaption></figure>

### Deposits

The only thing a prospective depositor needs to do to start earning yield is to create a Deposit UTXO using a spending script that can be used in one of two ways:

* **Spending by PegaSys**: Once included in a block, the UTXO can be spent by the PegaSys network using an aggregated Schnorr signature. This mechanism provides flexibility for the PegaSys network to manage funds as needed.
* **Time-locked Spending by the Depositor**: If 144 blocks (approximately 1 day) have passed since the UTXO was created, the depositor can spend the UTXO using their key. This spending path acts as an escape hatch for depositors if PegaSys hasn’t allocated their funds within a day.

Once the deposit UTXO has been added to a block and finalized (received 6 confirmations), the PegaSys network will add the UTXO to its “free liquidity pool” and make it provisionable to the lightning network for earning yield.


---

# 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://pegasys.gitbook.io/pegasys-docs/technical-details/pegasys-network.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.