Watchtower Admin

What it is

One search across every Vice Drip ledger — money, vehicles, property, cases — to replay a dispute and show exactly what happened. Every admin action lands in the same append-only record it reads, so a staff-corruption complaint can be settled in either direction. Tamper-evident by construction, never absolute. For owners who want staff trusted because they can prove it. 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

Admin tools are the most powerful code on a server and the least audited. The question that matters isn't what an admin can do — it's what happened, who did it, and whether the log can be edited by the person who'd want to edit it. The second half of the problem is that a staff-corruption accusation is currently unanswerable in both directions: the owner cannot prove the money moved, and the accused staff member cannot prove it didn't, so the outcome turns on who is more trusted rather than on what occurred.

Why we're building it

We publish a standard that says claims should be checkable. An admin tool is where that standard gets tested on ourselves: a menu that can grant items and money without an immutable trail is the single largest unaudited surface most servers run. The design decision we think matters most is that it reads rather than writes — an oversight desk that can also move money is another money path to secure, and the whole point of the thing is to be the surface that watches the money paths, not one of them.

What it's designed to do

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

• Designed so every privileged action writes an append-only audit entry into the same record the tool itself reads, which is what makes a staff-conduct complaint answerable in either direction.
• Designed so the audit trail is not editable from inside the tool that writes it. Tamper-evident by construction, never absolute — a claim of absolute is a claim nobody can keep.
• Designed for permission checks on the server, never on the menu — a hidden button is not a permission, and a client that can call the event does not care what the menu showed it.
• Designed as a read layer over each product's own audit tables rather than a second copy of them, so there is no central table to fall out of sync with the ledgers it is supposed to be evidence about.
• Designed to say when it cannot see something. A product you do not run, or one outside the caller's scope, should be reported as excluded from a search rather than quietly producing a shorter list.

What is not proven

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

• It is not released and not purchasable. There is nothing to buy or download.
• No runtime proof published — pending Shadow bench. 'The auditor is itself audited' is the entire pitch and it is, today, an unproven claim about software you cannot inspect.
• No resmon figure — [MEASURED-PENDING]. A search across several products' history is a database-shaped cost, and we have not measured it.
• $39.99 is a planned target, not a commitment until the studio pricing lock.
• No release date.

What we're building toward

A dashboard scrubbing back through a money-flow timeline to the exact "gotcha" moment.

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 player economy resource

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

• Ask whether admin actions are logged immutably, and specifically who can alter the log. If the answer is that an admin can, the log is a courtesy rather than evidence.
• Ask whether permissions are checked server-side. If the menu simply hides options, any client can call the event anyway (see /guides/fivem-server-security-net-events).
• Ask whether the tool can move money, and if so, whether that path is audited to the same standard as the money systems it oversees. An oversight tool with an unaudited grant command is the exploit it was bought to catch.
• Ask what happens when a product it reads from is missing or its table has changed: does the search report the gap, or silently return fewer rows? A quiet gap in an audit tool is worse than an error.
• Our July 2026 survey recorded two admin prices, $12.99 and $29.99 — two observations is a thin sample, not a market rate, and the spread suggests the category means different things to different vendors (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.