# Challenge & Security Mechanism

Trust is enforced through code and economic incentives. When a Guardian Node detects a discrepancy—like orders executed out of sequence or missing from an epoch—it initiates a challenge. But random accusations aren't enough; our system demands rigorous proof.

<figure><img src="/files/G84zhILMKx1Z6puImrCe" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/v0g0SgZVfpPJOiLfEnNe" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/rwN8OSaTOl5v4cDO6z5j" alt=""><figcaption></figcaption></figure>

This multi-stage validation creates a powerful security mechanism. False challenges result in slashed stakes and temporary exclusion from the network. Valid challenges unlock the Sequencer's locked fees—14 days worth of revenue—distributing them to the challenging nodes. This creates a Mexican standoff: Yamata is incentivized to keep the Sequencer honest to retain revenue, while nodes compete to catch any misbehavior.

The reputation system adds another layer of security:

* Nodes start at 100 points&#x20;
* Successful validations increase score&#x20;
* Failed challenges and downtime reduce it&#x20;
* Higher reputation means better rewards and lower slashing risk


---

# Agent Instructions: 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:

```
GET https://paper.yamata.io/challenge-and-security-mechanism.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
