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

# What Is Piron Finance

Welcome to Piron Finance — a protocol that brings real‑world fixed‑income access on‑chain through transparent pool mechanics, role‑gated operations, and verifiable accounting.

Piron is built for investors who want **real‑world yield with protocol‑level clarity**. The system is designed to be auditable, deterministic, and understandable — every pool has defined rules for deposits, investments, and withdrawals, and all movement of funds is governed by smart contracts.

> Piron is a protocol layer, not a bank or custodian. Returns are not guaranteed, and all investments carry risk.

***

### Why Piron

Traditional access to fixed‑income can be opaque, geographically restricted, and slow to settle. Piron exists to solve that gap with:

* **On‑chain accountability**: Funds are governed by smart contracts and escrow logic.
* **Clear lifecycle rules**: Every pool follows explicit state transitions and redemption rules.
* **Cross‑border access**: Investors can participate without the usual jurisdictional barriers.
* **Portfolio flexibility**: Multiple pool types allow different liquidity and duration preferences.
* **Operational control**: Admin and SPV roles are explicitly gated with protocol‑level permissions.

***

### What We Offer

Piron provides three distinct pool models that map to different investor needs:

| Pool Type        | Best For                           | Liquidity              | Return Profile            |
| ---------------- | ---------------------------------- | ---------------------- | ------------------------- |
| **Single‑Asset** | Fixed‑term investing               | Withdraw at maturity   | Coupon + maturity payout  |
| **Stable Yield** | Flexible yield exposure            | Immediate or queued    | NAV‑based yield           |
| **Locked**       | Time‑locked, higher predictability | Maturity or early exit | Tiered APY with penalties |

Each pool is backed by real‑world investment activity and governed by smart contracts that enforce deposits, allocations, and payouts.

***

### At a Glance (Protocol Flow)

```mermaid
flowchart LR
  U["Investor"] --> P["Pool Contract"]
  P --> E["Escrow"]
  E -->|Allocation| S["SPV"]
  S -->|Invests off-chain| R["Real-World Assets"]
  R -->|Cashflows| S
  S -->|Returns| E
  E --> U

  F["Fee Manager"] -.-> E
  Y["Yield Reserve"] -.-> E
```

### Who Piron Is For

Piron is built for users who want yield with clarity:

* **Retail investors** seeking predictable, asset‑backed yield.
* **Professional investors** who want transparent pool mechanics and auditable flows.
* **Partners and issuers** looking to offer structured yield products in a standardized format.
* **Developers and integrators** who need protocol‑level primitives for fixed‑income access.

***

### Vision

Piron’s long‑term goal is to become the **default protocol layer for global fixed‑income access** — where investors can participate in real‑world yield with the same transparency and programmability they expect from on‑chain systems.

This is a system designed to make **real‑world value legible on‑chain**.


---

# 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://piron.gitbook.io/piron-finance/readme.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.