τTaosisTaoScale
NewsOn-chainChild keysOct 11, 2026, 23:40 UTC

Validator tao.bot (5E2L…eZ5u) re-scheduled a child-key change on SN5

About SN5 Hone

Validator hotkey 5E2LP6EnZ54m3wS8s1yPvD5c3xo71kQroBw7aUVK32TKeZ5u announced new child keys on SN5, applying at block 9,270,481 (~24h). Stake delegated to it there routes through its children after that. On SN5 it replaces the change that was pending for block 9,265,442, which will not apply then.

Validatortao.botSubnetsSN5

Between blocks 9,263,222 and 9,263,285

View subnet →

SN5 Hone at a glance

SN5, Hone (α 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.012589 τ (≈ $3.64), against 33,565 τ of pool liquidity. On-chain, the best-delegated validator on it yields about 56.08% APR (simple) and 75.20% APY (compounded), emissions add 0.001765 τ to the pool each block, epochs run every 360 blocks. It was registered at block #2,491,604.

Chart, holders, conviction and every figure →

More on-chain events on SN5 Hone

On-chainChild keys2d agoBetween blocks 9,274,365 and 9,274,433
Validator TAO.app (5CoZ…bifj) scheduled a child-key change on 125 subnets
On-chainChild keys4d agoBetween blocks 9,266,106 and 9,266,170
Validator tao.bot (5E2L…eZ5u) re-scheduled a child-key change on 3 subnets
On-chainChild keys5d agoBetween blocks 9,258,178 and 9,258,244
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 21 subnets
On-chainChild keys5d agoBetween blocks 9,258,178 and 9,258,244
Validator tao.bot (5E2L…eZ5u) scheduled a child-key change on 2 subnets
On-chainIdentity6d agoBetween blocks 9,248,200 and 9,248,226
SN5 updated its on-chain identity
On-chainChild keys7d agoBetween blocks 9,242,758 and 9,242,821
Validator tao.bot (5E2L…eZ5u) scheduled a child-key change on SN5
On-chainChild keys7d agoBetween blocks 9,242,384 and 9,242,447
Validator xTAO (5GcA…HZCV) scheduled a child-key change on 4 subnets
On-chainChild keys10d agoBetween blocks 9,222,562 and 9,222,624
Validator tao.bot (5E2L…eZ5u) scheduled a child-key change on 2 subnets

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