> For the complete documentation index, see [llms.txt](https://docs.bits.financial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bits.financial/protocol-overview/unstaking-queue.md).
# Unstaking Queue
### Mechanics and Functionality
The unstaking queue in the Bits Protocol is a transparent mechanism designed to manage withdrawals efficiently while maintaining the integrity of the staking pool. Upon deposit, the protocol ladders the lock-up periods for each contribution, distributing unlocks across days. This staggered approach ensures a consistent flow of available liquidity, preventing sudden outflows that could disrupt the system.
When multiple users initiate unstaking simultaneously, requests are processed in a first-in, first-out (FIFO) queue. Depending on demand and the volume of unlocking assets, processing may take from a few hours to several days. Users can visualize the queue in real-time through the protocol's interface, providing clear expectations on timelines.
This system emphasizes accountability by handling all operations with real assets on-chain, eliminating opacity and ensuring that unstaking is backed by actual BTC liquidity. By monitoring the queue, users gain insights into network activity and can plan their withdrawals accordingly, fostering trust and predictability in the protocol.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bits.financial/protocol-overview/unstaking-queue.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.