Jito StakeNet is a decentralized Solana stake pool manager, blending Validator History and Steward Programs for secure, transparent validator management and autonomous stake operations.
The Validator History Program, a component of Jito StakeNet, is an on-chain record of verified Solana validator data, storing up to 512 epochs of history per validator. It takes fields accessible to the solana runtime like validator performance history, validator commission, MEV commission, as well as Gossip data like validator IP, version, and client type, and stores them all in a single account. It also contains some fields that currently require permissioned upload but are easily verifiable with a getVoteAccounts call, like total active stake per validator, stake rank, and superminority status. All these fields are stored in a single account per validator, the ValidatorHistory account. This enables all these disparate fields to be easily composed with in on chain programs, with a long lookback period and ease of access through the single account.
The main Anchor program is in programs/validator-history.
src/lib.rs- entrypoint for instructionssrc/state.rs- containing the account definitions as well as logic for appending all the fields to the main circular buffersrc/instructions/*.rs- individual instructions
ValidatorHistory: Tracks historical metadata on chain for a single validator. Contains a CircBuf, a data structure that acts as a wrap-around array. The CircBuf contains entries of ValidatorHistoryEntry, which stores validator metadata for an epoch. The default/null value for each field is the max value for the field's type.
Note that this is a zero_copy account, which allows us to initialize a lot of space without hitting runtime stack or heap size liimits. This has the constraint of requiring the struct to implement bytemuck::{Pod, Zeroable} and following C-style struct alignment.
Config: Tracks admin authorities as well as global program metadata.
Harnessing on-chain validator metrics and network data, the Steward Program employs advanced algorithms to evaluate and rank validators. Automated keepers then execute a state machine to optimally allocate stake, maximizing network security and efficiency.
On-chain Steward accounts for JitoSOL:
| Account | Address |
|---|---|
| Program | Stewardf95sJbmtcZsyagb2dg4Mo8eVQho8gpECvLx8 |
| Steward Config | jitoVjT9jRUyeXHzvCwzPgHj7yWNRhLcUoXtes4wtjv |
| Steward State | 9BAmGVLGxzqct6bkgjWmKSv3BFB6iKYXNBQp8GWG1LDY |
| Authority | 9eZbWiHsPRsxLSiHxzg2pkXsAuQMwAjQrda7C7e21Fw6 |
| Program | Date | Commit |
|---|---|---|
| Steward | 2024-07-29 | f4ea93a |
| Validator History | 2024-01-12 | fc34c25 |
anchor build --program-name validator_history (regular anchor build)
solana-verify build --library-name validator_history (solana verified build)
Verify with solana-verifiable-build:
solana-verify verify-from-repo -um --program-id HistoryJTGbKQD2mRgLZ3XhqHnN811Qpez8X9kCcGHoa https://github.com/jito-foundation/stakenet
Tests are in tests/ written with solana-program-test.
All tests can be run by running ( root directory ):
./run_tests.shCheck out the Keeper Bot Quick Start
This CLI can be used to see the status of on-chain validator history data.
Build: cargo b -r --package validator-history-cli
To see the current epoch state of all validator history accounts:
./target/release/validator-history-cli --json-rpc-url <YOUR RPC URL> cranker-status
To see the historical state of a single validator history account:
./target/release/validator-history-cli --json-rpc-url <YOUR RPC URL> history <VOTE ACCOUNT>
This CLI can be used to see the status of on-chain steward data.
Build:
cargo b -r --package steward-cliTo view the config:
./target/release/steward-cli --program-id Stewardf95sJbmtcZsyagb2dg4Mo8eVQho8gpECvLx8 view-config --steward-config jitoVjT9jRUyeXHzvCwzPgHj7yWNRhLcUoXtes4wtjvTo view the state: (Note: This fetches a lot of accounts, you may want to use your own RPC)
./target/release/steward-cli --json-rpc-url YOUR_RPC view-state --steward-config jitoVjT9jRUyeXHzvCwzPgHj7yWNRhLcUoXtes4wtjvTo see the state of each validator in the context of the steward add --verbose
./target/release/steward-cli --json-rpc-url YOUR_RPC view-state --steward-config jitoVjT9jRUyeXHzvCwzPgHj7yWNRhLcUoXtes4wtjv --verboseTIP: To use your own RPC configured in your solana config, use the following:
--json-rpc-url $(solana config get | grep "RPC URL" | awk '{print $3}')
To see all of the available commands:
./target/release/steward-cli -hTo see more info on the Steward CLI check out the CLI notes