> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/tasks/safety-phrase.md).

# Safety phrase

The Tasks preview derives a four-word safety phrase from the onchain terms hash so parties can compare a signed scope.

{% hint style="info" %}
Tasks is in preview. This page describes the design; the preview accepts no payments or work.
{% endhint %}

The safety phrase is a short way for the client and worker to compare the same signed scope. You would compare it out of band before relying on the terms of a tranche.

## What it is

Each tranche has a public onchain `termsHash`. Tasks derives four lowercase words from that hash. The phrase is a comparison aid, not a replacement for checking the full hash or signatures.

The phrase is not stored as a separate escrow field. Anyone can reproduce it from the public `termsHash` shown on BaseScan.

## How it is derived

At a conceptual level, the derivation:

1. Checks that `termsHash` is `0x` followed by exactly 64 hexadecimal characters.
2. Reads bytes 0, 8, 16, and 24 from the hash.
3. Uses those four byte values as indexes into the fixed 256-word table.
4. Joins the four lowercase words with one space.

For example, the hash below produces `amber bamboo cabin coral`:

```
0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
```

## Compare it safely

Both parties should view the phrase beside the authoritative escrow state and say the words to each other out of band. If the phrases do not match, stop and compare the full `termsHash` and signatures. A mismatch means that you are not looking at the same signed scope.

A matching phrase is a quick check only. Different terms hashes can share the same four-word phrase, so use the full hash for exact verification.

Checked on 2026-10-02.


---

# 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.vapinetwork.ai/tasks/safety-phrase.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.