1. Match network and environment.
Choose the intended network from the network directory. Keep mainnet and devnet/testnet records separate. For example, the Octra link is explicitly a devnet address, while the Cosmos Hub page identifies a Cosmos Hub validator.
2. Compare the full identifier.
Compare the full address or operator identifier shown on the network page with the destination profile. For Cosmos Hub, match cosmosvaloper1j3remw0kpu5cwkhhkwtmenutzcdn06c4wq0s56. For Fermah, the published identifier is the prover name cp0x, not a wallet address.
A network-wide dashboard, such as the Interfold Dashboard, requires another step to identify a particular operator. The directory labels this difference.
3. Review current conditions at the source.
Check current commission, active-set participation and any withdrawal or unbonding conditions that apply. Inspect timestamps on performance data. A previously published APY or uptime number is not a current measurement.
4. Distinguish the route.
Direct staking, liquid staking and restaking can use different interfaces and conditions. On Solana, the validator profile and stakrSOL route are separate resources. On shared-security systems, identify the specific vault, network or AVS relationship.
5. Resolve discrepancies before proceeding.
If identifiers differ or an interface is unavailable, stop and confirm the destination through STAKR.space’s published contact channels. This website never asks for a seed phrase or private key. It links to external interfaces; it does not sign or submit transactions.
Sources & review
By STAKR.space · Reviewed