Every check that ships in the offline kit also runs right here in your browser. Nothing leaves this page. If your network tab shows a single outbound call while the widget runs, we want to hear about it. Prompt. Proof. Provenance.
In-browser Offline after load Same engine as the kit Downloadable kit below
This widget is the offline kit, unrolled into your browser. It builds a real signed receipt, verifies it, lets you tamper with a byte and watch the check fail, then re-verifies the published 5,000-frame benchmark from a fingerprint alone. The signing engine is bundled and served from this same domain.
Every click prints the recomputed hash next to the stored hash, one line per layer. If a byte was changed, that layer will read FAIL in the same output. There is no server round-trip.
The widget above proves the offline kit in your browser with zero outbound calls. This one is different by design. It reaches the live Hive API and runs the public smoke route, so you see working primitives, not just an in-page reproduction. No account, no key, no payment, no telemetry beyond the single call you trigger.
Fourteen surfaces run with no credentials. One more is x402-gated and answers with a real payment challenge. Three sit behind a bearer and tenant. One is catalog-only and unconfigured today. This widget exercises the nine public checks the smoke route covers. Not every primitive in the catalog is implemented; the catalog is the honest map of which is which.
Live API call This leaves your browser and hits inkframe.thehiveryiq.com. The offline verifier above never does.
The four Filings under InkFrame v1 are on file with the USPTO. Both the in-page widget and the downloadable kit exercise the same four checks against a real signed receipt and a 5,000-frame benchmark manifest, using only public-safe code.
If your team prefers to verify from a shell on air-gapped infra, the zip below contains the exact same engine as the in-page widget. Eight files, three dependencies, four checks in one command. The kit hash is printed at the bottom of this page so you can compare it to what you downloaded.
The signing and gateway public keys are baked into both the widget engine and the download and printed below so you can compare them to what your run reports. If they match, you are checking against the same keys the fabric map references.
The four Filings under InkFrame v1 are the fastest path in for Equinix, but Hive's canon is broader. We mapped every Hive primitive against every Equinix Fabric surface, with a column for what we help you do now and what we help you take on next.
The widget, the engine bundle, the download, and the download path all sit on thehiveryiq.com. There is no interstitial, no shortener, no third-party host in the chain. If you fingerprint the download, you get the SHA-256 above. If you open your browser's network tab while the widget runs, you get zero external calls after the initial page load. That is the point.