> For the complete documentation index, see [llms.txt](https://zynoxdev.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zynoxdev.gitbook.io/docs/escrow.md).

# What is FiveM Escrow ?

Understanding Cfx.re Asset Escrow & Keymaster Protection

***

## 📌 Introduction to Cfx.re Escrow

The **FiveM Asset Escrow System** is the official digital rights management and protection platform provided directly by **Cfx.re** (Rockstar Games). It allows creators to distribute secure, tamper-resistant resources while keeping essential configurations, language files, and client-side styling completely customizable for server owners.

Whenever you purchase an asset from the **Zynox Development Tebex Store**, the license is automatically deposited into your Cfx.re Keymaster account linked to your purchase email.

***

## 🔑 Accessing Purchased Assets

### 1. Log in to Keymaster

1. Visit the official Cfx.re Keymaster portal: [**keymaster.fivem.net**](https://keymaster.fivem.net)
2. Sign in with the **Cfx.re forum account** you used during the Tebex checkout.

### 2. Navigate to "Purchased Assets"

1. In the top navigation bar, click on **Purchased Assets**.
2. Locate your Zynox resource (e.g., `zx_restart_warning` or `zx_loading_screen`).
3. Click the **Download** button to retrieve the latest version.

> \[!NOTE] Ensure your server's `sv_licenseKey` in `server.cfg` belongs to the exact same Cfx.re account that purchased the asset. Otherwise, the server cannot authenticate your ownership.

***

## 🔄 License Transfers & Granting Access

Cfx.re allows you to manage licenses for server teams:

### Transferring Ownership (One-Time Transfer)

If you purchased the asset on a personal account and want to move it permanently to a community/server master account:

1. Go to **Keymaster ➔ Purchased Assets**.
2. Click **Transfer to another account** next to the asset.
3. Enter the destination Cfx.re username.

> \[!WARNING] Asset transfers are **permanent and irreversible**. Ensure the destination username is spelled correctly.

### Granting Access to Developers

If you employ developers or system administrators who need access without transferring ownership:

1. In Keymaster, go to **Granted Assets**.
2. Add the developer's Cfx.re username to grant temporary download and testing access.

***

## ⚠️ Common Escrow Errors & Fixes

### Error 1: `You lack the required entitlement to use <resource>`

* **Cause**: Your server's `sv_licenseKey` is registered under a different Cfx.re account than the one used to buy the asset.
* **Fix**: Ensure your `server.cfg` uses the license key from the purchasing account, or transfer the asset to the account hosting your server key.

### Error 2: `Failed to verify protected resource`

* **Cause**: Corrupted archive extraction or FiveM master server temporary outage.
* **Fix**:
  1. Delete the existing resource folder from your server.
  2. Redownload a fresh zip from Keymaster.
  3. Extract using 7-Zip or WinRAR (avoid built-in Windows Zip if path length issues occur).
  4. Restart your FXServer instance.

### Error 3: `Resource has invalid syntax or binary header`

* **Cause**: Server artifacts are outdated and cannot decrypt modern Cfx.re escrow encryption.
* **Fix**: Update your FXServer artifacts to build **5848** or newer.

***

## 💬 Need Assistance?

If you encounter any issues validating your license, please join the [**Zynox Development Discord Server**](https://discord.gg/zynox) and open a support ticket with your Tebex Transaction ID.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://zynoxdev.gitbook.io/docs/escrow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.