Cross-subnet synergy
the validators that hold the network togetherSubnets are not islands. The clearest connective tissue is the validator set: a small group of validators scores miners on many subnets at once, so their behavior, and their failures, propagate across the network. This is that overlap, computed from the on-chain validator permits, one validator per row with every subnet it secures. New to this?
Validators by cross-subnet reach
Reach = how many subnets one validator secures at once. A high number is a single point of correlation across the network. Click any validator to drill into its per-subnet scores.
Method: for every subnet we index the per-UID validator permit straight from Subtensor, then group by validator hotkey. A validator on many subnets is a single point of correlation (and of failure) that a per-subnet view hides. Next: capital rotation between pools, and entity linkage (github org, website, funding) for the operator graph that ownership keys deliberately do not reveal.



























































