> ## Documentation Index
> Fetch the complete documentation index at: https://docs.presschain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Validators

> Understand the Validator role as a bonded protocol participant rather than a generic infrastructure label.

# Validators

Validator is protocol role ID `4` in the current V3 role table. It carries the highest listed testnet minimum bond, `250 PRESS`, and role weight `10`.

In PressChain application design, the word validator can refer to more than one thing. Be precise about whether you mean a **protocol role participant** or **node validation infrastructure**. This page focuses on the protocol role.

## Role responsibilities

The action policy includes Validators in workflows such as `review.submit`, `bounty.claim` and `bounty.approve`, subject to the additional permissions of each action.

Validator status is therefore relevant to application authorization, not merely a badge in a profile.

## Bonded participation

The active bond requirement creates an economic state that can be checked before a user participates in privileged verification work.

A client can provide a useful preflight summary:

```text theme={null}
Role: Validator
Bond: Active
Minimum testnet bond: 250 PRESS
Action: Submit review
Economic class: micro
```

The actual execution path still performs authoritative checks.

## Weight is contextual

Role weight `10` should only be used where the applicable protocol process defines role weight as an input. It is not a universal reputation score.

Do not take the number and display “Validator is 10x more trustworthy than Reader.” That is not what a protocol weight means.

## Validator and bounty work

A Validator can be eligible for bounty claiming under the current action policy. Bounty approval can also include Validator, but approval additionally depends on being the creator, designated reviewer or protocol authority according to the active policy.

This is another example of why role alone is not sufficient authorization.

## Audit-friendly interfaces

When a Validator action changes state, preserve the account, transaction hash, block and action semantics in your projection. If the product shows a finalized result later, readers should be able to trace which protocol action produced it.

## Mainnet caution

The testnet bond number and any current validator reward behavior should not be presented as final mainnet economics. Mainnet requires an approved validator reward policy and independent economic review.

Build interfaces around semantic requirements first and load mainnet amounts from the approved authority when it exists.