τTaosisTaoScale
NewsOn-chainChild keysOct 28, 2026, 09:10 UTC

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

About SN118, SN128

Validator hotkey 5E2LP6EnZ54m3wS8s1yPvD5c3xo71kQroBw7aUVK32TKeZ5u announced new child keys on SN118, SN128, applying at block 9,388,439 (~24h). Stake delegated to it there routes through its children after that. On SN118 it replaces the change that was pending for block 9,387,369, which will not apply then.

Validatortao.botSubnetsSN118, SN128

Between blocks 9,381,195 and 9,381,254

Taosis newsletters

Taosis News: the week’s articles from the subnet teams, the press and community newsletters, every Friday. Taosis Weekly: the week’s movers, best yields and chain events, with dollar values, every Monday. Past issues

Newsletters

Your address is used only to send the newsletters you tick, with your consent (double opt-in). Unsubscribe anytime · Privacy

More on-chain events

On-chainChild keys35SN3526m agoBetween blocks 9,381,550 and 9,381,668
Validator Datura (5GP7…VCMi) scheduled a child-key change on SN35
On-chainOwner key swap38SN3826m agoBetween blocks 9,381,550 and 9,381,668
SN38 owner announced a coldkey swap
On-chainChild keys17SN1750m agoBetween blocks 9,381,491 and 9,381,550
Validator General Tensor (5Gga…xGTV) scheduled a child-key change on SN17
On-chainChild keys17SN1750m agoBetween blocks 9,381,491 and 9,381,550
Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on SN17
On-chainChild keys17SN1750m agoBetween blocks 9,381,491 and 9,381,550
Validator General Tensor (5DvD…diFp) scheduled a child-key change on SN17
On-chainChild keys17SN1750m agoBetween blocks 9,381,491 and 9,381,550
Validator TAO.app (5CoZ…bifj) scheduled a child-key change on SN17
On-chainChild keys32SN321h agoBetween blocks 9,381,431 and 9,381,491
Validator 1T1B.AI (5G9h…wrc5) re-scheduled a child-key change on SN32
On-chainLarge trade124SN1241h agoBlock 9,381,322
SN124 large sell: 761.2 τ

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

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