# Trustless Mechanism: The Escape Hatch

<figure><img src="https://24377465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz93JXjGMa2bigdT2xBUy%2Fuploads%2FnfIVW95emQLwDp9lromE%2F(Trustless%20Mechanism).jpg?alt=media&#x26;token=d7d0e106-1522-4b72-9b16-14b6c12867d9" alt=""><figcaption></figcaption></figure>

This is the most critical feature affirming Bullbit's Web3 position. We answer the tough question: *"If Bullbit's Sequencer stops working or censors transactions, are my assets safe?"*

* **Inclusion Queue:** The system maintains a priority queue on the Blockchain (**On-chain Queue**). If a user wants to withdraw funds but the Sequencer does not process it, they can submit a request directly to the Inclusion Queue on Base L2.
* **Forced Compliance:** The Sequencer is forced to process requests in this queue within a specified **Time Window** (e.g., 24 hours). If the Sequencer deliberately ignores them, the Verifier Contract will reject all new Batches, paralyzing the system's ability to update its state, thus forcing the Sequencer to comply.