# Proof of Reserve

For a comprehensive illustration of utilizing **Orakl Network's Proof of Reserve**, refer to the example repository of the [`data-feed-consumer`](https://github.com/Bisonai/data-feed-consumer). The on-chain implementation for Proof of Reserve mirrors that of the Aggregator and the Aggregator Proxy.

## What is Proof of Reserve?

The **Orakl Network's Proof of Reserve (PoR)** stands as a vital element in fostering trust and transparency within the financial ecosystem of Orakl Network. Playing a pivotal role, PoR is dedicated to the validation of reserve holdings for financial entities through a secure and auditable procedure. The GPC Proof of Reserve refers to a reserved quantity of non-fungible tokens (NFTs) issued specifically for Gold Pegged Coin.

### Proof of Reserve on Cypress

<table><thead><tr><th width="157">PoR</th><th>Aggregator</th><th>AggregatorProxy</th><th>Heartbeat (m)</th></tr></thead><tbody><tr><td>GPC (Gold Pegged Coin)</td><td><a href="https://kaiascan.io/account/0xb5e91e5CE0B8e6fc3029b4E9ce057675a2c96dd1">0xb5e91e5CE0B8e6fc3029b4E9ce057675a2c96dd1</a></td><td><a href="https://kaiascan.io/account/0x9FbA23B10692cB3fa6Fea09834855ACc597BD180">0x9FbA23B10692cB3fa6Fea09834855ACc597BD180</a></td><td>60</td></tr></tbody></table>

### Proof of Reserve on Baobab

**Disclaimer:** The data submitted to Baobab chain and is only for testing purposes. It does not always represent real-world data.

<table><thead><tr><th width="157">PoR</th><th>Aggregator</th><th>AggregatorProxy</th><th>Heartbeat (m)</th></tr></thead><tbody><tr><td>GPC (Gold Pegged Coin)</td><td><a href="https://kairos.kaiascan.io/account/0x58798D6Ca40480DF2FAd1b69939C3D29d91b60d3">0x58798D6Ca40480DF2FAd1b69939C3D29d91b60d3</a></td><td><a href="https://kairos.kaiascan.io/account/0x821179a6d4F62fa6979BF42bEb9eE16a1F14C4eD">0x821179a6d4F62fa6979BF42bEb9eE16a1F14C4eD</a></td><td>2</td></tr></tbody></table>

## How to read from Aggregator contract of PoR

The Proof of Reserve (PoR) in Orakl Network is realized through two key smart contracts: `Aggregator` and `AggregatorProxy`. These contracts form a pair, representing a specific data feed, and enable continuous access to the reserve holdings. The `Aggregator` receives regular updates from off-chain oracles, ensuring accurate and up-to-date reserve information. The `AggregatorProxy` serves as a consistent API for accessing the submitted data.

For a detailed understanding of PoR and its integration, refer to the [Orakl Network Data Feed](https://docs.orakl.network/developers-guide/data-feed) documentation. This documentation provides comprehensive insights into the architecture, reading procedures, and the relationship between `Aggregator` and `AggregatorProxy`, enhancing your grasp of PoR functionality.

To learn more about how to read reserves from `Aggregator` contract, visit [`Data Feed documentation`](https://github.com/Bisonai/orakl-docs/blob/master/en/developers-guide/data-feed/README.md#initialization).


---

# Agent Instructions: 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://docs.orakl.network/developers-guide/proof-of-reserve.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.