Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 12 subnets
About SN1, SN2, SN3, SN35, SN36, SN58, … (12 subnets)
Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN1, SN2, SN3, SN35, SN36, SN58, SN70, SN76, SN90, SN103, SN108, SN116, applying at block 9,265,581 (~24h). Stake delegated to it there routes through its children after that. On SN1 it replaces the change that was pending for block 9,265,413, which will not apply then.
ValidatorTensorplex LabsSubnetsSN1, SN2, SN3, SN35, SN36, SN58, SN70, SN76, SN90, SN103, SN108, SN116
Between blocks 9,258,378 and 9,258,445
More on-chain events
On-chainChild keysSN31, SN65, SN11842m agoBetween blocks 9,293,869 and 9,293,932
Validator 5HK2…YYXr scheduled a child-key change on 3 subnetsOn-chainChild keysSN31, SN65, SN11842m agoBetween blocks 9,293,869 and 9,293,932
Validator 5HK1…RJAK scheduled a child-key change on 3 subnetsOn-chainChild keysSN31, SN65, SN11842m agoBetween blocks 9,293,869 and 9,293,932
Validator Kiln (5F7d…r6LW) scheduled a child-key change on 3 subnetsOn-chainChild keysSN31, SN65, SN11842m agoBetween blocks 9,293,869 and 9,293,932
Validator 5EqY…oaUf scheduled a child-key change on 3 subnetsTaosis read this event directly from the Bittensor chain; every figure in it comes from the chain. No third-party data.