For exchanges and wallets

An exchange or wallet that lists, holds or displays an anchor's token, or keeps balances at a custodial app, can use the issuer's record in a listing review and a treasury check, and watch it for warning signs.

In a listing review

Before you list a token, confirm that its issuer publishes coverage and that the record says what you expect.

1. Find the registry contract id in a channel the issuer controls, such as its stellar.toml. See Find a record.
2. Read the latest record and confirm it is recent. See Check a record on Stellar.
3. Read the history of records to see how long the issuer has published, and how regularly. See For auditors for the command.
4. Read where the reserve figures come from, and decide if that source meets your bar. See Where reserve figures come from.

A record covers one registry. For a token the issuer has on several networks or with several custodians, ask which reserves the registry counts.

In a treasury check

If you hold an anchor's token on your own balance sheet or keep funds at a custodial app, read its record on a schedule. Each read is free and needs no permission from the institution.

This check reads the latest record, works out how old it is, and computes coverage in basis points (hundredths of a percent) with integer arithmetic:

import { Solva } from "@solva/sdk-ts";

const MAX_AGE_SECONDS = 26 * 60 * 60;

const solva = new Solva({
  network: "testnet",
  tenant: "22222222-2222-2222-2222-222222222222",
  endpoints: { contractId: "CDSQ35U2Y3VC44PJC6RRUJVCES2DLBWELDN32AIAEY4J35H4WBEKEUQW" },
});

const record = await solva.getOnChainLatestProof();
const reserves = BigInt(record.reservesTotal);
const owed = BigInt(record.liabilitiesTotal);
const ageSeconds = Math.floor(Date.now() / 1000) - record.timestamp;
const coverageBasisPoints = (reserves * 10000n) / owed;
const fresh = ageSeconds <= MAX_AGE_SECONDS;

console.log({ fresh, ageSeconds, coverageBasisPoints });

Against the Solstice Exchange example registry, a run printed:

{ fresh: true, ageSeconds: 9241, coverageBasisPoints: 17777n }

17777n basis points is 177.77 percent. The 26-hour limit is a daily cycle plus a two-hour grace period. Set your own limit to match the cadence you expect from the institution.

What to watch

The registry limits how fast reserves can rise. Each record's reserves can be at most 10 percent above the record before, so reserves moved in shortly before a cycle cannot lift the figure by more than that. There is no limit on how fast reserves can fall.

Show coverage to your users

A wallet can show the status beside a token balance. Show short and stale as plainly as covered, each with the time of the record it comes from. Point holders at the inclusion check so they can confirm their own balance. See Check a balance was counted.

Automated checks with is_covered

is_covered Coming soon is a read on the registry that returns the status directly, covered, short or stale, with the ledger the asset was checked at. It takes the issuer and the asset, so a contract or a back-end job gets one answer per asset without working out freshness itself. A swap, a listing gate or an alert can call it before acting.

Without is_covered, read the latest record and apply your own freshness rule, as in the treasury check above. Solva's oracle for AI agents has two tools, get_solvency and get_anomalies. With answers from a live orchestrator Coming soon, it reads records and flags a reserve drop of 10 percent or more, a rise in what is owed of 15 percent or more, or a gap of more than 26 hours between cycles.

Next: For lenders and risk teams.