Validator role
A validator may operate software, maintain connectivity, follow protocol rules and respond to faults.
Understanding staking projects
Staking projects use protocol rules to assign duties, voting rights or network participation to validators and delegators. Their terminology can sound familiar while the actual obligations differ materially between networks.
Iridia explains these structures for learning and general information. Nothing on this page is financial advice, a forecast or an invitation to participate.
Delegation role
A delegator may assign participation rights under stated conditions without operating the underlying service directly.
Governance role
Some projects connect participation with proposals, voting processes or community rules.
Questions before reading a project document
| Area | Question | Record |
|---|---|---|
| Lockup | Can assets or rights be withdrawn immediately? | Period and exceptions |
| Penalties | What happens after downtime or rule violations? | Defined events and process |
| Custody | Who controls credentials or assets? | Role and safeguards |
| Governance | How are protocol changes proposed? | Source and voting rules |
Reading sequence
- Identify the network and locate its current primary documentation.
- Separate protocol rules from the terms of a third-party service.
- List technical duties, access requirements and interruption procedures.
- Check lockups, fees, penalties and governance participation.
- Record which facts are confirmed and which remain uncertain.
“A staking explanation should describe obligations as carefully as it describes participation.”
Keep the vocabulary precise
- Do not treat a protocol parameter as a permanent feature.
- Do not describe historical distributions as a future outcome.
- Do not confuse a validator operator with a service provider.
- Do not omit custody or withdrawal conditions.
Iridia’s coverage is educational and should be read alongside current source documents.