jarrodwatts/jev-trader

选用指南

AI 根据 README 整理 · 2026/10/16 21:21:41

使用方式

通过命令行运行，使用bun安装依赖并启动。

查看 README 依据

# jev-trader One decision every Monad block. A TypeSafe Jev model watches the Kuru MON-USDC order book and answers buy or sell every ~300 ms. Every block posts a real post-only limit order on that side, one tick inside the touch, replacing the last one. Fills happen when a taker hits it, so the bot earns the spread instead of paying it. A small server streams every block to the dashboard. ## Run cp .env.example .env bun install bun run start

部署要求

需要配置环境变量，如PRIVATE_KEY（可选，用于实盘），以及RPC URL等。

查看 README 依据

# jev-trader One decision every Monad block. A TypeSafe Jev model watches the Kuru MON-USDC order book and answers buy or sell every ~300 ms. Every block posts a real post-only limit order on that side, one tick inside the touch, replacing the last one. Fills happen when a taker hits it, so the bot earns the spread instead of paying it. A small server streams every block to the dashboard. ## Run cp .env.example .env bun install bun run start

With no `PRIVATE_KEY` it dry-runs: real book, real decisions, simulated fills. Set `MODEL=jev` and `TYPESAFE_AI_API_KEY` to use Jev; the default `mock` is a momentum heuristic stand-in. ## Endpoints Deployed (dry run, mock model): https://jev-trader-production.up.railway.app - `GET /` snapshot: model, wallet, dryRun, latest block event - `GET /history` last 1000 block events - `GET /events` SSE: `snapshot` on connect, then one `block` event per block, a `quote` event when a live order's receipt lands, a `fill` event when a taker hits a resting order, and a `ping` every 15 s

已知限制

默认使用模拟模型，若使用Jev模型需设置MODEL=jev和TYPESAFE_AI_API_KEY。

查看 README 依据

With no `PRIVATE_KEY` it dry-runs: real book, real decisions, simulated fills. Set `MODEL=jev` and `TYPESAFE_AI_API_KEY` to use Jev; the default `mock` is a momentum heuristic stand-in. ## Endpoints Deployed (dry run, mock model): https://jev-trader-production.up.railway.app - `GET /` snapshot: model, wallet, dryRun, latest block event - `GET /history` last 1000 block events - `GET /events` SSE: `snapshot` on connect, then one `block` event per block, a `quote` event when a live order's receipt lands, a `fill` event when a taker hits a resting order, and a `ping` every 15 s