General FAQ for the visible BTHEX stack
This page consolidates product orientation, context reading, execution boundaries, access model, strategy profile, and legal limits so first-time visitors can move through the stack with a clear process.
Understand what BTHEX Signals is, how to read market context, what you control, and how access, plans, and risk boundaries work.
This page consolidates product orientation, context reading, execution boundaries, access model, strategy profile, and legal limits so first-time visitors can move through the stack with a clear process.
What BTHEX Signals is, what it is not, and who it is built for.
It is a context and workflow product built around licensed strategy infrastructure. It is not a generic signals channel and not a black-box promise product.
Outputs are organized by context quality, recency, validation depth, and workflow progression. You can move from high-level context to symbol detail, live monitoring, and optimization in one stack.
It is workflow-assisted. You can keep decisions manual or connect execution tooling, but activation, sizing, and risk remain user-controlled.
How to interpret Bias, Ref, Levels, and Risk zone without overreading them.
Bias is regime context, not an entry command. It describes directional posture in the current engine readout.
Ref is the contextual anchor price used to map progression. It is not a prescribed fill price.
Levels are projection zones used to track contextual progression. They are not blind limit orders.
Risk zone is contextual invalidation structure. It is not an exchange stop order and does not replace your own risk controls.
No. Context output is informational guidance for decision support. Execution decisions remain separate and user-controlled.
Use context first to read direction and structure, confirm with symbol-level history, then apply your execution plan with explicit size and risk.
Who controls entries, account connections, and operational risk.
BTHEX provides workflow infrastructure and monitored outputs. It is not discretionary trade execution on your behalf.
No. BTHEX does not manage client funds and does not custody exchange balances.
You do. BTHEX outputs context and infrastructure, but timing, sizing, and exit decisions stay with the user.
How to interpret freshness labels, empty tables, and symbol update timing.
Markets Coverage Board summarizes tracked symbols with current context state, reference readout, snapshot status, and update freshness.
Latest context is the most recent published engine output available for each symbol or module view.
Refreshing means the board is polling for updates. Empty states usually mean there is no new eligible output yet, or your active filters return no rows.
Updates are symbol-dependent. A symbol refreshes when new context or snapshot data is generated for that symbol.
A reference snapshot is the latest stored historical/backtest package used for validation context on a symbol.
How access layers work and what changes with plan depth.
The public Plans page currently shows a free 7-day Platform Trial entry. Trial and paid activation are handled through register/checkout flow.
Layers are positioned as Platform, Platform + Edge, and Full Stack. Higher layers add deeper validation, history depth, and API/integration capabilities.
VIP Context refers to the /vip edge dashboard with deeper reference context, segment history, and account transparency views. Access is plan-gated.
Latest context is current operational readout. Extended history adds longer validation windows, historical segments, and deeper diagnostics.
Yes. The platform presents standard plan layers, and custom team/integration scope can be requested through support.
Public operating profile, without exposing proprietary internals.
Yes. The Strategy page documents the operating profile and deployment fit at a high level.
The public profile states that structure reading uses Heikin, while execution alignment remains anchored to regular OHLC candles.
Primary operating fit is Futures. Spot is supported under long-only operating constraints.
Yes. Hedge is presented as the primary fit, and One-Way support is explicitly documented.
The public operating profile defines Spot deployment as long-only and does not use short-side behavior in that mode.
No. It explains operating boundaries and workflow behavior, not formulas, thresholds, or confidential trigger logic.
What you should and should not assume from the platform.
No. The platform is informational software infrastructure and does not provide financial advice.
No. The public policy states no personalized financial, legal, or tax recommendations.
No. No guarantees are provided, and historical outputs are not performance promises.
Yes. Market and derivatives risk can include partial or total capital loss. Risk management remains your responsibility.
No. Past outcomes and historical context are informational and do not imply future performance.
Check your local regulatory framework before use. Legal and contractual terms are governed by the Legal, Terms, and Disclaimer pages.