τTaosisTaoScale
NewsOn-chainChild keysSep 29, 2026, 13:43 UTC

Validator 5HK1…RJAK scheduled a child-key change on SN52

About SN52 Dojo

Validator hotkey 5HK1Ubcg6MBwDGW7Td4RtAvE1FNyvkHvXKfwymW9q1BCRJAK announced new child keys on SN52, applying at block 9,181,089 (~24h). Stake delegated to it there routes through its children after that.

Validator5HK1Ub…BCRJAKSubnetsSN52

Between blocks 9,173,840 and 9,173,903

View subnet →

SN52 Dojo at a glance

SN52, Dojo (α token ا), is one of the independent markets on the Bittensor network, each with its own α token and its own price. Its α currently trades at 0.006008 τ (≈ $1.64), against 17,462 τ of pool liquidity. On-chain, the best-delegated validator on it yields about 48.08% APR (simple) and 61.74% APY (compounded), emissions add 0.000000 τ to the pool each block, epochs run every 360 blocks. It was registered at block #3,989,825.

Chart, holders, conviction and every figure →

More on-chain events on SN52 Dojo

On-chainChild keys1d agoBetween blocks 9,286,982 and 9,287,045
Validator 88 Root (5Djt…T4Kd) scheduled a child-key change on 7 subnets
On-chainChild keys3d agoBetween blocks 9,275,115 and 9,275,180
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on SN52
On-chainChild keys3d agoBetween blocks 9,274,365 and 9,274,433
Validator TAO.app (5CoZ…bifj) scheduled a child-key change on 125 subnets
On-chainChild keys3d agoBetween blocks 9,271,302 and 9,271,367
Validator Astrid (5ELR…qwVh) scheduled a child-key change on 29 subnets
On-chainChild keys4d agoBetween blocks 9,266,042 and 9,266,106
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on SN52
On-chainChild keys4d agoBetween blocks 9,265,977 and 9,266,042
Validator 5HK2…YYXr scheduled a child-key change on 3 subnets
On-chainChild keys4d agoBetween blocks 9,265,977 and 9,266,042
Validator 5HK1…RJAK scheduled a child-key change on 3 subnets
On-chainChild keys4d agoBetween blocks 9,265,977 and 9,266,042
Validator Kiln (5F7d…r6LW) scheduled a child-key change on 3 subnets

Taosis read this event directly from the Bittensor chain; every figure in it comes from the chain. No third-party data.