> For the complete documentation index, see [llms.txt](https://oracledocs.magpie.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oracledocs.magpie.gg/the-oracle/verifiability.md).

# Verifiability & permanence

The oracle's history cannot be quietly rewritten — including by us.

## The daily anchor

Every day (23:40 UTC) the published prices are frozen into a snapshot and:

1. **Merkle root on Solana mainnet.** Each price becomes a canonical leaf (`keccak256`, Ethereum-compatible encoding); the tree's 32-byte root is posted via the SPL Memo program: `MagpieOracle|<day>|<root>`. Cost: \~0.000005 SOL — the anchor is designed to outlive us.
2. **Encrypted snapshot on Arweave.** The full frozen snapshot (every leaf) is stored permanently, AES-256-GCM encrypted. Permanence without giving the dataset away; ADR-0001 forbids cleartext publication.
3. **Immutability guard.** Once a day's root is posted on-chain, the oracle refuses to recompute that day — a recomputed snapshot would diverge from the anchored root, and the code makes that impossible.

## Verify a price yourself

```
GET /oracle/v1/batch/2026-07-12
→ merkle_root, n_leaves, arweave_tx,
  attestations: [{chain:"solana", network:"mainnet", status:"posted", tx_ref}]

GET /oracle/v1/proof?day=2026-07-12&card_id=123&printing=Normal&lang=en&graded=false
→ { leaf, proof[], merkle_root, verified: true, attestations[] }
```

* The proof is **OpenZeppelin-compatible** (sorted-pair keccak256): it verifies in any standard Merkle library, off-chain or on-chain (EVM included).
* The attestation tx is public: check the memo on any Solana explorer.
* Both endpoints are **keyless** — verification must never be paywalled.

## Why keccak256 on Solana?

The leaf encoding is chain-agnostic by design: the same root can be attested on multiple chains (an EVM attestor is a drop-in), and EVM contracts can verify inclusion natively. Solana is the first anchor, not the last.

## What this buys an integrator

You can display a value today and later *prove* it was the value published at loan origination / at listing time / at dispute time. For financial use cases (SlabX-class), that turns "trust the API" into "verify the API".


---

# 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://oracledocs.magpie.gg/the-oracle/verifiability.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.