- What does this list represent?
- Every validator that has ever been seen by our indexer on QRL 2.0 — either via a withdrawal (execution-layer) or a registry snapshot (consensus-layer). The columns combine both sides: status + effective balance + blocks proposed come from the consensus layer; total withdrawn comes from the execution layer.
- What's the QRL 2.0 stake requirement and how is it different from Ethereum?
- QRL 2.0 uses MAX_EFFECTIVE_BALANCE = 40,000 Quanta (Ethereum mainnet uses 32 ETH). Once a validator's balance exceeds 40,000, the excess auto-sweeps to its recipient address each epoch — that's what appears as withdrawals on /rewards. The minimum to stay in the active set is EJECTION_BALANCE = 20,000 Quanta; falling below triggers forced exit.
- What do the 9 validator-status values mean?
- The standard beacon-chain lifecycle: PENDING_INITIALIZED (deposit processed, no activation yet), PENDING_QUEUED (waiting for an activation slot), ACTIVE_ONGOING (staking + earning), ACTIVE_EXITING (voluntarily exiting, still earning), ACTIVE_SLASHED (slashed, awaiting forced exit), EXITED_UNSLASHED (cleanly exited), EXITED_SLASHED (forcibly exited after slashing), WITHDRAWAL_POSSIBLE (sweep-eligible), WITHDRAWAL_DONE (fully drained). Hover the status pill on any row for the full QRL2-specific context.
- How does a validator become active?
- Deposit the activation amount to the beacon-chain deposit contract. The validator enters the PENDING_QUEUED state and waits for an activation slot — QRL2 activates only a limited number of validators per epoch (the activation churn limit, MIN_PER_EPOCH_CHURN_LIMIT = 10). Once activated, duties (attestations + occasional block proposals + sync-committee assignment) kick in immediately.
- How are QRL 2.0 validator rewards paid out?
- Consensus rewards accrue to a validator's effective balance, which is capped at 40,000 Quanta. Any excess is swept automatically every epoch as an EIP-4895 withdrawal — a payout applied directly by the protocol to the recipient address, not a signed transaction. Those sweeps are the 'Total withdrawn' column here, with the full per-validator history on /rewards.
- What does it mean if a validator is slashed?
- Slashing is a protocol-level penalty for provable misbehaviour: proposing two distinct blocks for the same slot, OR casting two conflicting attestations (double-vote or surround-vote). Immediate penalty = effective_balance / MIN_SLASHING_PENALTY_QUOTIENT (= 1/32 of the stake). A correlation penalty is applied EPOCHS_PER_SLASHINGS_VECTOR / 2 = 512 epochs later, scaled by how many other validators were slashed in the same window. Slashed validators are forcibly exited.
- What do the Entering, Active and Exiting counts mean?
- They summarise the validator set's churn, read from the consensus registry. Entering counts validators in the activation queue (status pending); Active counts those securing the chain right now (active_ongoing); Exiting counts validators leaving the active set — voluntarily exiting or force-exited after a slashing (active_exiting / active_slashed). On a stable network both Entering and Exiting are usually zero.