ONEPORT RESEARCH · R1

OnePort Live execution

On this page

OnePort Live execution

Execution model#

Live starts from a frozen Paper deployment, so the same Strategy, parameters, account keys and instrument routes carry forward. The signal source does not have to match the execution venue: a Strategy may use market data from venue A and place an order through a mapped account on venue B.

OnePort OpenAPI's official symbol and product type determine the executable instrument. Order, fill and position quantities are coin quantities without a second contract-size conversion inside OPR. Strategies explicitly quantize calculated values to the frozen steps, and submission rejects a step mismatch without silently rewriting it. Minimum quantity, minimum notional and per-order maximums remain venue rules; OnePort's Live response is authoritative. The same order result shape is used across Backtest, Paper and Live.

The preparation page shows the products currently eligible for new orders. SPOT and supported linear perpetual routes can be activated; instruments or product types not shown there cannot be added to that deployment.

Portfolio and account permissions#

A OnePort connection only exposes Portfolios and accounts available to that credential. Select one Portfolio as the source of authoritative NAV and equity, then map every Strategy account key to a distinct current member account.

The Strategy may trade only a subset of the Portfolio's accounts. Unselected members stay read-only and still contribute to the Portfolio's NAV and equity. If more than one selected account can trade the same venue, choose the account for each instrument explicitly.

Portfolio NAV and equity cover every member, while position and exposure details cover only the accounts selected for this deployment. Because those scopes differ, the Live dashboard does not calculate Portfolio gross exposure, net exposure or leverage from the selected accounts. Review account risk individually: gross exposure includes spot and derivatives, while leverage is shown only when debt, derivative and equity valuations are complete.

Connection	Owned by the user and revocable at any time
Portfolio	Provides full-Portfolio NAV and equity
Trading accounts	A distinct Portfolio member for each Strategy account key
Instrument routes	Determine where each order is submitted; signal data may come from another venue

From Paper to Live#

Live creation accepts the same strategy_memory_gb profiles. If omitted, it inherits a stored Paper selection; when the source is a legacy Paper with no stored field, the new Live deployment defaults to 8 GiB. Existing legacy Live deployments themselves retain the 2 GiB runtime fallback. The Agent must display the current tier's choices and ask before creating the stopped configuration.

Connect OnePortAdd a revocable OnePort OpenAPI credential in Settings. Exchange secrets remain managed by OnePort.

Choose Portfolio and accountsSelect the Portfolio, map the Strategy's trading account keys, and confirm the route for every instrument.

Review the preflightCheck Portfolio equity, account status, positions, open orders and exact routing before activation. OPR does not inspect or change venue leverage or position mode.

Activate, then startActivation reserves the selected trading accounts but keeps the deployment stopped. Start is a separate confirmation.

Monitor and controlUse saved local or native IDs when the Strategy chooses to query an order. The dashboard shows only the last local observation; OPR does not poll, confirm, close or cancel orders in the background.

Stop versus retireStop fences Strategy execution but retains the account binding and local evidence. After Stop, Retire releases the binding without inspecting, cancelling or closing venue state; OPR then stops monitoring and external state is managed by you at OnePort, the venue or another external tool.

Live NAV, equity and capital flows come from the selected OnePort Portfolio and therefore include every Portfolio member, including read-only accounts. Account balances and positions come from OnePort account facts. Order and fill rows are only the last locally persisted synchronous response or Strategy-requested exact lookup.

When OnePort does not provide a value, the dashboard shows it as unavailable instead of replacing it with zero or a local estimate. A temporary Portfolio-performance delay does not erase current account facts or the last local order observations.