vike
StrategiesTemplates

Trailing scalper (trailing_scalper)

The trailing_scalper portable strategy: what it trades, every parameter key with its TOML type, and whether it mounts live today — rendered from the strategy registry.

Trailing scalper enters on a trigger and rides a trailing stop, taking small moves repeatedly. It is one of the portable strategies — the names vike_strategy::strategy_by_name resolves for a live mount as well as a backtest — so a run profile or a daemon names it as trailing_scalper under [strategy], and the keys below arrive through [strategy.params]. The registry page explains the roster; the simulator-only page lists the names a backtest can still resolve that a daemon cannot.

Parameters

Each key is listed with the TOML type its reader insists on — read off the strategy's own from_params by the registry's gate, never chosen (vike_strategy::registry::PARAM_KEYS). A key of the wrong type is a silent no-op, which is why the type is stated.

KeyTOML type
qtynumber
half_spreadnumber
exit_delay_msinteger (a whole number — 4.0 sets nothing)
profit_targetnumber
entry_open_delay_msinteger (a whole number — 4.0 sets nothing)
entry_cutoff_before_close_msinteger (a whole number — 4.0 sets nothing)
market_open_msinteger (a whole number — 4.0 sets nothing)
market_close_msinteger (a whole number — 4.0 sets nothing)

Live mount

Resolves but would not trade live. The registry's LIVE_CAPABLE row names the missing input: NAKED SHORT on its own venue: from flat it rests a SELL leg documented as the single-token synthetic of buy Down (see its module doc), an equivalence that holds in the simulator — where a signed position may go negative for free — and NOT on the Polymarket CLOB it was written for, which requires the ERC-1155 outcome balance to sell. Live from flat that leg cannot rest, so the strategy degrades to a one-sided buyer while the backtest fills both sides; nothing in the mount path converts a sell into the Down-buy it is priced as

Where this comes from

The roster is vike_strategy::registry::PORTABLE_STRATEGIES; its parameter table and live verdict are that registry's PARAM_KEYS and LIVE_CAPABLE rows, held exhaustive against each other by the registry's own tests and exported as templates.json at every release. The glosses on this page are the one hand-written part; every table is rendered.

On this page