v0.1.17618 Aug 2026·Rendering, Networking, Privacy & Shields

Witness Mode: cryptographic, offline proof of what a site showed you (a world-first)

Every browser can save a page. None can prove what a site showed you IN RESPONSE to what you did - that you clicked Cancel and it said cancelled, that a price was what it was at checkout, that you rejected a consent dialog. Screen recordings and session-recorder tools capture a claim you have to be trusted on; they prove nothing. This release makes the interaction itself verifiable. Because the engine renders a saved page as a pure function of its bytes - the same input always paints the same pixels - a recorded session (the saved page plus the exact list of clicks, keystrokes and scrolls, each stamped with a logical time) can be replayed by anyone, offline, and checked frame by frame against a hash chain. The one thing that made this impossible before, time, is now virtualized during replay: the one place the real clock used to leak into a page is pinned to the recorded moment, so a page that stamps the instant you clicked still replays identically. Each frame is tied to the one before it in a chain, sealed into a receipt - move, drop or reorder a single action and the check fails at that exact point, and forging a different story is not feasible. It is shown from start to finish: a Cancel button that says 'cancelled' is recorded, the site is taken offline, and the session still verifies from the saved copy alone - and recording it twice comes out identical even though the page reads the clock, which is the whole point. No mainstream browser can do this: their rendering is not repeatable, their pages cannot be played back the same way twice, and a reload quietly loads something different. This is the fourth capability from the same root - after Render Receipts, Pixel Provenance and Counterfactual Browsing - now sealing an interaction over time rather than a single view; the same recording also lets you freeze a tab and prove the one you bring back is identical to the one you closed. Security moves 43 to 44; the overall holds at 58, because a new capability like this is real but not one of the big under-the-hood pieces the overall score waits on. It is available today under the hood, not yet a one-tap panel in the app. Its honest limits (the time is self-reported, with no internet involved by design) are explained inside the app.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Privacy & Shields	Witness Mode: record what you actually did on a page - your clicks, typing and scrolls, in order - and get proof of what the site showed you in response. Play it back later, on any machine, with no internet, and it comes out identical. No browser has ever been able to turn 'it said cancelled when I clicked Cancel' into something you can actually prove.
Rendering	The one thing that used to make a page impossible to replay - the clock - is now handled, so a page that stamps the exact moment you clicked still plays back identically. That is what lets a recorded session be re-checked by anyone rather than simply taken on trust.
Privacy & Shields	It is tamper-evident down to the step: change, drop or reorder a single action in the recording and the check fails at exactly that point, and forging a different story is not feasible. Shown from start to finish - a Cancel button that says 'cancelled' is recorded, the site is taken offline, and it still verifies from the saved copy alone.