Skip to content

Releases: opentensor/subtensor

v3.2.9-326

07 Oct 14:23
ae2b373

Choose a tag to compare

What's Changed

v3.2.9-323

30 Sep 22:50
79010a3

Choose a tag to compare

What's Changed

v3.2.8-320

25 Sep 18:38
835a2c9

Choose a tag to compare

Spec Version 320

Deregistration/Registration

Starting one week from this deploy (50,400 blocks after the mainnet deploy), subnet registrations will resume! The initial lock cost will be 2,000 TAO on day 7. The SubnetLimit is being introduced starting at 128. Registrations beyond this limit will trigger deregistration of the lowest scoring subnet. Some other parameters that have changed:

  • ImmunityPeriod is now 4 months (down from 6 months)
  • NetworkRateLimit has been raised from 2 days to 4 days
  • NetworkLockReductionInterval has been set to 8 days

For more information please see #1651 and/or BIT-0016.

Subnet Mechanisms (previously "Subsubnets")

Previously each subnet was capable of supporting a single "mechanism" (or problem that can be solved by miners and checked by validators via yuma consensus) out of the box unless the subnet implemented complex logic to simulate multiple mechanisms manually. Now subnets will natively support the concept of multiple mechanisms within the same subnet. This feature can be enabled at the discretion of the subnet owner, with an initial limit of 2 mechanism IDs per subnet (we plan to increase this later). This should be a huge boon for subnets that want to have miners work on multiple problems without needing to register multiple subnets, and subnets that want to try new miner code deployment strategies such as zero downtime deployment. Another positive effect of this change should be that multi-subnet ecosystems should feel less pressure to register multiple subnets since they will be able to do more with a single subnet, allowing them to unite multiple projects under a single market cap when desirable. This should foster new innovations by making it easier for existing subnets to experiment in a low-cost, low-risk way.

For more information please see:

btcli:

btcli subnet mech count
btcli subnet mech set
btcli subnet mech emissions
btcli subnet mech emissions-split

Trim UIDs

Some subnets have grown their set of miner UIDs to be larger than they originally intended. The Trim UIDs feature allows subnet owners in this situation to trim their set of UIDs down to 64 if and only if at least 20% of the resulting untrimmed UIDs are non-immune.

For more information please see #1998.

Hyperparameter Rate Limiting

We have introduced rate-limiting for hyperparameter changes within subnets. This should help prevent abuse by subnet owners and reduce volatility for stakers and subnet participants. The rate limit will be 2 tempos by default and applies to each hyperparameter individually (if you change hyperparameter A, you have to wait 2 tempos before changing it again, however this does not affect changing hyperparameter B, etc.). The triumvirate will update this rate-limit accordingly in the future via sudo call, as needed.

For more information please see #2048.

What's Changed

v3.2.7

10 Sep 00:13
81ee047

Choose a tag to compare

What's Changed

v3.2.6

28 Aug 15:46
737e4ac

Choose a tag to compare

What's Changed

Note that docker images for this release will be significantly delayed due to a CI issue.

v3.2.5

19 Aug 18:10
67c7ac6

Choose a tag to compare

What's Changed

v3.2.4

12 Aug 14:55
312c0be

Choose a tag to compare

spec_version: 301

What's Changed

v3.2.3

29 Jul 23:47
6309d35

Choose a tag to compare

What's Changed

v3.2.2

24 Jul 04:02
7b54109

Choose a tag to compare

What's Changed

v3.2.1

10 Jul 21:05
9f33e75

Choose a tag to compare

What's Changed