τTaosisTaoScale

Bittensor subnet news

Subnet teams' own channels, X posts, press, newsletters and events read from the chain — GitHub lives in its own tab

On-chainChild keys121SN1213d ago

Validator TAO.app (5CoZ…bifj) scheduled a child-key change on 125 subnets

Validator hotkey 5CoZxgtfhcJKX2HmkwnsN18KbaT9aih9eF3b6qVPTgAUbifj announced new child keys on SN1, SN2, SN3, SN4, SN5, SN6, SN7, SN8, SN9, SN10, SN11, SN12 and 113 more, applying at block 9,281,605 (~24h). Stake delegated to it there routes through its children after that.

ValidatorTAO.appSubnetsSN1, SN2, SN3, SN4, SN5, SN6, SN7, SN8, SN9, SN10, SN11, SN12, … (125 subnets)

Between blocks 9,274,365 and 9,274,433

On-chainChild keys121SN1215d ago

Validator Tensorplex Labs (5E4z…ULde) re-scheduled a child-key change on SN121

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

ValidatorTensorplex LabsSubnetsSN121

Between blocks 9,263,097 and 9,263,160View subnet →

On-chainChild keys121SN1215d ago

Validator Firepool (5Deo…zD9Y) scheduled a child-key change on 68 subnets

Validator hotkey 5Deo9Q3SnZWNPSEPRTgapbyy6egKu2oaNSqD4RQHHJEuzD9Y announced new child keys on SN4, SN6, SN8, SN9, SN15, SN16, SN17, SN19, SN21, SN23, SN27, SN29 and 56 more, applying at block 9,269,281 (~24h). Stake delegated to it there routes through its children after that.

ValidatorFirepoolSubnetsSN4, SN6, SN8, SN9, SN15, SN16, SN17, SN19, SN21, SN23, SN27, SN29, … (68 subnets)

Between blocks 9,262,073 and 9,262,137

On-chainChild keys121SN1215d ago

Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 22 subnets

Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN98, SN99, SN100, SN101, SN102, SN104, SN110, SN111, SN112, SN113, SN114, SN115 and 10 more, applying at block 9,265,650 (~24h). Stake delegated to it there routes through its children after that. It replaces the changes that were pending on SN98 (block 9,265,320), SN99 (block 9,265,308), SN100 (block 9,265,323), SN101 (block 9,265,326), SN102 (block 9,265,329), SN104 (block 9,265,332) and 5 more, which will not apply then.

ValidatorTensorplex LabsSubnetsSN98, SN99, SN100, SN101, SN102, SN104, SN110, SN111, SN112, SN113, SN114, SN115, … (22 subnets)

Between blocks 9,258,445 and 9,258,514

sundae_bar || SN121@sundaebar_ai

Most AI tools hand you an empty box and wait. The hard part was never typing. It was knowing what to ask for. Scout starts from the job. Tell it what you keep redoing and it finds a ready-made agent or builds one, checking each skill against your setup. Link in the reply.

Full post on TaosisOpen on X ↗

On-chainChild keys121SN1219d ago

Validator Tensorplex Labs (5E4z…ULde) scheduled a child-key change on 6 subnets

Validator hotkey 5E4z3h9yVhmQyCFWNbY9BPpwhx4xFiPwq3eeqmBgVF6KULde announced new child keys on SN77, SN93, SN107, SN110, SN113, SN121, applying at block 9,236,338 (~24h). Stake delegated to it there routes through its children after that. On SN113 it replaces the change that was pending for block 9,230,025, which will not apply then.

ValidatorTensorplex LabsSubnetsSN77, SN93, SN107, SN110, SN113, SN121

Between blocks 9,229,134 and 9,229,196

sundae_bar || SN121@sundaebar_ai

Three audiences, three different updates, and the reason most internal comms fails is that they get sent one. The team needs the detail. The partner team needs what changes for them. Leadership needs the decision and the date. Paste the standup notes. It writes all three. Ask it for a status report without giving it any facts and it names the three things it needs first. It will not invent your update.

Full post on TaosisOpen on X ↗