UNL Reports
The validators each flag ledger of the Xahau Network reports as active, the ones missing from it, and what the ledger holds.
Active validators
Validators, report by report
| Validator | Missed | |
|---|---|---|
Incidents
| Validator | Missing from | Back in | Reports | For | Negative UNL | Report |
|---|
Reports with changes
| Ledger | Time | Active | Changes | Object | First applied | Report |
|---|
A report
Why a validator is missing from a report
Each flag ledger, the validators proposing it add a UNLReport transaction for every UNL validator that signed more than half of the 256 ledgers before it, as they saw them. Consensus decides each one on its own: a validator that was down or behind for half the interval, or whose validations reached too few of the others, has no transaction in the ledger and is missing from the report.
The same count, under half, has the Negative UNL disable the validator (a UNLModify transaction in the same flag ledger), so most incidents start with one. The Negative UNL disables one validator a flag ledger at most, and re-enables one only past 80% of the interval: a validator can be missing from a report without being disabled, and disabled while in the reports.
The ledger's UNLReport object is built again from each report's transactions. When the first of them applied in a ledger is an import VL key's, the object's validator list is not started again: it keeps the report before's validators and only adds to them, so it can list validators the report has no transaction for (stale). This page counts the transactions; a report's page shows both.