Stage 2 Attest

Who this is for: issuers who have issued a token (see 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; the distinction between a price feed and a backing attestation specifically is covered at Price feeds vs. reserve attestation.

What Lumia provides today

Oracle integrations for market-data feeds are documented under Build: Read data feeds with API3, Read price feeds with Supra, and Supra. Those suit the price-feed side of attestation.

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.