> For the complete documentation index, see [llms.txt](https://docs.lumia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumia.org/tokenize/the-asset-lifecycle/stage-2-attest.md).

# Stage 2 Attest

**Who this is for:** issuers who have issued a token (see [Stage 1: Issue](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/tokenize/the-asset-lifecycle/stage-1-issue)) and need holders and downstream contracts to trust that the asset backing it actually exists. This is concept content.

### What attesting means

A token is only as trustworthy as the claim it makes about the real-world asset behind it. Attest is the stage where that claim (a valuation, a proof of custody, a reserve balance, an audit result) gets verified by a party other than the issuer and represented on-chain, so holders don't have to re-verify the paperwork themselves every time. The general models for doing this (reserve attestation, price-feed attestation, custodial attestation) are covered in depth at [Attestation models](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/ecosystem/lumia/chain-security/oracles-and-attestation/attestation-models); the distinction between a price feed and a backing attestation specifically is covered at [Price feeds vs. reserve attestation](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/ecosystem/lumia/chain-security/oracles-and-attestation/price-feeds-vs-reserve-attestation).

### What Lumia provides today

{% hint style="warning" %}
Oracle integrations for market-data feeds are documented under Build: [Read data feeds with API3](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/oracles/read-data-feeds-with-api3), [Read price feeds with Supra](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/oracles/read-price-feeds-with-supra), and [Supra](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/oracles/read-price-feeds-with-supra). Those suit the price-feed side of attestation.
{% endhint %}

### What the issuer brings

* The attestation source itself: an auditor, a custodian, or an oracle network willing to publish the claim on-chain.
* A cadence for re-attestation: a single point-in-time attestation says nothing about backing a month later unless it's refreshed on a predictable schedule.
* A decision about which attestation model fits the asset (reserve, price-feed, or custodial): see [Attestation models](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/ecosystem/lumia/chain-security/oracles-and-attestation/attestation-models).