Strategies
4 active
Dedicated signal infrastructure
Optix Signal v3.0
Validated trading infrastructure — from historical replay to controlled live execution.
Optix Signal is the software and dedicated server environment that runs the Trade Optix trading stack for signal users. It monitors markets continuously, replays historical scenarios, trades in sandbox — and when the user enables Live, it connects to their exchange account and submits real buy and sell orders inside limits they define.
v3.0 preview
V2.1 REMAINS THE CURRENT RELEASED VERSION
Risk
Normal
Optix Signal
v3.0
Running
Portfolio
Live
Control
Connected
Operating stateLive
Secure linkAES-256
ValidationPassed
Secure connection to the Trade Optix platform
Ecosystem position
A supporting pillar of the Trade Optix platform.
Optix Signal does not operate alone. Strategy intelligence, risk intervention, and oversight come from the wider Trade Optix platform; Optix Signal turns that into controlled activity on the signal user's own exchange account.
LAYER 01
Trade Optix platform
Strategy intelligence, risk systems, and platform oversight developed and operated by Trade Optix.
- STRATEGY INTELLIGENCE
- RISK INTERVENTION
- INFRASTRUCTURE MONITORING
- CONFIGURATION & OVERSIGHT
LAYER 02
THIS PAGE
Optix Signal environment
The signal user's dedicated trading and execution environment: the full algorithm stack, user-defined controls, three operating states, and validated deployment.
- FOUR-ALGORITHM STACK
- USER-DEFINED CONTROLS
- HISTORICAL & SANDBOX OPERATION
- LIVE ORDER EXECUTION
LAYER 03
Connected exchange
The signal user's own exchange account and portfolio. Orders arrive only when Live is enabled and every configured limit permits them.
- USER-HELD ACCOUNT
- REAL BUY / SELL ORDERS
- PORTFOLIO BALANCES
- ACTIVITY RETURNED TO USER
From signal to real execution
A signal becomes a real order only after every applicable check passes.
In Live mode, Optix Signal submits buy and sell orders to the exchange account the signal user has connected. Each order passes platform risk checks and the user's own configured limits before it leaves the signal server.
CONTROL PRINCIPLE
No live order can exceed what the signal user has configured. Turn Live off and the same pipeline runs end to end without touching the exchange.
-
01Strategy decision
An algorithm in the stack identifies a candidate buy or sell under the user's configuration.
-
02Risk and circuit-breaker checkGATE
Platform-wide protections are evaluated. If the Adaptive Circuit Breaker is restricting new buying, the signal does not become a buy order.
-
03User-limit validationGATE
Trading state, minimum balance, per-trade cap, hourly / daily / weekly / monthly spend, investment budget, allocations and target settings are all checked.
-
04Order preparation
Optix Signal builds the order on the dedicated signal server, where the user's exchange credentials are held.
-
05Submitted to the connected exchangeLIVE ONLY
In Sandbox or Watch-only operation this step is simulated or skipped entirely, as is a historical backtest run.
-
06Real buy or sell order
The order executes against the user's own portfolio at their exchange. Assets and balances remain in the user's account throughout.
-
07Portfolio and activity update
Positions, spend counters and activity records update, and the result is reported back through the Trade Optix platform.
Operating states
Three states. One is deliberate.
The operating state is an explicit setting, not an inference. Only Live places real orders — the other two keep the same system running with no exchange execution. Historical backtesting is a separate testing workflow, not an operating state.
SELECTED STATE
Live
Optix Signal is connected to the signal user's exchange account and may place real buy and sell orders. Every order remains bounded by the user's configured limits and by Trade Optix risk protection.
- Requires configured exchange API credentials and an explicit change of trading state.
- Buying stops when a spend cap, balance floor or allocation limit is reached.
- The Adaptive Circuit Breaker can restrict new buying at any time.
ENVIRONMENT STATE
Exchange connectionCONNECTED
Order routingREAL ORDERS
Market dataLIVE
Portfolio effectUSER PORTFOLIO
Risk protectionACTIVE
Why v3.0
A maturity step, built on the v2.1 foundation.
v2.1 established how Optix Signal operates in production. v3.0 takes that behaviour and hardens it: broader algorithm coverage, stricter configuration validation, and the same automated testing discipline used across the internal Trade Optix systems.
DIMENSION
V2.1 · FOUNDATION
V3.0 · PLANNED RELEASE
Algorithm coverage
Market Maker · Investment / Swing Trade
All four Trade Optix algorithms, including Profit Taker and Market Neutral
Signal-user historical testing
No integrated signal-user historical-testing workflow
User-defined historical scenarios, with backtest-to-sandbox continuity
Deployment
Installation and validation performed per unit
Repeatable installation and validation workflow on deployment-class hardware
Continuity
Historical results reviewed separately from the running environment
Backtest state can be imported and resumed in Paper / Sandbox mode
01
Hardened operational behaviour
Extensive bug fixes and clearer failure paths across the signal environment.
02
Improved error handling
Errors are detected, reported and contained rather than left to propagate.
03
Fewer unsafe configurations
Settings are validated so invalid or contradictory limit combinations are rejected early.
04
Continuous automated backtesting
Builds are replayed against historical scenarios on a repeating schedule, not only at release.
Continuous validation
Validated on the same class of hardware it runs on.
Several dedicated signal-server units sit inside the Trade Optix infrastructure environment purely for validation. A unit is reset to a known base system, given a fresh Optix Signal v3.0 installation, supplied with a historical scenario, and run through automated backtesting — then its behaviour is compared against expected results.
VALIDATION PIPELINE · REPEATABLE
STEP 01
Known base system
Unit booted and reset to a controlled baseline.
STEP 02
Fresh v3.0 install
The same installation workflow used in the field.
STEP 03
Historical replay
A defined market scenario is replayed through the build.
STEP 04
Behaviour comparison
Results checked against expected system behaviour.
STEP 05
Pass or investigate
A deviation stops the release path until it is understood.
VALIDATION UNITS · CURRENT CYCLE
UNIT 01
BASE IMAGE RESTORED
UNIT 02
INSTALLING V3.0
UNIT 03
REPLAYING SCENARIO
UNIT 04
COMPARISON COMPLETE
Illustrative view of a validation cycle. Units are dedicated deployment-class signal servers held inside the Trade Optix infrastructure environment — not customer equipment.
User-run historical tests
“What if Optix Signal had managed $5,000 in my Kraken account for six months?”
Coming with v3.0: signal users define their own historical scenario — exchange, starting capital, period, algorithms, limits and allocations — and Optix Signal replays it through the same environment that would have traded it.
Scenario builder
HISTORICAL BACKTEST
Exchange
Kraken
Starting portfolio
$ 5,000.00
Base currency
USD
Start date
2025-02-03
End date
2025-08-03
Algorithms
PLATFORM-MANAGED
CHOOSE MY OWN
Limits applied to the scenario
PER-TRADE CAP$250
DAILY SPEND CAP$2,000
MINIMUM BALANCE$500
ASSET SCOPEBTC · ETH · LTC · BCH
Scenario result
INTERFACE CONCEPT · DEMONSTRATION DATA
Scenario configured, not yet run
Run the test to replay six months of Kraken market history through this configuration.
STARTING
$5,000.00
ENDING · SIMULATED
$7,940.00 +58.8%
MAX DRAWDOWN
−5.8%
TRADES
1,140
SIGNALS EVALUATED
4,360
BUYING RESTRICTED
14 days
CB INTERVENTIONS
5
ALGORITHM PARTICIPATION
Market Maker
46%
Investment / Swing
27%
Profit Taker
18%
Market Neutral
9%
ENDING ALLOCATION
USD 41%BTC 24%ETH 18%LTC 11%BCH 6%
Illustrative interface data for design purposes. These figures do not represent an actual account or an achieved trading result. A historical replay describes what the configured environment would have done in past conditions — it is not a projection, a promise, or an indication of future results.
Backtest to sandbox
A historical test does not end as a report.
The portfolio and system state produced by the scenario can be imported into the signal user's own environment and resumed in Paper / Sandbox mode — so the scenario continues under current market conditions, still without placing real orders.
01
Historical test
Scenario replayed through the configured environment.
02
Review results
Activity, allocation, drawdown and restricted periods.
03
Import state
Ending portfolio and system state loaded into the environment.
04
Resume in Sandbox
Simulated trading continues under current conditions.
OPTIONAL · LATER
Move to Live — a deliberate user decision
Live is never the automatic end of the workflow. The signal user changes the trading state themselves, with credentials configured and limits in place.
The complete stack
Four algorithms. One protective layer above them.
v2.1 ran Market Maker and Investment / Swing Trade. v3.0 brings the full Trade Optix trading stack to the signal environment — with the Adaptive Circuit Breaker spanning all of it and the live execution path beneath.
Adaptive Circuit Breaker · protective layer
SPANS ALL ALGORITHMS AND THE LIVE EXECUTION PATH · NOT A TRADING ALGORITHM
Market Maker
SINCE V2.1
Active trading and inventory management within eligible markets.
Investment / Swing Trade
SINCE V2.1
Longer-horizon position management for qualified opportunities.
Profit Taker
NEW IN V3.0
A condition-specific strategy designed for deeply depressed market environments.
Market Neutral
NEW IN V3.0
Asset-expansion activity designed to operate across broader market regimes.
Live execution path · user-configured limits enforced
ACTIVE ONLY IN LIVE MODE
Roles are described here, not mechanics. Selection logic, thresholds and interactions between algorithms remain proprietary to Trade Optix.
User control
Automation does not remove control.
Every Optix Signal environment is bounded by settings the signal user owns. Trading state, exchange connectivity, spend windows, budgets, targets and per-pair allocations are explicit values — and the system will not act outside them.
- 01Changing the trading state — including enabling Live — requires explicit confirmation.
- 02Exchange credentials are stored on the signal server and are never displayed back.
- 03Reaching any cap pauses buying — the rest of the environment keeps running.
- 04Where enabled, AI-assisted limit management sets the spend windows on the user's behalf; it can be turned off and the values set manually.
Signal settings
INTERFACE CONCEPT
TRADING
Trading state
Real orders, simulation, or monitoring only.
Live
Change
Exchange API credentials
Held on the signal server. Editing requires verification.
••••••••
Configured
AI-assisted limits
Optional. Manages the spend windows below.
On — limits managed
LIMITS
MINIMUM BALANCE
$500
PER-TRADE CAP
$15
MIN GAIN TO SELL
1%
HOURLY
$50
DAILY
$250
WEEKLY
$1,000
MONTHLY
$2,000
INVESTMENT
One-time buyBTC/USD · $0
Continuous budget$1,000
Continuous target gain20%
ALLOCATIONS · BOUNDED BY THE BUDGET
BCH/USD
35%
ETH/USD
15%
LTC/USD
35%
BTC/USD
15%
Risk protection
The Adaptive Circuit Breaker sits above the whole stack.
It is a protective control layer used across the Trade Optix ecosystem — not a fifth algorithm. When conditions require intervention it can restrict new buying and stop new signals from becoming live buy activity, while the rest of the environment continues to operate and report.
It does not eliminate market risk, and it is not a guarantee against loss. Activation conditions are internal to Trade Optix.
PROTECTION STATE
ARMED
Restrict new buying
New buy activity is limited while conditions are judged unsuitable.
Halt new buy signals
Signals continue to be evaluated and recorded, but do not become live buy orders.
Protect during operational conditions
Intervention also applies when the environment itself is not in a suitable state to trade.
SELLING, REPORTING AND MONITORING CONTINUE · THE PLATFORM IS NOT SHUT DOWN
Continuous operation
Engineered to keep running.
01
Automated updates
Validated builds are delivered to signal units without manual intervention.
02
System health monitoring
Unit and process state are observed continuously by the platform.
03
Error detection
Failures are surfaced and contained rather than silently retried.
04
Data validation
Market and configuration inputs are checked before they influence decisions.
05
Repeatable testing
The same scenarios are replayed against every candidate build.
06
Secure platform link
Signal units communicate with Trade Optix over dedicated encrypted channels.
07
Deployment consistency
Every unit is installed from the same validated workflow.
08
Controlled recovery
After an interruption the environment returns to a known, safe state before trading resumes.
One platform
Optix Signal is one part of Trade Optix — not a product beside it.
The same strategies, risk systems, infrastructure and oversight that run the Trade Optix platform are what the signal environment participates in. Configuration, execution and validation all report back to the same place.
Strategies
The four-algorithm stack
Risk controls
Circuit-breaker protection
Portfolio
Holdings and activity
Infrastructure
Signal units and monitoring
User settings
States, limits, budgets
Execution
Live orders when enabled
Validation
Continuous automated testing
Oversight
Platform-side visibility
Optix Signal v3.0
See the infrastructure behind the signals.
Access to Optix Signal is arranged with the Trade Optix team. We will walk through the environment, the controls, and what changes with the v3.0 release.
V3.0 IS IN PREVIEW · V2.1 IS THE CURRENT RELEASED VERSION