Reference
Metrics and data sources
Where the dashboard numbers come from and how to interpret reward comparisons, relay registrations, and delivery pace.
3 min readReward accounting#
The site joins Vouch’s public delivery records with BlockFerret’s stored per-block accounting using the block hash. The relay establishes which payload was delivered and its bid value; our accounting supplies the ordinary baseline, added MEV, costs, and shares.
The reward dashboard uses a trailing 48-hour window and refreshes every minute. Only delivered blocks with comparable accounting enter the reward comparisons.
Reward definitions#
| Metric | Meaning |
|---|---|
| Vanilla reward | Ordinary baseline priority-fee value for the same slot’s block comparison |
| MEV added to validators | Verified validator MEV share after costs, including any applicable rebate |
| Typical block | Median per-block reward uplift among comparable blocks; not the largest win |
| MEV added per block | Total added validator MEV divided by blocks with comparable accounting |
| Blocks with MEV | Comparable delivered blocks with positive added validator MEV |
| Delivered blocks | All relay deliveries for our builder key, including deliveries without a comparable baseline |
Why coverage matters#
An outside builder’s complete block may have no comparable ordinary baseline in our own accounting. Such a block counts as a delivery but is excluded from baseline reward comparisons. Its entire payout must not be labeled added MEV.
Unavailable accounting is a separate category. A changed percentage can reflect a different window, opportunity supply, or comparison coverage. It does not by itself identify a scraping failure or a loss of funds.
Relay and validator counts#
Relay registrations come from /relay/v1/data/stats/summary, using validators_registered. The collector reads JSON, not the relay website’s HTML. Active-chain validator counts come from the beacon API’s active-status filter.
Registrations are an all-time total. Some registered validators may no longer be active or connected. Dividing registrations by active-chain validators is a size comparison, not current proposer coverage.
Delivery pace#
The private RPC timing guide divides the full trailing 24 hours by the number of BlockFerret deliveries in that period. It includes quiet time, lost bids, and slots outside the relay. It is hidden when a complete window cannot be verified or there are fewer than two deliveries.
Public data endpoints#
| Data | Endpoint |
|---|---|
| Reward dashboard | quote.switch.win/blockferret/stats |
| RPC reach and delivery pace | quote.switch.win/blockferret/rpc-stats |
| Relay registration summary | boost-relay.vouch.run/relay/v1/data/stats/summary |
| Relay deliveries | /relay/v1/data/bidtraces/proposer_payload_delivered on the Vouch relay, filtered by builder public key |
Use the live dashboard for current values. These docs intentionally do not embed a performance snapshot that would become stale.