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

# anchoring to solana

Anchoring is the act of writing a footprint's hash to the Solana blockchain — specifically, to the **Memo Program** — so that the world may later verify: *yes, this exact footprint existed at this exact moment.*

Anchoring is **optional**. A footprint saved off-chain is still a footprint. The field remembers either way.

## what actually goes on-chain

Almost nothing.

* **not** the title of your footprint.
* **not** the body.
* **not** your handle.
* **not** your wallet-to-content mapping.

Only the **SHA-256 hash** of the canonical footprint contents, written as a single memo instruction in a single transaction, signed by your connected wallet.

The chain sees:

```
<64-hex-char hash>
```

The chain does not see what the hash represents. Only you (and anyone you show your footprint to) can prove the hash matches the content.

## the flow

1. You compose a footprint and click **anchor**.
2. Your wallet adapter (Phantom, Solflare, Backpack, or anything Wallet-Standard-compatible) prompts you to sign.
3. The transaction moves through visible states: `pending → sent → confirmed`.
4. On `confirmed`, the field saves the footprint with the transaction signature attached.
5. The footprint's receipt now carries a **verify on-chain** badge.

If the transaction fails, no footprint is saved. The field refuses partial truth.

## which chain, which network

* **network**: Solana **devnet** by default. Mainnet is unlocked when the field is ready and you are, too.
* **program**: the [SPL Memo Program](https://spl.solana.com/memo).
* **cluster RPC**: configurable. defaults are Helius-friendly.
* **wallet**: any Wallet-Standard-compatible wallet. no adapter is hardcoded.

## why Solana, and not another chain

Because the field needed:

* **fees near zero.** a footprint should not cost a coffee.
* **finality in seconds.** the walker should not wait.
* **a memo program.** so nothing else has to be deployed for a hash to exist forever.

Other chains can do parts of this. Solana does all of it, and does it quietly.

## the philosophical part

The chain is not the field. The chain is the field's **witness**. A witness that does not speak, does not judge, does not clap — only remembers.

> *saved off-chain. still remembered.*
>
> *anchored to solana. the field has a witness.*


---

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