ncli_db validatorPerf is an advanced tool that helps you analyze the performance of your validator over time.
The tool requires that you build nimbus from source.
Make sure you're in the
1. Build ncli_db
The first step is to build
2. View options
To view the options available to you, run:
At the top you should see:
The default location of the
Near the bottom, you should see:
slots to restrict the analysis on a specific block range.
To view the performance of all validators on Holesky so far across the entire block range stored in your database, run:
You should see output that looks like to the following:
validator_index,attestation_hits,attestation_misses,head_attestation_hits,head_attestation_misses,target_attestation_hits,target_attestation_misses,delay_avg,first_slot_head_attester_when_first_slot_empty,first_slot_head_attester_when_first_slot_not_empty 0,128,0,127,1,128,0,1.0078125,0,3 1,128,0,125,3,127,1,1.0078125,0,2 2,128,0,127,1,127,1,1.0078125,0,5 ...
4. Adjust to target a specific block range
To restrict the analysis to the performance between slots 0 and 128, say, run:
5. Compare my validators to the global average
We'll use Paul Hauner's wonderful workbook as a template.
This workbook consists of three inter-related spreadsheets:
My Validators, and
Make a copy of the document.
Remove the table entries in
My Validatorsand delete everything in the
Import the output from
datasource. The easiest way to do this is to pipe the output to a
csv, remove the first few lines, and import the
Manually copy over your validator(s) to the
My Validatorssheet. The easiest way to find your validator's
validator_indexis to search for it by its public key on beaconcha.in (for example, this validator's index is 115733).
Go to the
Summarypage and view your results.
The workbook's method is explained here.