> For the complete documentation index, see [llms.txt](https://vayyl.gitbook.io/vayyl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vayyl.gitbook.io/vayyl-docs/product/conditional-settlement.md).

# Conditional Settlement

Conditional settlement lets a user commit an instruction without publishing the full instruction before its execution condition is met.

## Hidden orders

The planned hidden-order flow separates commitment from execution:

1. The wallet commits order parameters and ownership to the hidden-order registry.
2. A keeper observes public market inputs, not the hidden witness.
3. When a condition can be satisfied, the owner or authorized prover creates a trigger proof.
4. The contract verifies the proof, consumes the order nullifier, and routes settlement into private output notes.

This can protect limit levels and strategy intent from simple pre-execution copying. It does not hide public oracle data, contract invocation timing, or any public asset movement required by the adapter.

## Required components

| Component             | Responsibility                                                |
| --------------------- | ------------------------------------------------------------- |
| Hidden-order registry | Store order commitments and reject repeated execution         |
| Trigger circuit       | Prove committed conditions against an accepted oracle input   |
| Oracle adapter        | Normalize and authenticate the public price input             |
| Keeper network        | Detect eligible orders and submit execution attempts          |
| Pool adapter          | Consume private funding and create private settlement outputs |

The order and settlement must be atomic: either the proof-bound state transition and value movement both succeed, or neither does.


---

# 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://vayyl.gitbook.io/vayyl-docs/product/conditional-settlement.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.