> 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/protocol/trust-model.md).

# Trust model

Plimsoll does not remove trust. It makes each trusted party visible and checkable.

| Party          | What you trust them for                            | How you can check                                                |
| -------------- | -------------------------------------------------- | ---------------------------------------------------------------- |
| Registry admin | Choosing auditors, transcribers and supply posters | Every change is a `reporter_set` / `reporter_revoked` event      |
| Supply poster  | Counting supply correctly                          | The breakdown hash is on-chain; recompute it from Horizon        |
| Issuer         | Its own reserve figure                             | The document hash is on-chain; the tier says it is self-reported |
| Auditor        | An independent figure                              | Registered identity; document hash on-chain                      |
| Transcriber    | Copying a published figure correctly               | Document hash on-chain; lowest tier                              |

## What the contracts guarantee

* Only the issuer's account can post at the Issuer-signed tier.
* Only registered addresses can post at the Auditor-signed and Transcribed tiers.
* Only genuine Stellar Asset Contracts can be listed, with their real code and issuer.
* Supply snapshots and reports per tier only move forward in time.
* `coverage` and `is_covered` apply the same rule for everyone.

## What they do not guarantee

* That a reserve figure is true. A signer can lie; the tier tells you who did.
* That supply is counted correctly. The poster can be wrong; the hash lets anyone prove it.
* Availability. If nobody posts, readings age and `is_covered` starts returning `false`, which is the safe direction.

## Known gaps in v0.1

These are tracked as issues:

* No on-chain dispute of a supply snapshot.
* Admin transfer is one step, not propose-and-accept.
* Soroban-native (SEP-41) tokens are not supported.
* The contracts are unaudited.


---

# 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/protocol/trust-model.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.