ADV
Availability
% Forged
ADV2
Availability
% Forged
ADV3
Availability
% Forged
ADV4
Availability
% Forged
Availability is the percentage of scheduled slots where the pool attempted to forge blocks. Forged is the percentage of blocks confirmed on chain compared to the expected slots. Both metrics are calculated across the previous 20 epochs.
We track a large number of metrics to ensure that the ADAvault pools are reliably forging blocks including:
- the expected number of leader slots based on pool stake,
- leader slots scheduled,
- blocks forged and confirmed on chain.
Cardano uses a Verifiably Random Function (VRF) to schedule the leader slots. This averages over time to 100% of the expected slots, but there can be significant short term variance, particularly when pools are smaller.
ADV
The graph shows expected slot allocation based on stake, scheduled leader slots allocated, and blocks forged then confirmed on the blockchain. We show tabular data below for the last 20 epochs.
Epoch | Expected | Scheduled | Luck | Forged | MGSI* |
ADV2
ADV, ADV2 and ADV3 have similar performance profiles. In all cases note the ghosted and stolen blocks become more likely as a pool gets closer to 100% saturation.
Epoch | Expected | Scheduled | Luck | Forged | MGSI |
ADV3
Epoch | Expected | Scheduled | Luck | Forged | MGSI |
ADV4
Slot leader allocation for ADV4 has a greater variance while the pool is smaller. There are less stolen and ghosted blocks as the potential for VRF collisions is also reduced. This can result in higher performance.
Epoch | Expected | Scheduled | Luck | Forged | MGSI |
* M=Missed, G=Ghosted, S=Stolen, I=Invalid (see below for more details).
There are stolen and ghosted blocks in some Epochs where an assigned block was minted by another pool. This is a standard part of the Ouroboros Praos protocol with the decision based on the pool VRF key. See discussion on implementation here https://github.com/input-output-hk/ouroboros-network/issues/2014
Key to headings;
Expected: The expected number of leader slots based on active stake
Scheduled: Number of slots scheduled to lead and attempt to forge a block
Luck: The percentage of leader slots scheduled vs expected
Forged: Number of blocks forged and subsequently confirmed on-chain
Invalid: Node attempted but failed to forge block (for unknown reasons)
Missed: Scheduled at slot but no record of pool attempting to forge and no other pool has made a block for this slot
Ghosted: Block created but marked as orphaned and no other pool has made a valid block for this slot, possibly due to height battle or block propagation issue
Stolen: Another pool has a valid block registered on-chain for the same slot, possibly due to VRF contention and more than one pool assigned to the slot
Historic performance data is refreshed periodically, there will be some lag against the real time statistics for block production in the current epoch.
Observability
ADAvault uses BetterStack for alerting, plus Prometheus and Grafana to monitor infrastructure and collect data from nodes.

ADAvault has very low latency measurements for connectivity to peers. This is important as it increases the likelihood that the blocks forged by the stake pools are adopted on chain. Real time details are available from PoolTool.io who measure propagation delays across all registered pools.
We regularly review global peer connectivity, and are confident the pools have excellent performance characteristics for reliable block production.