> For the complete documentation index, see [llms.txt](https://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/guides/holders.md).

# For holders and wallets

You hold, or are about to accept, a Stellar-issued asset. Plimsoll tells you whether it is backed, according to whom, and how recently.

## Read an asset in 30 seconds

1. Open the [app](https://plimsoll-app-gths-amber.vercel.app/) and find the asset.
2. Read the three things on its card:
   * **The ratio.** 100% or more means reported reserves cover everything in circulation.
   * **The status.** *Fully backed*, *Under-backed*, *Report stale* (older than 31 days) or *No data*.
   * **The tier.** *Auditor-signed* is strongest. *Issuer-signed* means the issuer vouched for itself. *Transcribed* means a volunteer copied a published figure.
3. Open the asset page to see every report, its date, its signer and its document.

## Check it yourself

On the asset page:

* **Check on-chain now** reads the contract directly from your browser. It does not use Plimsoll's servers.
* **Verify hash** downloads the reserve document and compares its SHA-256 with the hash stored on-chain. A mismatch means the document changed after it was posted.
* **How supply was counted** shows the six buckets. When the indexer is connected, the page also checks that they hash to the on-chain value.

## What a reading does not tell you

A reading is only as good as its signer. An issuer can post a false figure at the Issuer-signed tier, and the contract will record it. Plimsoll makes that visible: you always see who signed.

## For wallet builders

Show the ratio and tier next to the balance. One SDK call:

```ts
const cov = await plimsoll.coverage(sac, Tier.Transcribed);
```

See [TypeScript SDK](/plimsoll-protocol-docs/developers/sdk.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://plimsoll-protocol.gitbook.io/plimsoll-protocol-docs/guides/holders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.