Why EXITE waits: ANTH and SNDK entry checks
No fills is an observation, not a diagnosis. EXITE can wait for entry conditions, but a waiting caption cannot tell you whether data is fresh, permissions are ready or an existing position has been closed. Read those separately.
First identify the market
EXITE on Entropy lists io:ANTH and io:SNDK in the reviewed public selector. Eligibility still depends on current catalog permissions for manual selection and entries. A disabled item is not an invitation to bypass the restriction.
The venue is part of the market identity. Entropy io:SNDK and QFEX SNDK-USD are separate integrations; QFEX uses Risk core. Do not transfer one venue’s settings, balances or accounting assumptions to the other.
| Observation | What to check next |
|---|---|
| Waiting + fresh data | Selected market’s reason, session state and errors |
| Stale or disconnected view | Venue account and support; do not rely on the caption |
| Stop requested | Final session state, zero position and no remaining bot orders |
Read the reason, then check freshness
EXITE filters entry quotes instead of aiming to quote continuously. A displayed entry reason can explain why conditions currently fail. Less turnover can follow from waiting; lower CPM or profit does not necessarily follow.
Check that the selected market, session state and activity are updating. Read connection and error messages as well as the gate. If information is stale or contradictory, inspect the venue and contact support rather than declaring the session safe from its caption.
Do not copy ANTH thresholds into SNDK
The setup guide includes historical ANTH screenshots with five entry dials. They illustrate an earlier release, not a current SNDK parameter specification. Use the selected market’s current controls and limits; this article does not prescribe settings.
An open entry gate concerns entry eligibility. It does not prove that an order filled, that inventory is protected, that an exit completed or that the next trade will earn a spread. A maker fill can leave exposure to a price move.
Separate configuration from authorization
Save settings records a configuration; it is not Start. A selected market is not proof that a trading agent is approved or that a session is running. After any requested signature, check the resulting state rather than inferring success from the wallet prompt.
If the balance appears wrong, verify the account and its Hyperliquid account abstraction mode. Standard accounts can have separate balances; unified and portfolio modes behave differently. Do not make another transfer merely because an old screenshot shows a route.
Do not force volume to improve the number
Read the selected mode’s guide and review the actual wallet authorization before signing. Venue fees, funding and trading risks depend on your account and market.
CPM needs traded volume and a clearly defined period. With no volume, a cost-per-million comparison is not meaningful. At low volume it can swing sharply. Compare the same cost coverage and period, and account for open exposure; do not remove filters simply to produce a larger denominator.
A stopped run needs separate evidence
Use the signed Stop workflow and wait for its final outcome. Then verify the selected venue account has no position and no remaining bot orders. A Stop request, disconnected wallet or closed browser tab is not evidence that cleanup finished.
Do not start another mode on the same account before cleanup is confirmed. Venue or network failures can delay it, and closing exposure may realize a loss. If intervention is needed, follow the setup guide’s recovery guidance; this public article neither performs nor authorizes account actions.
Sources and next reading
Questions
Is waiting an engine failure?
Not by itself. Check the selected market’s entry reason, fresh data, session state and errors. A waiting caption alone cannot establish health.
Does an open gate guarantee a fill?
No. Entry eligibility, order placement, a fill and completed cleanup are different observations. Inventory and execution risks remain.
Are ANTH and SNDK thresholds identical?
Do not assume so. Historical ANTH screenshots are not a current specification for SNDK; read the selected market’s present controls.
Is QFEX SNDK-USD the same EXITE market?
No. EXITE uses Entropy io:ANTH or io:SNDK. QFEX SNDK-USD is a separate venue integration using Risk core.
Does Save settings start trading?
No. Saving configuration is separate from Start, wallet authorization and the resulting session state.
Can I treat no fills as no exposure?
No. Check positions and orders independently. An existing position or order can remain even when no new fill appears.