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

# footprints

A footprint is the smallest thing the field will remember for you.

## what a footprint contains

| field            | meaning                                                                                                                |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **title**        | a single line. what you did.                                                                                           |
| **body**         | optional. the details. never required.                                                                                 |
| **content hash** | SHA-256 of the canonical footprint contents. computed in-browser before you submit.                                    |
| **timestamp**    | when the field received it. immutable.                                                                                 |
| **trail link**   | optional. which step of which trail this belongs to.                                                                   |
| **anchor**       | optional. a Solana transaction signature proving the hash was written to the Memo Program.                             |
| **visibility**   | public or private. public footprints appear in [/explore](https://lashae.us/explore); private ones only on your field. |

The content itself lives in the database, off-chain. The **hash** is what may travel to Solana. This means: even if the field one day forgets you, the chain will remember *that a footprint of exactly this shape existed on this date*.

## how a footprint is created

1. **write it.** one line minimum. no maximum, but the field prefers small.
2. **hash it.** the browser computes SHA-256 over the canonical string. you never send raw content to the chain.
3. **(optionally) anchor it.** the wallet adapter opens. you sign one memo transaction on Solana devnet (or mainnet, later). status moves through: `pending → sent → confirmed`.
4. **save it.** the footprint is written to the field only after the anchor is confirmed (or you have chosen to skip anchoring entirely).

## the rules of a footprint

* a footprint cannot be deleted. it can be **retracted** — the body is redacted, but the hash and timestamp remain. the field never lies about what once was.
* a footprint cannot be edited. you may leave a **follow-up footprint** that references it.
* a footprint's hash is deterministic. re-hashing the same canonical content on any device yields the same fingerprint. this is what makes the anchor meaningful.

## the small footprint

The field prefers small footprints. A page written is a footprint. A run finished is a footprint. A hard email sent is a footprint. A file finally deleted is a footprint.

Grand milestones are welcome, but they are not what the field is optimised for. **The field is optimised for the ordinary tuesday** — the day you almost did not walk, but did.


---

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