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

# attestations

An attestation is a **pilgrim's judgment of a footprint** — recorded, hashed, and anchored on-chain so it cannot be quietly rewritten.

Elsewhere in software, an AI reply is ephemeral. Somebody screenshots it. Somebody else says the model never said that. There is no receipt. LASHAE fixes this by treating every pilgrim reply as a first-class object with its own on-chain memo.

## the shape of an attestation

| field                 | meaning                                                                 |
| --------------------- | ----------------------------------------------------------------------- |
| **footprint\_id**     | the footprint being judged.                                             |
| **pilgrim\_mode**     | which pilgrim spoke — usually `gatekeeper` or `witness`.                |
| **model**             | the exact model identifier used (e.g. `google/gemini-3-flash-preview`). |
| **prompt\_hash**      | SHA-256 of the exact system prompt fed to the model.                    |
| **reply\_text**       | what the pilgrim said. stored verbatim.                                 |
| **reply\_hash**       | SHA-256 of the reply.                                                   |
| **verdict**           | one of `credible`, `incomplete`, `unclear`.                             |
| **attestation\_hash** | \`SHA-256(LASHAE\_ATTEST                                                |
| **anchor\_signature** | optional. Solana signature memoing the attestation hash.                |

## the flow

1. the footprint's owner **summons a pilgrim** (Gatekeeper for credibility, Witness for acknowledgment).
2. the server calls the model, records everything above, and returns the canonical hash.
3. the walker **anchors the hash** on Solana with a `LASHAE_ATTEST` memo.
4. the footprint's public receipt now shows the reply, the verdict, and a **verify on-chain** badge.

Anyone — including bots, journalists, and successors — can recompute the canonical hash from the stored fields and check the memo. If it matches, the AI's judgment cannot have been altered.

## why this matters

* **models change.** what a model said last month, on that prompt, is normally impossible to reproduce. attestations preserve it exactly.
* **screenshots lie.** an anchored attestation cannot be photoshopped without breaking the hash.
* **judgment is a public artifact.** if the Gatekeeper says a footprint is credible, that judgment is visible, dated, and immutable — the pilgrim cannot quietly change its mind.

## verifying an attestation

```bash
# 1. fetch the memo
solana confirm -v <SIGNATURE> --url devnet

# 2. recompute the canonical hash
printf 'LASHAE_ATTEST\x1f%s\x1f%s\x1f%s\x1f%s\x1f%s\x1f%s' \
  "$FOOTPRINT_HASH" "$MODEL" "$PROMPT_HASH" "$REPLY_HASH" "$VERDICT" "$ISSUED_AT" \
  | shasum -a 256
```

Matches ⇒ the attestation is intact.

## what an attestation does not do

* it does not turn the pilgrim into an oracle.
* it does not make the verdict "true in the world."
* it does not bless the footprint — blessings are a separate primitive, and they belong to walkers, not AIs.

An attestation is a **cold, small record** that an AI, given exactly these inputs, produced exactly this output at exactly this moment. That is a rare and useful thing.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lashae.gitbook.io/lashae-docs/the-protocol/attestations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.