τTaosisTaoScale
NewsOn-chainChild keysOct 9, 2026, 13:42 UTC

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

About SN61 RedTeam

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

Validator5HK1Ub…BCRJAKSubnetsSN61

Between blocks 9,245,834 and 9,245,897

View subnet →

SN61 RedTeam at a glance

SN61, RedTeam (α 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.011047 τ (≈ $3.04), against 14,036 τ of pool liquidity. On-chain, the best-delegated validator on it yields about 34.69% APR (simple) and 41.47% APY (compounded), emissions add 0.001484 τ to the pool each block, epochs run every 360 blocks. It was registered at block #4,457,976.

Chart, holders, conviction and every figure →

More on-chain events on SN61 RedTeam

On-chainChild keys39m agoBetween blocks 9,297,975 and 9,298,129
Validator 5HK2…YYXr scheduled a child-key change on 5 subnets
On-chainChild keys39m agoBetween blocks 9,297,975 and 9,298,129
Validator 5HK1…RJAK scheduled a child-key change on 5 subnets
On-chainChild keys39m agoBetween blocks 9,297,975 and 9,298,129
Validator Kiln (5F7d…r6LW) scheduled a child-key change on 5 subnets
On-chainChild keys39m agoBetween blocks 9,297,975 and 9,298,129
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on SN61
On-chainChild keys1d agoBetween blocks 9,288,552 and 9,288,615
Validator Tensorplex Labs (5E4z…ULde) re-scheduled a child-key change on SN61
On-chainChild keys1d agoBetween blocks 9,287,296 and 9,287,360
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 2 subnets
On-chainChild keys1d agoBetween blocks 9,287,232 and 9,287,296
Validator 5HK2…YYXr scheduled a child-key change on 6 subnets
On-chainChild keys1d agoBetween blocks 9,287,232 and 9,287,296
Validator 5HK1…RJAK scheduled a child-key change on 6 subnets

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