root_dissolve_network
Call v320 → current #120Dissolves a network using root authority.
View calls on chainCall Workflow
Click items to navigate. Pan and zoom to explore.
The Big Picture
Normal dissolution requires owner action and may have waiting periods. Root dissolution is the admin override - it removes a subnet immediately, regardless of owner consent or immunity periods. This is an emergency or governance power, not normal operations. Used when a subnet is harmful, broken, or abandoned and must be removed.
Why This Matters
Subnets are generally owner-controlled, but the network needs a way to remove problematic ones. Root dissolution provides this nuclear option. It's heavily restricted (only root/sudo can call it) and should be used rarely and with justification.
Example Scenario
Subnet 42 is running malicious code that harms participants. Governance decides it must be removed immediately. Admin calls root_dissolve_network(netuid=42). The subnet is gone within one block, regardless of the owner's wishes or immunity period remaining.
Common Questions
- Can the subnet owner prevent root dissolution?
- No - root authority overrides owner control. That's the point. If an owner could block it, malicious owners could keep harmful subnets running.
- What happens to the lock deposit?
- Depends on the reason for dissolution. Malicious subnets might have deposits slashed. Emergency removals might return deposits. Check governance decision.
- Is there a warning before root dissolution?
- Usually governance processes involve discussion and voting before using this power. In emergencies, it might be immediate. Check community channels for context.
Use Cases
- Emergency removal of malicious or broken subnets
- Governance-mandated subnet shutdown
- Cleanup of abandoned subnets
- Network maintenance and security response
From Chain Metadata
Remove a subnetwork The caller must be root
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | netuid | u16 | Subnet/network identifier (0-65535) |
Permissions
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller has root/sudo privileges
- Network exists
Effects
Events Emitted
Storage Modified
Postconditions
- Network removed immediately
- All neurons deregistered
- Subnet parameters cleared
Side Effects
- Administrative override of normal dissolution
- Bypasses immunity period and owner consent
- Lock may or may not be returned depending on circumstances
Possible Errors
Code Examples
import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";
const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });
// Build root_dissolve_network call
const netuid = 1;
const call = api.tx[stringCamelCase("SubtensorModule")][stringCamelCase("root_dissolve_network")](
netuid
);Runtime Info
View Source- Pallet Index
- 7
- Call Index
- 120
- First Version
- v320
- Current Version
- v393