Hyperliquid
Hyperliquid on Vike Trader: capabilities, order kinds, time-in-force handling, margin, fees, amend semantics and how the bridge is wired — rendered from the venue tables the runtime consults.
Hyperliquid is one of the 14 venues Vike Trader mounts through the shared bridge contract: the
runtime speaks to every venue through one ExecutionClient seam, and everything below is rendered
from the capability tables that seam is built on — caps_for,
venue_margin_support, fee_schedule_for, amend_semantics, attribution_for and venue_tif
in the Rust workspace — exported as venues.json at every release. This page cannot state a
stale capability: each table has a roster-completeness gate in the product tree, and a wrong row
fails that gate before it could reach here. What a table cannot hold — the operational judgement
— lives in the hand-written venues overview.
How the bridge is wired
Class: live-exec-recon. A default build mounts a real execution client from this venue's credentials and includes the venue in the default reconcile set: vike_mount::make_engine has an ungated arm for it. With no credentials in the store the venue stays paper — absent credentials are the live gate — and policy.venues.<id> in policy.toml is consulted before the credentials and can only ever refuse (vike_config::VenueMode::cap is a minimum, never a maximum).
Capabilities
| Capability | Value |
|---|---|
| Modify (amend) an order | yes |
| Native batch submit / cancel | yes |
| Reduce-only | yes |
| Combo (multi-leg) orders | no |
| Post-only | no |
| Batch size cap | no cap of the adapter's own |
| Backfill: bars | yes |
| Backfill: ticks | no |
Live market data the bridge feeds: bars, quotes, trades, depth.
Order kinds and triggers
Order kinds the adapter wires: market, limit, stop, stop_limit, take_profit. Trigger types for the
conditional kinds: stop-loss, take-profit. The vocabulary is the canonical one from
vike_model::venue_caps::ORDER_KINDS, not this venue's wire strings; the
orders concepts pages explain each kind's semantics and the per-venue
matrix.
Time in force
"Supported" is what the adapter wires; "accepted" is what it will take from a strategy without
rejecting — a TIF can be accepted and then coerced or ignored on the wire, and that is what the
last column says (vike_bridge_core::tif::venue_tif).
| TIF | Supported | Accepted | On the wire |
|---|---|---|---|
| GTC | yes | yes | mapped to Gtc |
| IOC | yes | yes | mapped to Ioc |
| FOK | no | yes | coerced to IOC (Ioc) |
| GTD | no | yes | coerced to GTC (Gtc) |
| Day | no | yes | coerced to GTC (Gtc) |
Margin
Margin modes the adapter offers: cross, defaulting to cross.
What the exchange itself offers (a vendor-documentation transcription, vike_model::venue_margin_support):
cross, isolated, switched at-leverage-set; the isolated-margin
wallet is not adjustable.
Fees
Percentage maker/taker: 1.5 bps maker, 4.5 bps taker (the default schedule; venue tiers and rebates are not modelled). The schedule is vike_model::fee_schedule_for's default row and is what the
cost model charges in a backtest.
Amending orders
A modify on this venue is applied as a cancel followed by a fresh submit — the order loses its queue position and, briefly, its protection
(vike_model::amend_semantics).
Attribution
A signed builder address that needs an on-chain approval first; set HYPERLIQUID_BROKER_CODE or HYPERLIQUID_BUILDER_CODE. An absent or invalid code degrades to no attribution with a
byte-identical wire (vike_model::attribution::attribution_for).
FXCM
FXCM on Vike Trader: capabilities, order kinds, time-in-force handling, margin, fees, amend semantics and how the bridge is wired — rendered from the venue tables the runtime consults.
Interactive Brokers
Interactive Brokers on Vike Trader: capabilities, order kinds, time-in-force handling, margin, fees, amend semantics and how the bridge is wired — rendered from the venue tables the runtime consults.