vike
StrategiesTemplates

Funding carry (funding_carry)

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

Funding carry holds a hedged spot/perpetual position to collect the funding rate. 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 funding_carry 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
symbolstring
qtynumber
tpnumber
slnumber
time_limit_msinteger (a whole number — 4.0 sets nothing)
trailingnumber
hold_periodsnumber
entry_thresholdnumber
venuestring
cooldown_msinteger (a whole number — 4.0 sets nothing)
venuestable

Live mount

Resolves but would not trade live. The registry's LIVE_CAPABLE row names the missing input: TWO-LEG and cross-venue: needs one declared mount leg per carry venue, and no mount surface declares legs today (vike_run::MountSpec's legs is empty on every spec, and the paper builder asserts it) — plus the same missing live funding series as funding_capture

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