> For the complete documentation index, see [llms.txt](https://casefun.gitbook.io/casefun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://casefun.gitbook.io/casefun/mechanics-case-opening-and-multi-open-modes.md).

# Mechanics: Case Opening & Multi-Open Modes

## 📦 Case Opening & Multi-Open Modes

The **CaseFun Opening Engine** allows users to open project cases in real time, leveraging verifiable randomness smart contracts to distribute token rewards instantly to non-custodial wallets across both the Web platform and Telegram Mini App.

***

### ⚡ Multi-Open Capabilities (Batch Unboxing)

To maximize user efficiency and accommodate high-volume gameplay, CaseFun supports multi-case openings in a single operation:

* **Supported Multipliers:** 1x, 2x, 3x, 4x and 5x cases per execution.
* **Gas Efficiency:** Batching multiple case openings into a single contract call significantly reduces total network gas overhead compared to single openings.
* **Aggregated Outcome Reveal:** Users receive a consolidated breakdown of all dropped token quantities across all opened cases in a unified UI card.

***

### 🚀 Execution & Speed Modes

Players can adjust the opening experience depending on their preference for visual engagement or execution speed:

| Mode              | Visual Experience                                                                  | Ideal For                                                           |
| ----------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Standard Mode** | Full 3D/2D cinematic roulette animations and sound effects for maximum excitement. | Casual players, high-stakes case openings, and streamer recordings. |
| **Fast Mode**     | Skips roulette roll animations; reveals drop outcomes within \~1 second.           | High-frequency traders and automated opening strategies.            |
| **Flash Mode**    | Instantaneous outcome calculation with zero animation latency.                     | Maximum throughput multi-open sessions (e.g., 5x batch openings).   |

***

### 🎲 Provably Fair Engine Integration

Case openings dynamically route through the user's selected **Provably Fair** provider:

* **Random.org Mode (Default / Fast Track):**
  * Instant execution.
  * **Zero extra wallet transaction signatures required.**
  * Perfect for Telegram Mini App mobile sessions and Fast/Flash modes.
* **Chainlink VRF Mode (On-Chain Proof):**
  * Cryptographic proof generated on-chain.
  * **Requires an extra wallet signature** for randomness request verification.
  * Ideal for institutional/large-value drops requiring 100% on-chain proof.

***

### 📱 Cross-Platform Parity

All case openings, multi-open multipliers, and speed settings operate with **100% real-time synchronization** between the desktop Web interface ([casefun.net](https://casefun.net)) and the native Telegram Mini App ([t.me/casefun\_bot](https://t.me/casefun_bot)).


---

# 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://casefun.gitbook.io/casefun/mechanics-case-opening-and-multi-open-modes.md?ask=<question>&goal=<endgoal>
```

`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.