ChainLock Evidence

What it is

Bag it, log it, and every transfer of custody appends a row that cannot be edited afterward — corrections are new entries, never rewrites. Contraband, lab results, and K9 finds chain into the CaseLink case, which is what makes a lucky bust hold up in court roleplay. For owners whose court scenes collapse because the evidence trail is a screenshot. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. Escrow split publishes at release. In development; no runtime proof published — pending Shadow bench.

The problem it exists for

Evidence systems fail in the one moment they exist for: the argument about what happened. If an item's history can be edited, or lives only in the officer's memory of collecting it, then the evidence proves nothing and the scene collapses into two players asserting different pasts at each other. Chain of custody isn't a feature of an evidence script — it is the entire product.

Why we're building it

We already argue publicly that a ledger which can't survive a crash isn't a ledger (see /guides/stress-test-fivem-economy-scripts). Evidence is the same problem wearing different clothes: an append-only record whose value is precisely that nobody can quietly change it. We would rather build that correctly than ship a nice-looking item list.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed as an append-only chain: collected, moved, tested, presented — each step added, none overwritten.
• Designed to share the record with the MDT rather than keeping a private table nobody else can read.
• Designed so that who touched an item, and when, is a question with an answer.
• Designed to be server-authoritative end to end — a client that can forge an evidence event can forge an alibi.

What is not proven

The section every product page should have and almost none do.

• It is not released and not purchasable — nothing on this page can take money.
• No runtime proof published — pending Shadow bench. An append-only chain is a claim about behaviour under pressure, and nobody outside the studio has pressured it yet.
• No resmon figure — [MEASURED-PENDING].
• The $29.99 planned price is a target, not a commitment until the studio pricing lock.
• No release date exists to publish.

What we're building toward

Contraband → evidence bag → a custody timeline snapping onto an open case file.

Current status, stated exactly

• resmon [measured-pending]
• escrow manifest — at release
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any law & order resource

This applies to every product in this category, ours included, whenever it arrives. Hold ChainLock Evidence to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask whether an evidence entry can be edited or deleted, and by whom. If admins can silently rewrite it, the chain is decorative.
• Ask what the MDT sees. An evidence system that shares nothing forces officers to narrate the record out loud, which is the failure it was bought to fix.
• Ask how it validates net events — evidence writes are a client-reachable endpoint (see /guides/fivem-server-security-net-events).
• In our July 2026 survey we recorded exactly one evidence price, $24.99. One observation is an anecdote, not a market rate — check current prices yourself (see /guides/fivem-script-prices).

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.