Errors/Chain errors

LockIdOverFlow

A chain-side capacity limit was hit; reduce the size or count of the request

View as Markdown

The global network-registration lock id counter reached its u32 maximum while queueing a subnet registration, so no new lock could be created. Check the NetworkRegistrationLockId storage value; this indicates lock id exhaustion, not a balance problem.

Declared by the SubtensorModule pallet; it classifies to the semantic code limit_exceeded.

Remediation

A chain-side capacity limit was hit; reduce the size or count of the request

The same explanation is available in the terminal: btcli explain LockIdOverFlow.