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

# The Astonic Reserve

### Understanding the Reserve Framework

The Astonic Reserve operates as a sophisticated, diversified portfolio of crypto-assets that underpins the entire protocol's stability mechanism. This comprehensive guide explores its structure, assets, and governance.

#### Core Components:

* Asset Portfolio Management
* Stability Maintenance
* Transparent Operations
* Community Governance

### Reserve Asset Framework

#### Asset Selection Criteria:

* 24/7 trading availability
* High market liquidity
* Open-source protocol basis
* Governance approval

#### Collateralization Structure:

* 110% stable asset backing
* Primary stable assets: USDC and DAI
* Diversification assets: BTC, ETH, ATOM, INJ, PLQ, OSMO
* Experimental: Nature-backed assets

> "The Astonic Reserve's robust collateralization model ensures stability while promoting innovation in digital asset management." - Digital Asset Strategy Expert

### Custodial Framework

#### Asset Security Measures:

1. Smart Contract Holdings

   * *Assets are securely stored in audited smart contracts, minimizing the risk of manipulation or unauthorized access.*

2. Native Planq Assets

   * *The system uses Planq’s native assets, benefiting from its decentralized and secure infrastructure.*

3. Automated Management

   * *Collateral and reserves are managed automatically by algorithms, ensuring efficiency and eliminating manual errors.*

4. Custodians

   * *Reputable third parties oversee reserve assets, adding an extra layer of security and accountability.*

5. FATF-Compliant Jurisdictions

   * *The framework adheres to global anti-money laundering standards, promoting legal and secure operations.*

6. Public Transparency Requirements

   * *Reserve details and operations are regularly audited and published, allowing users to verify the system’s integrity.*

7. Multi-Signature Control
   * *Transactions require approval from multiple trusted parties, ensuring no single entity can access reserves unilaterally.*

### Reserve Mandate & Governance

#### Primary Objectives:

* Protect stable asset holders
  * Ensuring all stable assets are fully collateralized and secure, safeguarding user funds.
* Maintain 100% backing
  * Reserves always match or exceed the value of issued stable assets, preventing any risk of under-collateralization.
* Enable portfolio diversification
  * Reserves include a mix of assets like Planq, USDC, and other tokens to enhance stability and reduce risks.
* Ensure transparent operations
  * All reserve-related activities are publicly logged, allowing community members to monitor governance and performance.

#### MultiSig Operations:

* Community-driven governance
  * Important decisions, such as asset rebalancing, are made through community voting or trusted representatives.
* Asset rebalancing authority
  * MultiSig holders can adjust the reserve portfolio to optimize stability and performance when market conditions change.
* Transparent transaction history
  * All MultiSig transactions are recorded on-chain, allowing anyone to verify the actions taken by custodians.
* Public verification system
  * Tools and dashboards are available for users to independently verify collateral levels and transaction records.


---

# 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://astonic.gitbook.io/astonic-docs/astonic-protocol-concepts/the-astonic-reserve.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.