> For the complete documentation index, see [llms.txt](https://skysync.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://skysync.gitbook.io/docs/from-input-to-chain-the-skysync-mechanism/validation-layer.md).

# Validation Layer

In SkySync, once a submission is made, it enters the validation layer. This layer is structured to distribute review responsibilities across multiple participants, rather than relying on a centralized moderator or authority node.

Validation follows a randomized, multi-party check process, designed to ensure no single actor has unilateral control over whether a data point is accepted or rejected.

#### Key Elements:

* Sampling & Distribution

Each new submission is routed into a pool where it becomes available for review. A randomized subset of validators is assigned to review each entry. The selection process is non-deterministic and changes per session.

* Validator Roles

Validators receive raw submissions and are required to assess their internal consistency (e.g. image vs. text), relevance (e.g. does the content reflect observable environmental states), and completeness.

* Review Options

Each validator can choose from three actions:

&#x20;       Approve – the entry appears consistent, readable, and relevant.

&#x20;       Reject – the entry is clearly flawed, non-informative, or invalid.

&#x20;       Flag – the entry shows anomalies or subjective uncertainty, and may require a broader review round.

* Minimum Confirmation Threshold

A submission is only forwarded for anchoring if it reaches a predefined threshold of approvals, which may vary based on submission type or geographic sensitivity.

* No Cross-Communication

Validators operate independently and do not communicate during the validation process. This prevents coordinated decisions and reinforces judgment based on content alone.

* Re-review Rounds

If a submission receives both approvals and rejections, it may be routed to a secondary validation layer for additional votes or escalation review.

<br>
