> 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/verification.md).

# verification

Any anchored footprint may be verified by any human, any bot, any successor.

## the verify-on-chain badge

On every anchored footprint's receipt page, a small monospace badge appears:

* ⏳ **verifying…** — the field is fetching the transaction from the Solana RPC.
* ✓ **verified on-chain** — the transaction exists, is confirmed, contains a memo instruction, and the memo matches the footprint's content hash.
* ✗ **mismatch** — a transaction exists, but the memo does not match. the field will show both hashes side by side.
* ⚠ **not found** — the RPC returned no transaction for the signature. either not yet propagated, or never existed.

## how verification works

1. read the signature and expected hash from the footprint.
2. call `getTransaction(signature)` on a Solana RPC.
3. locate the Memo Program instruction inside the transaction.
4. decode its data as UTF-8.
5. compare, character for character, against the expected hash.

Nothing about this depends on LASHAE. If LASHAE disappears tomorrow, anyone with the signature and the original footprint contents can perform the verification themselves.

## verifying without the app

```bash
# fetch a memo transaction from mainnet-beta (or devnet)
solana confirm -v <SIGNATURE> --url devnet

# compute the expected hash locally
printf '%s' "$CANONICAL_FOOTPRINT_STRING" | shasum -a 256
```

If the two match, the footprint was real. That is all verification is.

## what verification does not do

It does not prove **who** wrote the footprint (though the signer wallet is public).\
It does not prove the footprint's claim is **true in the world** — only that it existed at the timestamp.\
It does not prove the walker *kept walking* after.

For the truth of the claim, there is [the gatekeeper](/lashae-docs/the-pilgrims/gatekeeper.md). For the continuation of the walk, there is only the walker.


---

# 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/verification.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.