Validator Guide¶
This guide covers everything you need to know about becoming a validator on the Herald Network's Reputation-Linked Micropayment (RLM) system.
Overview¶
Validators are essential to the Herald Network's quality assurance system. As a validator, you:
- Stake USDC to participate in the network
- Vote on the quality of tool outputs
- Earn a share of the 10% validator pool from every tool payment
- Build reputation through accurate voting
Why Validate?¶
| Benefit | Description |
|---|---|
| Passive income | Earn from every tool invocation |
| Stake multipliers | Lock USDC for higher rewards |
| Network governance | Shape tool quality standards |
| Early access | Preview new tools before public release |
Economics Overview¶
Revenue Distribution¶
When a tool is invoked with payment:
| Recipient | Share | Example ($1 tool) |
|---|---|---|
| Tool Creator | 70% | $0.70 |
| F3L1X Treasury | 20% | $0.20 |
| Validator Pool | 10% | $0.10 |
How Validator Pool is Split¶
The 10% validator pool is distributed based on:
1. Stake amount - More stake = larger share
2. Lock multiplier - Longer locks = higher weight
3. Reputation score - Better reputation = priority selection
4. Consensus participation - Active validators earn more
Staking Requirements¶
Minimum Stake¶
| Tier | Amount | Description |
|---|---|---|
| Minimum | 10 USDC | Entry-level validation |
| Standard | 100 USDC | Regular validation tasks |
| Professional | 1,000 USDC | Priority task assignment |
| Institutional | 10,000+ USDC | Maximum task volume |
Lock Period Multipliers¶
Lock your stake for higher earning potential:
| Lock Period | Multiplier | Effective Stake |
|---|---|---|
| No lock | 1.0x | Base stake |
| 1 month | 1.5x | 1.5x rewards |
| 3 months | 2.0x | 2x rewards |
| 6 months | 3.0x | 3x rewards |
| 1 year | 5.0x | 5x rewards |
Example: 100 USDC with 1-year lock = 500 USDC effective stake weight.
Withdrawal Rules¶
| Lock Status | Withdrawal Time |
|---|---|
| No lock | Instant |
| Active lock | After lock expires |
| Slashed | 24-hour cooldown |
Reputation System¶
Your reputation determines task priority and trust level.
Reputation Scale¶
| Score | Level | Benefits |
|---|---|---|
| 800-1000 | Elite | First priority, premium tasks |
| 600-799 | Trusted | High priority, bonus multiplier |
| 400-599 | Standard | Normal task assignment |
| 200-399 | Provisional | Reduced tasks, monitoring |
| 0-199 | Suspended | No tasks until recovery |
How Reputation Changes¶
| Action | Impact | Notes |
|---|---|---|
| Correct vote (majority) | +10 | Consensus alignment |
| Incorrect vote | -25 | Against consensus |
| Fast response | +2 | Under 5 seconds |
| Abstention | -5 | Failure to vote |
| Consecutive correct | +5 bonus | 10+ streak |
Starting Score: All new validators begin at 500 (Standard).
Recovery Strategies¶
If your reputation drops:
- Vote conservatively - Align with consensus
- Focus on clear cases - Avoid ambiguous validations
- Stay active - Consistent participation helps
- Study patterns - Learn what consensus considers valid
Validation Process¶
How Validation Works¶
1. Tool receives invocation request
↓
2. Herald selects 3 validators (weighted by stake × reputation)
↓
3. Validators independently assess output quality
↓
4. 2/3 majority determines consensus
↓
5. Rewards distributed, reputation updated
Validation Criteria¶
When assessing tool output, consider:
| Criterion | Weight | Description |
|---|---|---|
| Accuracy | 40% | Is the output factually correct? |
| Completeness | 25% | Does it fully answer the request? |
| Format | 15% | Is the response properly structured? |
| Safety | 20% | Does it avoid harmful content? |
Voting Options¶
| Vote | When to Use |
|---|---|
| VALID | Output meets quality standards |
| INVALID | Output fails quality criteria |
| ABSTAIN | Insufficient expertise to judge |
Note: Abstention costs -5 reputation but avoids potential -25 for incorrect vote.
Slashing Mechanism¶
Slashing protects network quality by penalizing bad behavior.
Slashing Conditions¶
| Violation | Penalty | Recovery |
|---|---|---|
| Incorrect vote | 5% stake | Immediate |
| Coordinated voting | 25% stake | 7-day suspension |
| Sybil attack | 100% stake | Permanent ban |
| Extended inactivity | 1% stake/week | Warning first |
Slashing Example¶
Initial State:
- Stake: 100 USDC
- Lock: 3 months (2x multiplier)
- Effective weight: 200
After Incorrect Vote:
- Slashed: 5 USDC (5% of stake)
- New stake: 95 USDC
- Effective weight: 190
- Cooldown: 24 hours (no new tasks)
Appeal Process¶
If you believe you were incorrectly slashed:
- Submit appeal via Herald dashboard
- Provide reasoning and evidence
- Community review (48 hours)
- Decision finalized by governance
Getting Started¶
Step 1: Prerequisites¶
- Base L2 wallet - MetaMask, Coinbase Wallet, or similar
- USDC on Base - Bridge from Ethereum or buy directly
- Herald account - Register at f3l1x.tech
Step 2: Connect Wallet¶
# Register your validator wallet
curl -X POST http://127.0.0.1:8014/api/validators/register \
-H "Authorization: Bearer $HERALD_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"wallet_address": "0x742d35Cc6634C0532925a3b844Bc8e7595f42263",
"network": "eip155:8453"
}'
Step 3: Stake USDC¶
# Initiate staking (returns transaction to sign)
curl -X POST http://127.0.0.1:8014/api/validators/stake \
-H "Authorization: Bearer $HERALD_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"amount": "100",
"lock_period": "3mo"
}'
Response:
{
"transaction": {
"to": "0x...",
"data": "0x...",
"value": "0"
},
"stake_details": {
"amount": "100",
"lock_period": "3mo",
"multiplier": 2.0,
"effective_weight": 200,
"unlock_date": "2026-05-12T00:00:00Z"
}
}
Sign the transaction with your wallet to complete staking.
Step 4: Start Validating¶
Once staked, you'll automatically receive validation tasks based on your weight. Monitor your dashboard for incoming tasks.
Validation Interface¶
Receiving Tasks¶
Tasks arrive via WebSocket:
const ws = new WebSocket('wss://herald.f3l1x.tech/ws/validator/');
ws.onmessage = (event) => {
const task = JSON.parse(event.data);
if (task.type === 'VALIDATION_REQUEST') {
console.log('New task:', task.invocation_id);
console.log('Tool:', task.tool_name);
console.log('Input:', task.input_data);
console.log('Output:', task.output_data);
console.log('Deadline:', task.vote_deadline);
}
};
Submitting Votes¶
curl -X POST http://127.0.0.1:8014/api/validators/vote \
-H "Authorization: Bearer $HERALD_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"invocation_id": "550e8400-e29b-41d4-a716-446655440000",
"vote": "VALID",
"confidence": 0.95,
"notes": "Output accurately answers the query"
}'
Vote Deadline¶
- Standard tasks: 60 seconds
- Priority tasks: 30 seconds
- Extended tasks: 5 minutes
Missing the deadline counts as abstention (-5 reputation).
Monitoring Performance¶
View Your Stats¶
curl http://127.0.0.1:8014/api/validators/me/stats \
-H "Authorization: Bearer $HERALD_TOKEN"
Response:
{
"validator_id": "val_abc123",
"reputation": 685,
"stake": {
"amount": "100",
"locked_until": "2026-05-12T00:00:00Z",
"multiplier": 2.0,
"effective_weight": 200
},
"performance": {
"total_votes": 542,
"correct_votes": 498,
"accuracy": 0.919,
"avg_response_time_ms": 4200,
"current_streak": 15
},
"earnings": {
"total": "12.45",
"this_month": "3.21",
"pending": "0.15"
}
}
View Earnings History¶
curl http://127.0.0.1:8014/api/validators/me/earnings \
-H "Authorization: Bearer $HERALD_TOKEN"
Earnings Calculator¶
Estimated Monthly Earnings¶
| Stake | Lock | Multiplier | Network Volume | Est. Monthly |
|---|---|---|---|---|
| 10 USDC | None | 1x | $10,000 | ~$0.50 |
| 100 USDC | 3mo | 2x | $10,000 | ~$10.00 |
| 1,000 USDC | 1yr | 5x | $10,000 | ~$250.00 |
| 10,000 USDC | 1yr | 5x | $100,000 | ~$2,500.00 |
Formula:
Monthly Earnings = (Your Weight / Total Network Weight) × Monthly Validator Pool
Note: Actual earnings depend on network volume and your reputation-based task assignment rate.
Best Practices¶
1. Stake Strategy¶
- Start small - Learn the system with minimum stake
- Lock strategically - Higher multipliers compound earnings
- Diversify timing - Don't lock everything at once
2. Voting Strategy¶
- Be consistent - Align with consensus over time
- Vote quickly - Response time affects reputation
- Abstain wisely - Better than incorrect votes
- Study patterns - Learn what validators consider valid
3. Risk Management¶
- Monitor reputation - Drop below 200 suspends tasks
- Maintain stake - Keep buffer above minimum
- Review slashing - Understand what triggers penalties
- Stay active - Inactivity causes gradual decay
4. Technical Setup¶
- Reliable internet - Don't miss vote deadlines
- Notifications - Enable alerts for new tasks
- Backup wallet - Have recovery phrase secured
- Monitor gas - Keep ETH for Base transactions
Troubleshooting¶
Common Issues¶
| Issue | Cause | Solution |
|---|---|---|
| Not receiving tasks | Low reputation | Build score with correct votes |
| Votes rejected | Deadline missed | Improve response time |
| Stake not showing | Transaction pending | Wait for confirmation |
| Earnings delayed | Payout threshold | Minimum 0.10 USDC to withdraw |
| Wallet mismatch | Wrong network | Switch to Base L2 |
Support¶
- Email: hello@f3l1x.tech
Glossary¶
| Term | Definition |
|---|---|
| RLM | Reputation-Linked Micropayment system |
| Stake | USDC deposited to participate |
| Lock | Period stake is non-withdrawable |
| Multiplier | Bonus for locking stake |
| Consensus | 2/3 majority agreement |
| Slashing | Penalty for incorrect behavior |
| Cooldown | Waiting period after slashing |
| Weight | Stake × Multiplier value |