go-forge · /solver
Operator front end for the OFFLINE V8-embedded reese84 forge. Pick a harvested
device profile, optionally adjust device-static fields, FORGE a payload, and
(optionally) VERIFY it offline or POST it live. Forge + verify never touch the
network; the live POST is OFF by default and explicitly gated.
0 · profile library
loading profiles…
label browser platform health captured size actions
Refresh library
Health: complete = canvas + fingerprint PNG + 765-sample audio +
WebGL(present/correctly-absent) + navigator/screen/window/zi_globals all present.
missing-* flags an incomplete capture (re-harvest that device).
self-test = the profile carries a self-consistent self-test
fixture (its own emitted p + frozen inputs); use the row's self-test button to
byte-verify the forge against it.
Offline self-test:
byte-exact common prefix (base64, capped)
1 · inputs
device profile
fresh session — random seed (varies cr) + real wall-clock + fresh 5×5 entropy canvas
1b · engine (embedded V8 / Chrome)
forge engine — the version-pinned V8 binary that runs (matching it to the device's Chrome makes the offline self-test byte-exact)
Build a new engine with tools/v8go-fork/build-engine.sh <chrome-major> --do-build
(heavy V8 compile; run on CI / a capable machine), then it appears here. See
tools/v8go-fork/UPGRADE.md.
2 · adjuster — device-static fields (class-A: forge re-derives dependent bytes)
Pin to engine Chrome 138
LOCKED (captured-replay; edit by swapping profiles, not fields):
canvas fingerprint PNG · audio render · WebGL readbacks.
AUTO-VARY per fresh session: the 5×5 entropy canvas + timer jitter.
3 · forge
Verify (offline backward-check after forge)
POST LIVE — send the forged token to the real server (sets confirm:true)
LIVE — sends to the real server. This is the only path that egresses to a
real Imperva endpoint. It fires only on this explicit opt-in, with confirm:true.
Forge payload
Idle.
4 · result
cr
og
sr
st
p length
structure
seed / clock
p (base64 reese84 token)