dTao Compatible Subnet Deregistration

[JohnReedV]

dTao-Compatible Subnet Deregistration

Background

Since the dTao launch, our existing subnet deregistration (dissolve_network / remove_network) is no longer working correctly.

Subnet Pruning

• Triggered when SubnetLimit is reached
• Step 1: Exclude subnets still within NetworkImmunityPeriod
• Step 2: Among the rest, find the subnet with the lowest price EMA
• Step 3: If multiple share the same emission, pick the one with the earliest registration timestamp

Network Dissolution

• In dissolve_network / remove_network, perform full dTao cleanup:
  • Unwind liquidity providers
  • Destroy all α-in and α-out stakes
  • Distribute remaining Tao to α-out stakers pro-rata
  • Adjust the owner’s returned lock cost by subtracting the portion of total emissions the owner actually received (owner_received_emission = E * get_float_subnet_owner_cut()), so the final refund is max(0, lock_cost - owner_received_emission).
• Maintain root-only access to direct calls for now

Explicit Subnet Limit

Add new sudo hyperparameter SubnetLimit starting at 128.
Immunity period changed to 864_000 blocks (4 months) from 1_296_000 (6 months)
NetworkRateLimit 2 -> 4 days, 28_800 blocks.
LockCost will begin at 2,000 Tao
Registrations can begin to occur 7 days after the deploy.

High-Level Flow

New Registration → check slot cap?
  ├─ No → register network, grant immunity
  └─ Yes → prune one subnet → deregister → register new
Deregistration (manual or pruning) → unwind LPs → destroy α-in/out → distribute Tao → remove network

[creativeessence]

Add new sudo hyperparameter SubnetLimit starting at 256.

According to @unconst 's announcement (official Discord server), SubnetLimit is starting at 128, can you please clarify this?