# RWA Lens — Presenter walkthrough

A take-away script for the guided demo at
[rwalensonsolana.vercel.app/demo](https://rwalensonsolana.vercel.app/demo).
It follows the four chapters on that page — Identity, Balance, Controls,
Evidence — then continues into the app workspace, yield screener, device
watchlist and mobile distribution.
Budget nine to eleven minutes, plus three for questions.

**Read the token. Understand the asset.**

## Watch the narrated tour

The [demo page](https://rwalensonsolana.vercel.app/demo) opens with the narrated
product walkthrough and selectable English captions. Use it before the live
walkthrough, or share the
[MP4](https://rwalensonsolana.vercel.app/demo/rwa-lens-walkthrough.mp4).
The matching [caption track](https://rwalensonsolana.vercel.app/demo/rwa-lens-walkthrough.vtt)
and [transcript](https://rwalensonsolana.vercel.app/demo/rwa-lens-transcript.txt)
are available separately. The recording shows real app interactions and public
mainnet reads; its market figures describe the recording time.

## Before you present

1. Open `/demo` and let the inspector finish its first read. It loads the
   Ondo USDY mint `A1KLoBrKBde8Ty9qtNQUtq3C2ortoC3u7twggz7sEto6` on Solana
   mainnet and shows a live observation with its provider and context slot.
2. Have one public wallet address ready to paste for the balance chapter. Any
   address the audience names works; an address you read is public data.
3. Say once, at the start, what inspection does: it reads public chain state,
   requires no wallet connection and never moves assets. The separate optional
   deploy flow requires an operator to enable it and a user to review and sign
   in their own wallet. It is off on the public deployment.
4. Keep a second tab on the issuer source
   ([docs.ondo.finance/addresses](https://docs.ondo.finance/addresses)) so
   attribution and decoding stay visibly separate.

Before presenting, `node scripts/verify-live.mjs` performs one explicit public
mainnet read and writes its receipt, so you know the provider path is warm.

## Navigate the app workspace

Choose **Open app** from the landing page, or open
[`/rwa`](https://rwalensonsolana.vercel.app/rwa). The workspace navigation links
**Inspector**, **Yield** and **Watchlist**. The inspector has five sections:
**Overview**, **Balances**, **Controls**, **Liquidity** and **Evidence**.
Switching sections keeps the mint, wallet input and current observation in
place. Use the arrow keys, Home or End while a section tab has focus, or use
browser Back and Forward to revisit sections.

The four chapters on `/demo` use an inline inspector. In the app workspace,
select the corresponding section tab before presenting each result below.
Select Liquidity to continue the market discussion after Evidence.

## 01 · Identity — start at the source

**Show:** the Token identity card. Mint address, token program badge, decimals,
raw supply, mint authority and freeze authority.

**Say:** "The issuer's documentation says this address is USDY. The RPC read
says this account is a mint owned by the legacy SPL Token program with six
decimals. Those are two different statements from two different sources, and
the page keeps them apart."

**Look for:** the program badge reads *SPL Token · legacy program*. That is the
observed program, so no Token-2022 extension logic applies to this mint. Open
*Program & metadata* to show the owning program address and the declared
metadata URI: a URI is issuer-supplied content, and the page states whether the
deployment's host allowlist permits fetching it before anything is requested.

## 02 · Balance — make every unit count

**Show:** paste the public wallet address into *Wallet address (optional)* and
press Inspect. Then open *Public token accounts*.

**Say:** "Raw base units are exact integers. The displayed amount is a
conversion. This page shows both, plus the account list the total came from."

**Look for:**

- *Raw base units* carries an EXACT marker. A display multiplier never changes it.
- *Standard decimal* is raw units ÷ 10^decimals.
- The account table lists each validated token account, its raw amount, its
  state and any extensions found on it.
- An empty validated account list means zero observed holdings for that owner.
  A read that did not complete says so instead, and no zero is invented.

## 03 · Controls — read the rules

**Show:** the Extension inventory and Transfer readiness cards.

**Say:** "Authorities and extensions are the controls that decide what can
happen to a holding. Readiness explains observed state; it is not permission and
not legal advice."

**Look for:** for USDY the inventory states that no Token-2022 extensions were
found on this mint, which is the honest result for a legacy SPL mint — a good
moment to explain that the inventory reports what the account actually carries.
In Transfer readiness, point at the separation between a known block, such as an
inspected frozen token account, and an unresolved check. A configured freeze
authority can freeze accounts; its presence alone does not mean a holder is
currently frozen. Each reason carries its own evidence line.

If the audience wants to see extension handling, inspect any Token-2022 mint
they name. Scaled UI Amount, Interest Bearing, Transfer Hook, Default Account
State and Permanent Delegate each get a plain-language impact line, their
authorities and their decoded fields.

## 04 · Evidence — take it with you

**Show:** open *Every observation has a source*, then Export JSON and Export CSV.

**Say:** "Every number you just saw has a method, a context slot and a time
behind it. The export is that record, as a file you keep."

**Look for:**

- The evidence table lists each read: method, status, context slot and detail.
- Commitment, fetched-at time, observed Clock timestamp, time source and decoder
  version are all stated.
- Separate reads keep their own context slots. The page says plainly that this
  is not an atomic snapshot.
- The JSON receipt contains the inspection request, the export time, the full
  observation and a SHA-256 content hash of the observation payload. The hash
  identifies the payload; it is not an issuer endorsement.
- The CSV carries the same values as flat rows for a reconciliation workflow.

Also open *Issuer registry attribution*. It names the issuer, the asset class,
the exact retrieval timestamp and the freshness of that record, and links to the
issuer source. The same retrieval timestamp appears in the JSON receipt, so a
reviewer can check the page against the file.

## Continue · Follow the market

**Show:** issuer attribution and the reserve badge, then choose **Yield** in
the workspace navigation or open `/yield`.

**Say:** "The mint tells us what is on chain. The reserve link takes us to the
issuer's reports. The yield view shows where supported tokenized assets trade
on Meteora. These sources answer different questions."

**Look for:**

- USDY links to the issuer's reserve-report page. RWA Lens links the reports;
  it does not audit or verify their contents.
- Filter pools by issuer, pair and minimum liquidity. Copy the resulting URL
  to show that the view is shareable.
- Review TVL, volume, fees and the issuer-reported market session. Historical
  fee APY does not promise a future return.
- Open a row's mint in the inspector. Its address is passed through the URL,
  so the next observation is for the token you selected.
- Exported token receipts stay separate from third-party pool figures.

The optional **Deploy USDC** action is off on the public deployment. On an
operator-enabled deployment, it prepares one Jupiter swap plus Meteora DLMM
deposit, runs a mainnet preflight check, and shows amounts, range and costs
before the user's wallet signs and sends. The server never holds signing keys.
A funded send with a real wallet remains required before public activation.
Do not describe an unsigned preview as a completed deposit.

## Continue · Save a token for the next look

1. Open a mainnet token in **Inspector** and choose **Save to watchlist**. The
   control changes to **Saved on this device**.
2. Choose **Watchlist** in the workspace navigation. The saved card keeps the
   full mint address, available name and symbol, and save date.
3. Reload the page to show that the entry stays in this browser. Choose
   **Open inspector** on the card to request a fresh observation of that mint.
4. On the Watchlist page, paste an address into **Add a Solana mint**, then
   choose **Save mint**. Saving an existing address does not duplicate it.
   **Remove** deletes that mint from this device's list.

The list holds up to 20 public mint addresses. It stores no inspected owner
field, balances or receipts, and needs no wallet connection. Changes appear in
other tabs on the same site. Clearing browser data clears the list; the page
explains when device storage is unavailable. Cloud report storage remains off
on the public deployment.

## Continue · Bring the lens to mobile

The site offers an installable PWA. A connection is required for fresh chain
reads; offline navigation shows a connection notice. The repository also ships
an Android Web Shell for Android and Solana Seeker, with Mobile Wallet Adapter
support on enabled wallet surfaces. Release signing, real-device validation and
dApp Store publishing are pending release steps. Present the PWA in the browser
without claiming a shipped Android app or completed phone validation.

## Questions you should expect

**Does this prove the token is backed by a real asset?** No, and the page says
so wherever attribution appears. It proves what the mint account contains and
who can act on it. Backing, eligibility and redemption rights come from the
issuer and from diligence outside this tool.

**Can it move my tokens?** Inspection, market discovery and local export are
read-only. The separate optional deploy flow, off on the public deployment,
asks your own wallet to sign and send one transaction after your review. The
server does not sign, hold keys or take custody.

**Where does the data come from?** One configured Solana RPC provider, named in
the evidence drawer with the context slot of every read. The browser cannot
choose the provider. Market discovery separately uses the xStocks catalog and
Meteora market data; reserve links come from recorded issuer attribution.

**What if a read fails?** The failure stays visible, the previous observation
keeps its original timestamp, and the message names what resolves it — a
different address, a pause, or the provider. No value is replaced with a zero.

**Is the displayed amount exact?** The standard decimal conversion is exact. A
Scaled UI Amount display uses the official Token-2022 helper and is labelled as
a rounded display conversion, next to the exact raw units.

## Where to go next

- `/technical` — architecture, accounting boundaries, the API contract and the
  reliability and security model.
- `/pitch` — the presentation kit.
- `/yield` — tokenized-asset liquidity discovery and exact-mint inspector links.
- `/rwa` — the inspector workspace, with five sections for a direct second look.
- `/watchlist` — public mint addresses saved on this device.