CannotReleaseYet
Error v154 → current 20.5ReleaseDelay hasn't passed since safe-mode ended.
Encountered by: validatorsdevelopers
Why This Error Exists
ReleaseDelay exists to give governance time to review deposits before release. You must wait this period after safe-mode ends. Governance can force-release if needed.
Deep Dive
The delay prevents hit-and-run attacks where someone enters safe-mode frivolously and immediately recovers their deposit. During the delay, governance can slash abusive deposits.
Debugging Example
Safe-mode ended at block 1000. ReleaseDelay is 500. You call release_deposit at block 1400. Error: CannotReleaseYet. Wait until block 1500 (1000 + 500).
Prevention Tips
- Query ReleaseDelay constant before attempting release
- Track when safe-mode ended and add ReleaseDelay
From Chain Metadata
This deposit cannot be released yet.
What This Means
ReleaseDelay hasn't passed since safe-mode ended.
Common Causes
- Calling release_deposit too soon after safe-mode ended
- Safe-mode hasn't ended yet
- Not accounting for ReleaseDelay constant
How to Fix
- Check current block vs (safe-mode end block + ReleaseDelay)
- Wait for ReleaseDelay more blocks
- Use force_release_deposit if you have governance privileges
Storage to Check
Runtime Info
- Pallet Index
- 20
- Error Index
- 5
- Error Code
- 20.5
- Runtime Version
- v393