> For the complete documentation index, see [llms.txt](https://docs.canhav.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.canhav.com/token-launch/journey-and-credibility.md).

# Journey and credibility

**Available now.**

A **journey** is the off-chain plan for a token: milestones, narrative, and updates over time. At launch, CanHav commits hashes on-chain so anyone can verify that a published document matches what was launched.

## Two commitments

| Hash              | Commits to                             |
| ----------------- | -------------------------------------- |
| `descriptionHash` | Short description from the launch form |
| `journeyHash`     | Full journey document stored off-chain |

They are independent. Changing one document does not rewrite the other hash. Verification is: hash the published bytes and compare to the event.

## Why it matters

Launch pages often make claims that never appear on-chain. Binding a journey hash at factory time means:

* The launch event is the source of truth for “what was promised at t0”
* Later [journey updates](/token-launch/journey-updates.md) can add content-addressed progress without rewriting the original commitment
* Explorers and indexers can surface the hashes even if hosting moves

## Format notes

Journey document format may evolve. Smoke-test launches have used placeholders. Treat the **hash in the event** as the contract with the chain; treat the hosted file as the human-readable payload that must match.

## Related

* [Create a token](/token-launch/create-a-token.md)
* [Journey updates](/token-launch/journey-updates.md)
* [Milestone escrow](/token-launch/milestone-escrow.md)


---

# 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://docs.canhav.com/token-launch/journey-and-credibility.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.