Stop Stacking
Last updated
Was this helpful?
Last updated
Was this helpful?
When you decide it's time to stop stacking your STX tokens, the process depends on whether you are stacking solo or delegating your tokens to a pool operator. This guide explains the steps for both scenarios.
When stacking solo using the stack-stx
function, your STX is locked for a fixed period (the lock period) defined when you initiated stacking or when you extended the lock period. No additional action is required to stop stacking, you simply have to wait until the lock period expires.
If you're stacking with a pool (where you delegate your STX via the delegate-stx
function), the process to stop stacking requires one extra step before your STX is eventually unlocked.
Before your STX can be unlocked, you must cancel the delegation with the pool operator. This is done by calling the revoke-delegate-stx
function through the pool's interface, or within the contract.
Calling revoke-delegate-stx
cancels your STX delegation, revoking the pool operator's access to further lock/stack your funds. Even after revoking the delegation, your STX will remain locked until the end of the last stacking cycle chosen by the pool (can be at most 12 cycles in the future).
Failing to revoke your delegation will mean that you continue to allow the pool to stack your STX until the reach of the burn block height mentioned in the delegate function (delegate-stx
). Ensure that you have successfully called revoke-delegate-stx
if you want to stop stacking sooner.
After revoking your delegation, your STX tokens will still remain locked until the last stacking cycle chosen by the pool operator completes. The unlock occurs automatically at the predefined unlock burn height for that cycle.
Plan Ahead: Since the unlocking is bound to cycle's timing, plan your stacking period or revocation accordingly to minimize delays in accessing your funds.
Monitor Your Stacking Status: Use your wallet's interface or the to track the status of your lock period and confirm when your tokens are available.
Using the API: Hiro's API offers an endpoint to , which contains the burnchain_unlock_height
height, representing the burn block height where your STX unlocks.