Verification

The verified ledger

How fills are priced, how triggers are replayed, and the hash chain behind every account.

A track record is only worth something if nobody, including its owner and Kinfield, can quietly improve it. Signed-in trading is built so that the browser never decides anything that matters, and every event is written to an append-only hash chain that shows any later edit.

The browser only sends intentions

When you place an order, your browser sends what you want: market, side, size, leverage, order type, limit, take profit and stop loss prices, strategy and reason. Kinfield's server then:

  • fetches the fill price from Hyperliquid itself, for that one market, the moment the order arrives;
  • computes the market context itself from Hyperliquid's candles;
  • caps leverage at the market's limit and 20x, and checks free margin;
  • writes the position, the new balance and the ledger entry in a single database statement.

Your account is locked and read while the price is in flight, so two orders can't race each other, and the order fills at the price when it reached the server, not after processing. /api/health reports the server's current latency to its database and to Hyperliquid.

Triggers are replayed, not polled

Resting limit orders, take profit, stop loss and liquidation don't depend on anyone watching. Each time an account is read or changed, and on the agents' 15-minute run, Kinfield replays Hyperliquid's real price history since each order and position was last checked:

  • one-minute bars where Hyperliquid still has them, then 15-minute and hourly bars further back;
  • only bars that start after the last check, so price action from before a position existed never counts;
  • then the live price, for anything the bars haven't covered yet.

A limit fills at its price at the end of the first bar that trades through it, and the new position's own stops are then checked on the bars after. When one bar touches both a protective level and the take profit, the worse outcome is recorded. Closing by hand replays the position first, so a stop that was already hit can't be dodged. See How triggers are settled.

The hash chain

Every account has its own chain. Each entry stores its kind, its payload, the previous entry's hash and its own hash:

genesis    = sha256("kinfield:" + account_id)
hash[n]    = sha256(hash[n-1] + "\n" + kind + "\n" + canonical(payload))

canonical is JSON with object keys sorted alphabetically at every level, no spaces, and fields whose value is undefined left out, so the same payload always produces the same text. Because each hash covers the one before, changing, removing or reordering any entry changes every hash after it. The last hash, the head, therefore stands for the whole history.

Each nightly publish of the open dataset is a git commit, so the heads are timestamped in public. An older copy of a ledger file must always be a prefix of the newer one; anything else means the record was rewritten.

Entry kinds

KindWritten whenPayload fields
openA market order fills, or a resting limit fillsposition_id, coin, side, size_usd, leverage, entry_px, opened_at, strategy, rationale_commitment, features, tp_px, sl_px, agent_p. A limit fill instead records order_id, type and entry_fee; its commitment and features are on the order entry
orderA limit order starts restingorder_id, coin, side, size_usd, leverage, limit_px, placed_at, strategy, rationale_commitment, features, tp_px, sl_px
cancelA resting order is cancelledorder_id, cancelled_at
tpslTake profit or stop loss is changed on an open positionposition_id, tp_px, sl_px, set_at
closeA position closes by hand, take profit, stop loss or time limitposition_id, coin, exit_px, closed_at, pnl, fees, reason
liquidateA position is liquidatedposition_id, coin, exit_px, closed_at, pnl, fees

An entry, as published

{
  "kind": "close",
  "payload": {
    "position_id": "4f1c2a0e-...",
    "coin": "BTC",
    "exit_px": 102000,
    "closed_at": "2026-11-17T14:32:05.112Z",
    "pnl": 190.91,
    "fees": 9.09,
    "reason": "manual"
  },
  "prev_hash": "9b2e...c41d",
  "hash": "e07a...5f19",
  "recorded_at": "2026-11-17T14:32:05.230Z"
}

Times inside payloads are when the event happened in the market (Hyperliquid's time for a fill, or the end of the bar a trigger hit). recorded_at is when Kinfield wrote the entry.

Reasons on the ledger

The ledger never holds your written reason, only rationale_commitment, a salted hash of it. See Reasons stay private by default.

Resets and history

Resetting archives the account and starts a new one with a new chain. Nothing is deleted: the archived chain stays complete, stays on your record and, if you share, stays published. Only deleting your account removes your data. See Deleting your account.

What the ledger does and doesn't prove

  • It proves the published history is complete and unedited since it was published, that every trade in the dataset matches the entries that opened and closed it, and that a published reason is the one recorded at the time.
  • It relies on Kinfield's server having priced fills honestly from Hyperliquid. Fill prices and times can be compared against Hyperliquid's public candles.
  • It does not prove that a strategy would work with real money. See How it differs from a real exchange.