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

# Validator network

# Validator Network

Validators are the economic backbone of the Notareum trust layer. They stake NOTA, attest to resource authenticity, earn fees and rewards, and face slashing if they misbehave. This page covers what validators do, how the network is structured, and the operational responsibilities that come with the role. For the detailed staking mechanics and tier parameters, see [Staking and Tiers](staking-and-tiers.md).

## What a validator does

A validator runs software that watches the Verification Engine for pending requests, evaluates each resource against off-chain evidence, and submits on-chain attestations. Validators also monitor disputes and may participate in governance via veNOTA. The role is operational: validators are not passive stakeholders, they are active participants whose job is to protect users from fraudulent resources.

## Validator tiers

Four tiers are automatically assigned based on staked NOTA.

```mermaid theme={"system"}
graph TD
    A[Stake NOTA] --> B{Amount}
    B -->|>= 1M NOTA| C[INSTITUTIONAL<br/>4.0x rewards<br/>75% slash<br/>unlimited/day]
    B -->|>= 250K NOTA| D[ENTERPRISE<br/>2.5x rewards<br/>50% slash<br/>2,500/day]
    B -->|>= 50K NOTA| E[PROFESSIONAL<br/>1.5x rewards<br/>35% slash<br/>500/day]
    B -->|>= 10K NOTA| F[BASIC<br/>1.0x rewards<br/>25% slash<br/>100/day]
    B -->|< 10K NOTA| G[Not a validator]
```

Each tier balances throughput, rewards, and risk. Higher tiers process more verifications per day and earn larger rewards per attestation, but they also face proportionally larger slashing if caught misbehaving. The design incentivizes professional operators to stake deeply while lowering the barrier for smaller validators to participate.

## Attestation flow

```mermaid theme={"system"}
sequenceDiagram
    participant E as VerificationEngine
    participant V as Validator
    participant S as Staking
    participant FM as FeeManager

    E-->>V: VerificationRequested event
    V->>V: review resource + off-chain evidence
    V->>E: submitAttestation(resourceId, approved)
    E->>S: recordVerification(validator)
    S->>S: check daily limit
    S->>S: increment dailyVerifications
    alt Quorum resolved (verified)
        E->>V: distribute fee share
    else Quorum resolved (rejected)
        E->>FM: forward 50% fee share
    end
```

Each active validator watches for `VerificationRequested` events, applies off-chain evidence review, and submits an attestation within a reasonable window. Attestations are independent votes: validators do not coordinate on-chain, and duplicate votes per request revert.

## Operational responsibilities

**Evidence review.** Validators must inspect the resource off-chain. For an address resource, this may mean checking the signer's public communications or cross-referencing a known identity. For a contract resource, it may mean checking the source code and deployment history. For an NFT provenance claim, it may mean checking the studio's social attestations.

**Uptime.** Daily verification limits bound the maximum throughput, but validators who miss too many attestations become economically unproductive. Operators should target high uptime.

**Key security.** Validator private keys control staked NOTA. Operators should use hardware security modules or multi-sig equivalents and follow industry best practices.

**Dispute readiness.** A validator may be reported for a false attestation. Operators should retain evidence for any resource they approve, enabling a defense during arbitration.

## Daily verification limits

Daily limits reset at UTC midnight and apply per validator. They prevent a single validator from dominating throughput and bound the blast radius of a compromised key.

| Tier          | Daily Limit |
| ------------- | ----------- |
| BASIC         | 100         |
| PROFESSIONAL  | 500         |
| ENTERPRISE    | 2,500       |
| INSTITUTIONAL | Unlimited   |

Hitting the daily limit causes further `submitAttestation` calls to revert with `DailyLimitExceeded` until the next UTC day.

## Rewards

Validator rewards come from two sources. First, direct fee distribution from the Verification Engine: when a verification resolves `VERIFIED`, the fee is split equally among approving validators. Second, periodic fee distribution from the Fee Manager, which aggregates rejected-verification fees, alias fees, and other protocol revenue.

Validators claim accumulated rewards via:

```solidity theme={"system"}
function claimRewards() external;
```

The staking contract tracks `rewardsAccrued` per validator. In v1.0, distribution from rejected verifications is equal-weighted. Future versions may weight by tier multiplier or by recent attestation volume.

## Slashing exposure

Misbehavior is punished via slashing. Slash rates scale with tier.

| Tier          | Slash Rate |
| ------------- | ---------- |
| BASIC         | 25%        |
| PROFESSIONAL  | 35%        |
| ENTERPRISE    | 50%        |
| INSTITUTIONAL | 75%        |

Slashed tokens are burned, removing them permanently from supply. Reporters who successfully dispute a validator receive their bond back plus 10% of the slashed amount. See [Slashing](slashing.md) and [Dispute Resolution](dispute-resolution.md) for details.

## Joining the network

1. Acquire at least 10,000 NOTA.
2. Call `stake(amount)` on `NotareumValidatorStaking`.
3. Your tier is automatically assigned.
4. Run validator software and start watching for events.
5. Submit attestations and earn rewards.

See [Becoming a Validator](../guides/becoming-a-validator.md) for a step-by-step tutorial.

## Leaving the network

Validators exit through a 14-day unbonding period.

1. Call `requestUnstake(amount)` to initiate.
2. Stake is immediately reduced and tier may downgrade.
3. Wait 14 days.
4. Call `completeUnstake()` to receive tokens.

The unbonding period prevents validators from staking, behaving maliciously, and withdrawing before disputes resolve.

## Related pages

* [Staking and Tiers](staking-and-tiers.md) for detailed mechanics
* [Slashing](slashing.md) for misbehavior penalties
* [Dispute Resolution](dispute-resolution.md) for challenge procedures
* [Fee Model](fee-model.md) for revenue distribution
* [Becoming a Validator guide](../guides/becoming-a-validator.md)