Fabrknt

Verifiable operations for onchain financial systems.

We build tools that leave a record of operational actions — oracle prices, config changes, what each signer signed — so your team, your partners and your users can check what happened instead of taking it on trust.

Get in touch See the products

Self-hostedNon-custodialChecked against public data

receipt 0x8f3a…c21eExample · verification passes

Action: Oracle price update
Market: EXAMPLE-PERP
Price: 41.82 → 41.95 (+0.31%)
Signed by: 2 of 3 signers (e.g.)
Block: 1,204,388

Move vs. 1% warning line0.31 / 1.00%

Anyone with the receipt file can re-check it against Hyperliquid's public data.

Illustrative receipt: values are made up

LoadingSelected markets from the xyz and km HIP-3 dexes · Hyperliquid public API

Loading…

Products

One habit, several tools: write it down, then let anyone check.

Our main focus is teams running perpetual markets on Hyperliquid under HIP-3. The same approach carries into accounting, stress testing and teaching.

Featured areaIndependent; built for HIP-3 on Hyperliquid; not affiliated with Hyperliquid

Fabrknt for HIP-3

Run Hyperliquid markets with evidence, not blind trust.

HIP-3 Ops
Self-hosted operations toolkit: oracle failover, separated roles, multisig, receipts.Testnet sending HL Price Guard
Solidity library for HyperEVM apps that read Hyperliquid prices.Library HIP-3 Record
What HIP-3 operators did, rebuilt from public data.Public

From HIP-3 Record

12 / 162markets marked on risk settings

Marked (near cap or thin book)No mark

Source: HIP-3 Record, risk settings scorecard, snapshot of 16 Oct 2026, 01:50 UTC, 4 dexes (xyz, io, para, mkts). A market is marked when its open interest is 80% or more of its cap, or more than 20× the book within 5%. Positions in the grid are illustrative.

IntentioLive

Onchain accounting. Ledger, audit and tax all come from one record, so the numbers agree.

Open Intentio →

Reactor

Sandboxes that show how a perp engine behaves under stress: gaps, thin books, liquidation cascades.

Go to Reactor →

Dojo

Engineering courses on Rust, the EVM and Reth, for people learning how onchain financial systems work.

Go to Dojo →

How we work

Evidence first. Claims second.

Three rules we hold ourselves to, in our products and on this site.

Write it down

Operational actions leave a record: who signed, what changed, by how much.

Check against public data

Receipts point to onchain facts, so anyone who has them can verify them without asking us.

Say what isn't done

Each product states its status plainly: what is tested, what is testnet-only, what is not audited.

Case · HIP-3 Record

SK Hynix: one oracle update, 72 seconds of liquidations

−15.6%in one oracle update

961long accounts liquidated

72 sof liquidations

1oracle update for the whole drop

Source: HIP-3 Record, SK Hynix liquidation replay. Market xyz:SKHX, 27 July 2026, 23:00 UTC: the operator's oracle dropped 15.6% in a single update; in the next 72 seconds 961 long accounts were liquidated. Rebuilt from Hyperliquid's public node data.

Oracle price (index, 100 = before)Long liquidations per 3 s

−15.6%, 961 and 72 s are from HIP-3 Record. The price path and per-bin shape are illustrative.

Running markets, or about to?

Tell us what you operate, and what you want to be able to show your partners and users.

Get in touch Request access