CannotAffordLockCost
Error Re-added v320 → v326, v334 → v377, v385 → current 7.116Why This Error Exists
Creating a subnet requires locking TAO as collateral - a significant amount that varies based on network demand. This lock cost mechanism ensures only serious participants create subnets and helps manage the total number of active subnets. The locked TAO is returned if the subnet is dissolved.
Deep Dive
NetworkMinLockCost is dynamic - it increases when subnets are created and slowly decreases over time. The actual cost you pay is max(NetworkMinLockCost, SubnetLocked(last_created_netuid)). This creates an auction-like mechanism where high demand drives up costs. The lock is tied to your coldkey and refunded if the subnet is later dissolved or pruned.
Debugging Example
You call register_network(...). Error: CannotAffordLockCost. Query NetworkMinLockCost - returns 10,000 TAO. Query System.Account(your_coldkey).free - returns 5,000 TAO. You need 10,000 TAO minimum, have 5,000. Either acquire 5,000+ more TAO, or wait for lock cost to decrease (check NetworkLockReductionInterval for decay rate).
Prevention Tips
- Query NetworkMinLockCost before attempting subnet creation
- Monitor lock cost trends - it decreases if no new subnets are created
- Budget for lock cost + transaction fees + initial stake
From Chain Metadata
Insufficient funds to meet the subnet lock cost
What This Means
Insufficient balance to pay the subnet lock cost.
Common Causes
- Lock cost is higher than your balance
- Lock cost varies based on demand
How to Fix
- Check SubtensorModule.NetworkMinLockCost for current cost
- Ensure sufficient TAO for the lock
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 116
- Error Code
- 7.116
- Runtime Version
- v393