> 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-updates.md).

# Journey updates

**Available now.**

**JourneyUpdates** is an admin-less singleton, deployed once on each chain, that anchors **content-addressed** progress updates for a launched token.

Updates are posted against a milestone, so only a token launched with a [commitment](/token-launch/journey-and-credibility.md) has them. The page shows an update only when it was posted by the token's creator and its stored text re-hashes to the anchored value.

## Properties

| Property  | Detail                                                        |
| --------- | ------------------------------------------------------------- |
| Address   | See [Contract addresses](/token-launch/contract-addresses.md) |
| Ownership | None                                                          |
| Role      | On-chain anchor for off-chain update payloads                 |

Updates do not rewrite `journeyHash` from launch. They add a verifiable trail of later documents (or blobs) whose hashes appear on-chain.

## Product surface

Token detail pages load update hashes from the indexer and resolve stored documents where available. If a document is missing off-chain, the hash on-chain still proves that a specific payload was committed.

## Not the weekly update

A project's **weekly update** (Studio+, written on the Overview and shown on the project page) is a team post stored by CanHav and published when the team says so. A journey update is signed by the launch wallet and anchored on chain; the two are kept apart on purpose.

## Related

* [Journey and credibility](/token-launch/journey-and-credibility.md)
* [The token page](/token-launch/token-page.md)

## Design launches

A token launched from a published design commits the design's snapshot hash instead of a journey. The milestones in the design's Post-launch section are the launch's milestones, verified the same way (the snapshot re-hashes to the on-chain value), so everything on this page that references the journey's milestones applies to them by index. A design published without milestones gives the launch nothing to schedule against.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.canhav.com/token-launch/journey-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.