feat: add page with details on how to stop stacking

Author: BowTiedDevOps

SUMMARY.md

@@ -114,6 +114,7 @@
   * [Solo Stack](guides-and-tutorials/stack-stx/stacking-flow.md)
   * [Operate a Pool](guides-and-tutorials/stack-stx/operate-a-pool.md)
   * [Stack with a Pool](guides-and-tutorials/stack-stx/stack-with-a-pool.md)
+  * [Stop Stacking](guides-and-tutorials/stack-stx/stop-stacking.md)
 * [Community Tutorials](guides-and-tutorials/community-tutorials.md)
 
 ## 📚 Reference

guides-and-tutorials/stack-stx/stop-stacking.md

@@ -0,0 +1,60 @@
+# Stop Stacking
+
+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.
+
+---
+
+## Stopping Solo Stacking
+
+When stacking solo using the `stack-stx` function, your STX tokens are locked for a fixed period (the lock period) defined when you initiated stacking. **No additional action is required to stop stacking.** Simply wait until the lock period expires.
+
+{% hint style="info" %}
+In solo stacking, the `stack-stx` function returns an object that includes the `unlock-burn-height`. This is the burn block height at which your tokens will be automatically unlocked.
+{% endhint %}
+
+---
+
+## Stopping Pooled Stacking
+
+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 the tokens are eventually unlocked.
+
+### Step 1: Revoke Delegation
+
+Before your tokens 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 [pox-4](https://explorer.hiro.so/txid/SP000000000000000000002Q6VF78.pox-4?chain=mainnet) contract.
+
+<details>
+
+<summary>Function source code</summary>
+
+```clojure
+;; Revokes the delegation to the current stacking pool.
+;; New in pox-4: Fails if the delegation was already revoked.
+;; Returns the last delegation state.
+(define-public (revoke-delegate-stx)
+  (let ((last-delegation-state (get-check-delegation tx-sender)))
+    ;; must be called directly by the tx-sender or by an allowed contract-caller
+    (asserts! (check-caller-allowed)
+              (err ERR_STACKING_PERMISSION_DENIED))
+    (asserts! (is-some last-delegation-state) (err ERR_DELEGATION_ALREADY_REVOKED))
+    (asserts! (map-delete delegation-state { stacker: tx-sender }) (err ERR_DELEGATION_ALREADY_REVOKED))
+    (ok last-delegation-state)))
+```
+
+</details>
+
+Calling `revoke-delegate-stx` cancels your STX delegation, revoking the pool'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.
+
+{% hint style="warning" %}
+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.
+{% endhint %}
+
+### Step 2: Wait for Funds to Unlock
+After revoking your delegation, your STX tokens will still remain locked until the last stacking cycle chosen by the pool completes. The unlock occurs automatically at the predefined unlock burn height for that cycle.
+
+{% hint style="info" %}
+Even in pooled stacking, the unlocking mechanism follows the same blockchain timing as solo stacking. Revoking delegation only stops future stacking actions, it does not immediately unlock your tokens.
+{% endhint %}
+
+## Considerations
+- Monitor Your Stacking Status: Use your wallet's interface or the [Hiro Explorer](https://explorer.hiro.so?chain=mainnet) to track the status of your lock period and confirm when your tokens are available.
+- 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.