# Midas Attestation Engine

The **Midas Attestation Engine** is the trust layer powering Midas onchain investment products.

It transforms structured information into verifiable onchain checkpoints. These checkpoints can relate to financial exposure, technical state, operational processes, or any other information that requires public verification.

The engine was built in close collaboration with Chainlink, LlamaRisk, vLayer, and Canary.

### A General-Purpose Attestation Layer

Anything can be attested.

The Attestation Engine is not limited to NAV or proof of reserves. It can formalize and verify:

* Asset backing
* Net Asset Value calculations
* Collateralization levels
* Smart contract parameters
* Governance decisions
* Operational workflows
* Risk committee approvals
* Offchain portfolio statements
* Legal confirmations
* Service provider confirmations
* Monitoring alerts
* Any structured claim requiring verifiable anchoring

If information matters to investors, it can be transformed into a claim and bundled into an attestation.

### Why It Matters

Midas aims to provide the highest possible level of real-time reporting across its products (release anticipated in April 2026). Real-time reporting delivers continuous visibility. However, live systems can occasionally experience temporary inconsistencies, latency, or data synchronization issues.

The Midas Attestation Engine addresses these limitations by providing **high-quality, independently verified checkpoints**.

Each attestation represents a formal and structured event that:

* Is anchored onchain
* Is independently verified onchain
* Can be programmatically consumed by investors, integrators, curators, and risk frameworks

Attestations are designed to serve as authoritative checkpoints. They do not replace real-time transparency dashboard and KPIs. Instead, they complement them.

In practice:

* Real-time reporting provides continuous information.
* Attestations provide verified reference states.

Together, they establish a transparency model that combines visibility with independently verifiable trust anchors.

### Core Concepts

#### Claim

A **claim** is a structured assertion about a specific fact.

A claim may originate from:

* A service provider
* A fund administrator
* A risk manager
* A blockchain endpoint
* An API
* A notarized email
* An internal monitoring system

Claims can, when required, be stored directly in the Midas Attestation Engine smart contracts.

#### Attestation

An **attestation** is a structured bundle of one or more claims.

It:

* Defines a reporting scope
* Links related claims
* Includes timestamps and metadata
* Follows predefined validation logic
* Is emitted onchain
* Is stored on IPFS
* Is permanently recorded in the Attestation Engine smart contracts

When possible, Midas leverages Chainlink CRE to publish attestations in a standardized and decentralized manner.

An attestation becomes a machine-readable checkpoint that downstream systems can consume.

### Verification Layer

After publication, attestations are independently reviewed by verifiers.

A onchain verification confirms that:

* The expected operational workflow was followed
* The claims originate from legitimate sources
* The validation process was executed independently

Verifications are recorded onchain (and tied with their associated attestation), and deliver the credibility layer of the system.

### **Built With Best-in-Class Partners**

We did not build this alone. The Attestation Engine is the result of close collaboration with [Chainlink](https://chain.link/), [LlamaRisk](https://www.llamarisk.com/), [vlayer](https://www.vlayer.xyz/), and [Canary](https://www.canaryprotocol.com/).

LlamaRisk co-developed the SAVE verification framework and the core attestation architecture, and also serves as an independent onchain verifier. Chainlink Runtime Environment (CRE) provides the decentralized attestation building and publication infrastructure that ensures attestations are broadcast through a predefined, transparent onchain workflow. vlayer powers the cryptographic notarization of source documents (like email disclosures) preserving their content and timestamp so they can be publicly inspected. And Canary provides independent verification capacity, reinforcing the credibility layer of every attestation cycle.

### Smart contract and Public Codebase

The Attestation Engine is available at [0x2D6e9F608807436DE5D9603B00Abe3FEd1Bc809d](https://etherscan.io/address/0x2d6e9f608807436de5d9603b00abe3fed1bc809d) on Ethereum.

The workflow and verification scripts are made public at Midas's [GitHub repo](https://github.com/midas-apps).

### Feed Types

#### POR Feed

The Midas Proof of Reserve attestation cryptographically anchors the risk manager’s NAV disclosure. The NAV statement is notarized using vLayer’s technology, which converts the original email into a verifiable onchain input while preserving its integrity and timestamp.

The notarized email is stored on IPFS and is publicly accessible for review. This allows anyone to inspect the exact content that entered the attestation workflow.

The workflow used to construct and publish the attestation is executed through Chainlink CRE. This ensures that the publication process follows a predefined and transparent onchain logic.

Independent verifiers, including LlamaRisk and Canary, review the process and confirm onchain that the publication workflow has been respected. Their verification confirms that the data submitted by the risk manager was not altered by Midas during the attestation process.

Before the NAV is used to update token pricing, Midas performs internal consistency checks and reconciliation procedures. These controls ensure that the disclosed NAV is coherent within the broader allocation and valuation framework.

**Attestation parameters per token**

| Token  | Allocation snapshot     | Reserve NAV Source                                                                                 | NAV consistency checks             | Workflow                    | Verification                   |
| ------ | ----------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------- | --------------------------- | ------------------------------ |
| mHYPER | Planned via 1Token APIs | <p>• disclosed by Hyperithm<br>• notarized by vLayer<br>• onchain anchored<br>• stored on IPFS</p> | • Internal reconciliation by Midas | • Executed on Chainlink CRE | <p>• Llamarisk<br>• Canary</p> |


---

# 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://midas-docs.gitbook.io/midas-docs/how-does-it-work/midas-attestation-engine.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.