Question 1

Will it place live trades as soon as I start it?

Accepted Answer

No. It is dry-run by default and goes live only when session note jev.live is exactly yes, with one-sided BUY walls re-sited to SELL after a fill.

Question 2

What if I run it without a TypeSafe key?

Accepted Answer

The desk keeps running on pure math; Jev via jev-latest is an advisor with probabilities journaled, never a hard requirement, overridable by TYPESAFE_MODEL.

Question 3

Can Jev override a dirty rug card or cost floor?

Accepted Answer

No. Hard gates and cost tiers come first, _jev_math clamps answers to the role envelope and can refuse them, with no invented pools when scan is empty.

Question 4

What breaks if I mistype the run mode?

Accepted Answer

Nothing destructive: an unrecognised mode falls back to test rather than raising, while set_mode.py keeps book, slots, floors, and ceiling from drifting apart.

Question 5

What is it exactly, and how do I add it to a Condor checkout?

Accepted Answer

A Condor trading agent, not a Condor or hummingbot fork: you drop agents/jev/ into a Condor checkout. It scans the Meteora DLMM universe across the Top, Trending, New and RWA tabs, enriches with live eight-flag rug cards that fail closed, ranks hard gates first then a soft score of fee yield, depth, clean and tab, selects 3 to 5 distinct tokens with at most 2 from New under a slot budget using one Noul per candidate in a single call, sizes percent of book plus width under a cost tier, and gates each pool WAIT, SHIFT, REBUILD or SIT.

Question 6

What does the dashboard show, and what does it know about your machine?

Accepted Answer

Run python dashboard/live_bridge.py 8099 for a live desk or sim_jev.py for the same page driven by mock data. index.html polls /state.json every 2.5 seconds, so positions, decisions, trades and the confidence stream move on their own. The bridge carries no host paths, account ids or credentials and reads everything from the environment: CONDOR_HOME, JEV_STATE_DIR, CONDOR_USER_ID, JEV_MEMORY_DIR, and the Hummingbot API url, user and pass, which silently falls back to admin with an empty password.

Question 7

How do you test the decision logic without a key?

Accepted Answer

Three suites. test_jev_math.py covers the pure logic, test_jev.py the SDK and decision paths, and test_jev_transport.py drives the real typesafe_sdk client against a mock HTTP transport so the request actually put on the wire, the Noul fan-out, the Score levels and the jev-latest tag, is asserted without a key. Separately validate_agent.py checks routine discovery, the routine contract, strategy loading, and that no sibling entry or model-provider name leaked into the instructions, with the deny-lists supplied locally rather than hardcoded.

Jev Decision Maker At Meteora

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev community