τTaosisTaoScale
NewsOn-chainChild keysOct 10, 2026, 10:24 UTC

Validator 01Lamida, Inc. (5CqR…b9Ed) scheduled a child-key change on SN19

About SN19 blockmachine

Validator hotkey 5CqRMuYSSqYkSa8AM3VawVfdyUhyBufyesvvgh3vCgaGb9Ed announced new child keys on SN19, applying at block 9,259,243 (~24h). Stake delegated to it there routes through its children after that.

Validator01Lamida, Inc.SubnetsSN19

Between blocks 9,252,041 and 9,252,105

View subnet →

SN19 blockmachine at a glance

SN19, blockmachine (α token t), is one of the independent markets on the Bittensor network, each with its own α token and its own price. Its α currently trades at 0.009159 τ (≈ $2.52), against 31,019 τ of pool liquidity. On-chain, the best-delegated validator on it yields about 57.11% APR (simple) and 76.94% APY (compounded), emissions add 0.001245 τ to the pool each block, epochs run every 7200 blocks. It was registered at block #1,956,072.

Chart, holders, conviction and every figure →

More on-chain events on SN19 blockmachine

On-chainChild keys1d agoBetween blocks 9,291,808 and 9,291,870
Validator 01Lamida, Inc. (5CqR…b9Ed) scheduled a child-key change on 3 subnets
On-chainHyperparameters2d ago
SN19 changed immunity period: 3,600 blocks → 21,600 blocks
On-chainChild keys2d agoBetween blocks 9,280,931 and 9,280,995
Validator 01Lamida, Inc. (5CqR…b9Ed) scheduled a child-key change on 2 subnets
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 keys5d agoBetween blocks 9,262,847 and 9,262,910
Validator 01Lamida, Inc. (5CqR…b9Ed) scheduled a child-key change on 2 subnets
On-chainChild keys5d agoBetween blocks 9,262,073 and 9,262,137
Validator Firepool (5Deo…zD9Y) scheduled a child-key change on 68 subnets
On-chainChild keys9d agoBetween blocks 9,233,902 and 9,233,965
Validator 01Lamida, Inc. (5CqR…b9Ed) 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.