> For the complete documentation index, see [llms.txt](https://nanoscripts.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://nanoscripts.gitbook.io/docs/information/fivem-asset-escrow-system.md).

# FiveM Asset Escrow System

FiveM Escrow is an asset protection system provided by FiveM for all platform content creators. It encrypts most purchased assets, ensuring robust security. This system effectively prevents all types of dumps and bypasses, safeguarding your exclusive Pluto Development's asset.

### You lack the required entitlement to use `resource_name` <a href="#you-lack-the-required-entitlement-to-use-resource_name" id="you-lack-the-required-entitlement-to-use-resource_name"></a>

Your server is using a FiveM license key that is not linked to the original purchase, indicating the resources were bought with a different FiveM account.

Alternatively, this issue might occur if the asset was installed without restarting the server. Try restarting your server to confirm if this resolves the problem.

### Failed to verify protected resource `resource_name` <a href="#failed-to-verify-protected-resource-resource_name" id="failed-to-verify-protected-resource-resource_name"></a>

Files were possibly corrupted during transfer.

Ensure the encrypted files are copied; the .fxap file must be included. Some FTP programs skip these files. If you use [FileZilla](https://filezilla-project.org/), try using [WinSCP](https://winscp.net/eng/index.php) instead.

### Syntax error \</1> and similar <a href="#syntax-error-less-than-1-greater-than-and-similar" id="syntax-error-less-than-1-greater-than-and-similar"></a>

The problem can be caused by several factors. Maybe you do not have the artifact version higher than +4960, be sure to use that artifact version or higher. You can get your latest [Linux ](https://runtime.fivem.net/artifacts/fivem/build_proot_linux/master/)or [Windows ](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/)artifacts here.

Another factor could be that you have edited encrypted code which you should not do or simply that you did not restart the server after installing this asset, try to resolve it with these two more options.