> For the complete documentation index, see [llms.txt](https://cifer.gitbook.io/cifer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/on-chain-commitments.md).

# On-chain commitments

The commitments namespace supports contracts that store compact metadata while emitting encrypted bytes through event logs.

```mermaid
flowchart TB
    P[Plaintext] --> E[Encrypt]
    E --> C[Cifer envelope and ciphertext]
    C --> T[Storage transaction]
    T --> S[Hashes and metadata in contract state]
    T --> L[Encrypted bytes in event logs]
    S --> R[Locate block and verify hashes]
    L --> R
    R --> D[Authorized decryption]
```

## Why use commitments

* Prove that an encrypted record existed in a specific form.
* Keep full encrypted bytes out of expensive contract storage.
* Retrieve records from known transaction or block ranges.
* Validate hashes before requesting decryption.

The SDK can build storage intents, parse metadata and logs, and verify integrity. Your application supplies the target contract ABI/function definition and executes the transaction.

{% hint style="info" %}
A commitment proves integrity and ordering properties. It does not make plaintext public, prove that the plaintext was true, or hide every form of metadata.
{% endhint %}


---

# 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://cifer.gitbook.io/cifer-docs/documentation/cifer-sdk/web3-integration/on-chain-commitments.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.