Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The paper-trading demo sends a BTC five-minute market snapshot to Jev. One Choice estimates whether the market will settle UP or DOWN relative to its opening reference; a separate Choice asks whether a paper trader should buy UP, buy DOWN, or wait now. The entry answer informs a simulated signal, subject to data, risk, quote-depth, and fee checks.

What Jev decides

Illustrative paper-trade entry decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · entry
YOUR APP
INSTRUCTION

Should a paper trader with no open position buy UP shares, buy DOWN shares, or wait now, accounting for outcome value, current asks, fees, depth, time, and uncertainty?

STATE

The source-defined model state contains the active market and reference price, seconds remaining, recent reference-price history and returns, UP/DOWN order books, fee schedule, and optional Binance perpetual features explicitly marked as auxiliary. Values change each cycle; this is not an observed market snapshot or Jev output.

JEV · CHOICE
  1. buy_up
  2. buy_down
  3. wait

App workflow

  1. Collect and validate a market snapshot

    The engine obtains reference prices, order books, market timing, fee data, and optional auxiliary perpetual-market features; stale or invalid observations block evaluation.

  2. Evaluate outcome and entry separately

    Jev returns probabilities for the terminal direction and for the entry actions. The entry policy uses the latter when configured as the entry decider.

  3. Recheck and simulate execution

    After inference, the engine fetches fresh data and rejects stale or changed-round results. It applies risk and depth checks, records paper trades in the ledger, and later settles positions from market resolution.

Why it is interesting

It asks Jev to separate terminal-outcome probabilities from the distinct decision to trade at current prices. The app then refreshes quotes after inference and uses a paper ledger, so a model preference alone cannot bypass execution and account constraints.