Don't take our word for it.

1. A token really backs what the site says

1. Open the registry on the explorer, tab Read contract.
2. Call getLaunch with the token address from its page here.
3. Compare assetId and feeMode (0 reserve, 1 creator, 2 holders) with the token page. They were written in the launch transaction and cannot be edited afterwards.

2. The fees go to the treasury

1. On the factory, call getLaunchedToken with the token address.
2. creatorFeeRecipient must equal the treasury above and creatorTaxBps must be 200. Nothing else about the token is special.

3. The reserve exists

1. Open the treasury address, tab Tokens. Every asset the reserve page lists should be there in at least the units shown.
2. Every purchase row on the reserve page links to the transaction that moved the units in. Every claim row links to the escrow claim.
3. What the issuer holds behind those tokens is the issuer's claim, backed by their attestation. That part is their risk, not ours to prove.

4. The numbers add up

Raised is the sum of claims, each with its transaction. NAV is units held times the issuer's last published price. Nothing on the site is a stored total; every figure is a sum over rows you can see on the reserve page.

What we cannot prove on chain

Purchases of the asset are made by the treasury through the issuer's venue and booked afterwards, so a claim can sit as “unbought” for a while. Yield is booked when the issuer pays it. Both are visible on the reserve page as they happen, with transactions.