Research Tools
Reverse
Binary analysis for the FiveM game process. Turn an offset into a portable signature, carry it across every build we track, and inspect protected asset containers.
Reverse Tools
Two ways at the same binary. Search any of the 6,565 natives by name, namespace or hash and read off its implementation in the build you pick — or hand it an address instead and get an ida-sigmaker signature for every instruction that references it, with where each one lands in the other builds.
FXAP Inspector
Reads an .fxap container without executing it: magic and version, header fields, embedded resource metadata, a byte histogram and a per-block entropy map that shows exactly which regions are encrypted and which are not.
Access
Every resolve spends from one pool. How much it costs depends on how the answer had to be found, not on which tool you opened.
- All 5 builds, 6,565 natives
- Native resolver, offset reverser and cross-build scan
- ida-sigmaker signatures with symbol naming
- Tokens do not expire
- All 5 builds, 6,565 natives
- Native resolver, offset reverser and cross-build scan
- ida-sigmaker signatures with symbol naming
- Tokens do not expire
- All 5 builds, 6,565 natives
- Native resolver, offset reverser and cross-build scan
- ida-sigmaker signatures with symbol naming
- Tokens do not expire
The counts above are the extremes of one shared pool, not two separate allowances. A Reverser wallet is 250,000 tokens — 10 şifreli queries if every one of them needs the chain walk, 20 şifresiz if none do. Spend one on a şifreli lookup and the şifresiz count drops by two.