Docs. Everything You Need, In One Place.

#Pick The Path That Fits.

Three common starting points. Click a card to jump straight to what you need. New here? The fastest path for any persona is to import a preconfigured layout from Discord — see Shared Layouts.

#Get Trading In 6 Steps.

1. Subscribe. Visit paradoxalgo.com/pricing and choose Core or Pro.
2. Submit your TradingView username. Sent automatically with your welcome email. Scripts are typically granted within minutes (up to 24 hours in rare cases).
3. Accept the invitation. Open the invite link in your inbox to enable script access in TradingView.
4. Load the tools. In TradingView open the path below. Every tool you have access to appears ready to deploy. Indicators → Invite-Only Scripts
5. Configure for your style. Set asset class and trading style — the tools auto-tune internally. Manual overrides available for power users.
6. Paper trade first. Run in simulation for at least a week before going live. Verify the signals match your expectations.

#Skip Configuration. Just Run A Layout.

You do not have to figure out the "best" settings yourself. Our team and the community publish complete TradingView layouts — preconfigured charts with the indicators, strategies, inputs, sessions, and timeframes already dialed in. Import a layout, save it as your own, and you're ready in under two minutes. This is the fastest path from zero to running.

Where to find layouts in Discord

How to import a shared layout

Layouts are shared as TradingView links. The flow takes under two minutes:

1. Open the layout link. In Discord, click the layout URL in the post. TradingView opens in your browser with the chart and all its settings already loaded — but at this point you're viewing the author's layout, not editing it.
2. Save it to your account. In the top-right of TradingView, click the cloud icon (Save Layout) → pick "Save As..." → give it a name you'll recognize (e.g. Paradox Apex Eval — my copy). The layout is now in your personal Chart Layouts list under your account.
3. Confirm the indicators / strategy are on the chart. Look at the bottom panel — you should see the Strategy Tester populated and any indicators visible. If they're missing, your account doesn't yet have access to those scripts (check your Pro tier and TradingView username in your account portal).
4. Inspect the inputs before going live. Click the gear icon next to each indicator/strategy → review the input panel. The layout author has already set everything — but it's still your responsibility to know what you're running. Spend two minutes reading the inputs.
5. Set up your alert. If the layout is for automated execution, create the webhook alert (Condition: Any alert() function call) as described in Webhook Setup. Layouts do not include alerts — alerts are per-user.
6. Run the 3-Gate ladder. Even with a community-validated layout, follow the Three-Gate ladder. Don't skip Paper just because someone else's backtest looks good.

Why layouts beat manual configuration

• Zero setup time. No hunting through input panels, no copy-pasting numbers from a recipe.
• Reproducibility. Backtests published with a layout are reproducible by anyone who imports it — you know you're running the exact configuration that was tested.
• Updates flow automatically. When the official team ships a new strategy version, an updated layout is posted alongside. You re-import once and you're current.
• Community knowledge. Member-shared layouts often reveal use cases the official team hasn't published (specific eval firms, exotic instruments, unique session windows).
• Safer for new users. Reduces the risk of misconfiguring an input you didn't realize mattered.

#Setup Recipes.

Reference setups for common use cases. Treat these as starting frames — not prescriptions. Every trader's instrument, account size, broker, and risk tolerance is different, so adapt the recipe to your situation, validate in backtest, and use a shared layout from Discord whenever possible to start from a known-good configuration.

#What Is Paradox Algo?

Paradox Algo is a quantitative trading ecosystem for TradingView. Three automated strategies, six manual indicators, and an AI strategy optimizer — all built on advanced statistical models and institutional finance principles. Designed to work across crypto, forex, stocks, and futures markets, our models analyze the context of a move (volatility regimesVolatility regime: the market's current personality — quiet, normal, or wild. The algo measures it in real time and adapts its risk to match., order-flow imbalancesOrder-flow imbalance: when one side of the order book is consistently being absorbed faster than the other. Often a leading signal for big moves., liquidity zones) instead of relying on simple crossover signals.

#What's Included.

Yearly Pro is the same Pro tier, billed annually at 75% off and locked for life.

#Six Quant Tools.

The indicator suite is purpose-built for discretionary traders who read the market themselves. Each indicator surfaces a different dimension of price action — trend, momentum, regime, structure, edge — so you can layer them into an approach that fits your style. No prescribed strategy: you decide which combination of signals warrants an entry, your own stop placement, and your own targets.

#The Three Engines.

Three strategies, three different jobs. Each is a fully automated TradingView strategy with its own input panel, prop-firm framework, and webhook payload builder. Pick by use case:

#Optimize Any Strategy Autonomously.

Stratera is our macOS desktop app. Load any TradingView strategy, set your target metrics (SharpeSharpe ratio: reward per unit of risk. Higher is better. Anything above 1 is solid; above 2 is rare in trading., profit factor, net profit, max drawdown, win rate), click Optimize. Stratera autonomously runs thousands of adaptive backtests in the background — experimenting with input configurations until it finds the combo that maximizes your target.

What Stratera does

• Works with any TradingView Pine strategy you have access to — Paradox products or your own
• Detects the loaded strategy and pulls its inputs — every tunable parameter can be optimized
• Adaptive search: the engine learns from each iteration instead of brute-forcing every combination — full runs typically complete in minutes, not days
• Multi-target: maximize Sharpe ratio, profit factor, net profit, or win rate — or minimize max drawdown
• Outputs a ranked results dashboard and applies the winning configuration back to your TradingView strategy
• Runs 100% locally — your strategies and results never leave your Mac

Download & install

1. Visit paradoxalgo.com/stratera and scroll to the download section.
2. Enter the email address tied to your Pro subscription (the one you used at checkout). Our system verifies your active subscription and the download starts automatically (~80MB DMG).
3. Open the .dmg and drag Stratera into Applications, then eject the DMG.
4. Double-click Stratera in Applications. On first launch macOS may show a developer-verification prompt — click Open (first launch only; if it won't open, right-click the app → Open → confirm).

• OS: macOS 12 (Monterey) or newer — Apple Silicon (M1/M2/M3/M4) and Intel both supported. macOS only; no Windows or Linux version.
• Subscription: active Pro membership — verified by email at download time. Core members: Stratera is a Pro-tier tool.
• TradingView: a TradingView account — free or paid both work for backtesting.

Connect to TradingView

• Stratera operates against your TradingView session in your default browser — open TradingView there and make sure you're logged in before launching Stratera.
• Launch Stratera — it auto-detects the TradingView session.
• If the connection drops or doesn't auto-detect: Stratera → Preferences → TradingView → re-authenticate.

Your first optimization run — step by step

1. In TradingView, open a chart with the strategy you want to optimize loaded on it.
2. Switch to Stratera — it detects the strategy and pulls its inputs.
3. Pick your target metric: Sharpe ratio, profit factor, net profit, win rate — or max drawdown (minimize).
4. Set bounds for each input you want optimized (e.g. Target Multiplier 2–5). Anything you don't bound, Stratera holds fixed — that's how you lock inputs you've already settled.
5. Click Optimize. Stratera runs adaptive backtests in the background — you can keep using your Mac while it works. Runs typically complete in minutes; tighter bounds converge faster.
6. Review the ranked results dashboard, pick the winner, and apply it — your TradingView strategy's input panel updates with the new configuration.
7. Before going live: validate out-of-sample (next callout) and paper-trade the configuration for at least a week.

Stratera troubleshooting

What Stratera doesn't do

• It doesn't trade. Stratera is a research and optimization tool, not a trading bot — it never places orders.
• It doesn't touch the cloud. Local Mac app only; your strategies, settings, and results stay on your machine.
• It doesn't run on Windows or Linux. macOS only.
• It doesn't manage your account or capital. You review, you decide, you apply.

Learn more about Stratera →

#What's New in v7.4.

CrossTrade is now built in (NinjaTrader 8)

• Native provider. Pick CrossTrade from the Webhook Provider dropdown, paste your CrossTrade key and NinjaTrader account name, done — no more hand-building custom templates for NinjaTrader.
• Fixed bracket mode (default): every entry ships with its take-profit and stop attached, held at NinjaTrader at the chart's exact prices.
• ATM mode (the trailing stop): point the algo at your saved NinjaTrader ATM template and NinjaTrader runs your stop, target, and a tick-level auto-trail on its own — even if your connection drops mid-trade. The dashboard's Trail row shows the exact trigger/distance numbers to copy into the template. One rule: your Contracts setting must match the template's contract count.
• Exit Mirror (on by default): when the chart closes a trade, NinjaTrader closes with it and cancels leftover orders — chart and broker stay in sync automatically.
• Strategy tagging (automatic): Paradox's trades stay in their own lane — other bots on the same NinjaTrader account can't touch them, and Paradox won't touch theirs. Running Kairos on the same account? Each algo keeps its own tag.
• Multiple NT accounts from one alert — comma-separated account names.
• Tradovate through CrossTrade (beta): already on CrossTrade with a Tradovate account? Set the new Destination setting to Tradovate and orders route through CrossTrade's cloud — no desktop software, bracket included. ATM templates remain NinjaTrader-only (auto-fallback to the fixed bracket on Tradovate).

Rithmic accounts now work on PickMyTrade

• On a Rithmic-based account (used by many prop firms)? Select PickMyTrade and type your Rithmic connection name into the new field — exactly as it appears in your PMT dashboard. Full bracket, adaptive trailing stop, and multi-account all carry natively. On Tradovate? Leave the field blank — nothing changes for you.

TradersPost, verified end to end

• The trailing stop is confirmed working exactly as designed — it trails from entry at your full stop distance, broker-side. It's a simpler trail than the chart's adaptive one, so live trail exits won't mirror the backtest tick for tick. That's expected behavior, now clearly documented in the tooltips.
• Two TradersPost-side settings worth checking today: keep the "Use signal take profit / stop loss" boxes CHECKED (unchecked = your brackets get silently ignored), and near contract rollover use the exact contract symbol (like MNQZ2026) — TradersPost switches front-month on its own schedule, which can differ from TradingView's.

Settings you can actually read

• The webhook panel is now five clear sections — one Setup section everyone fills, then one per provider. Fields grey out unless their provider is selected, and every tooltip was rewritten in plain English to lead with what to do.
• Small safety upgrades: the Setup-Health 24-hour/overnight-window warning now covers all three session windows (it previously watched only your main Active Hours), and credential fields are editable for CrossTrade and Custom Template setups (previously PickMyTrade-only).

Which provider do I pick?

The alert is the same for every provider: Condition = Any alert() function call → Message box empty → paste your provider's webhook URL in the Notifications tab. Change any setting later? Delete and re-create the alert. Full setup walkthrough →

Previous release — v7.3 (flexibility & safety update)

• TradersPost became built in. Native Webhook Provider — the strategy builds the complete bracketed order (market entry + take-profit + stop; stop-limit and trailing supported). URL-authenticated, so Auth Token / Account ID grey out.
• PickMyTrade multi-account. Comma-separated Account IDs — a single alert fires all of them (e.g. an eval and a funded account together).
• QuantLynk retired. If you were on it, flatten any open QuantLynk-managed position and migrate to TradersPost or PickMyTrade; your selection resets to PickMyTrade.
• Up to three trading windows. Main hours plus an overnight or Asia block — each closed out flat at its own window end. Windows 2 and 3 are opt-in and off by default, sharing one timezone and weekday filter.
• Trailing-stop master switch. One toggle for the trail: on (default) for the usual behavior, off for a clean take-profit / stop bracket when you want live fills to track the backtest as tightly as possible.

Setup-Health — the dashboard warns you before a mistake costs money

The on-chart Setup-Health readout (introduced in v7.3, extended in v7.4) flags the configuration mistakes that quietly cost money:

• Wrong chart timeframe for the algo
• Contract size that looks heavy for your drawdown room
• A 24-hour / overnight window on any enabled session (v7.4 — previously main Active Hours only)
• A preset silently overriding your edited inputs — the #1 "why won't my settings apply" question, now answered on-screen
• Missing webhook credentials for your selected provider

Risk controls (since v7.3)

• The loss-streak breaker counts only real losses. The consecutive-loss circuit breaker and its cooldown count only bracket losses — actual target, stop, or trailing exits. Forced time/session exits don't trip them.
• Risk-counter hardening. The pacing and loss counters can no longer stall new entries in unusual configurations (24/7 sessions, a midnight reset hour, or the multi-day guard).
• Carried over from v7.2: the loss breaker still resets each session (it can't lock you out across days), and the Daily Loss Cap still tracks live floating P&L, so it can trip before a position closes — matching how prop firms evaluate accounts.

Default settings (unchanged since v7.2 · optimized for MNQ 3-minute)

v7.3 and v7.4 change no defaults — these are unchanged from v7.2 and apply to new chart loads only; existing users keep their saved settings. The Setup Recipes still recommend their own values where a specific goal calls for it (e.g. prop-firm caps with a safety buffer).

Setup & clarity

• Tooltips rewritten and expanded, including honest setup guidance for third-party webhook routes.
• Same alert setup for every built-in provider (PickMyTrade, TradersPost, CrossTrade, Custom Template): set the TradingView alert Condition to Any alert() function call, leave the Message box empty, and paste your provider's webhook URL in the Notifications tab — the strategy supplies the full payload. PickMyTrade, CrossTrade, and Custom Template need their credential fields filled first; TradersPost is URL-authenticated, so those fields grey out. Full walkthrough →
• Reminder: a blank credential field is the most common cause of alerts never reaching your broker. Enter credentials in the strategy inputs first, every time.

Carried over from v7.2 and earlier: zero-repaint confirmed-bar execution, per-timeframe regime-flip exits, the adaptive volatility trailing stop, the floating-P&L prop-firm engine, single-alert bracket delivery, persistent exit + cancel-all on reconnect, the MNQ-3-minute default set, and the grouped input panel.

#Kairos Scalper v1.5.

• CrossTrade is now built in (NinjaTrader 8). Fixed bracket mode (target + stop held at NinjaTrader at the chart's exact prices) or ATM mode (your saved NinjaTrader ATM template runs stop, target, and a tick-level auto-trail broker-side). Exit Mirror keeps NinjaTrader in sync with chart exits; automatic strategy tagging keeps Kairos's trades isolated from other bots on the same account — including Paradox Algo. Multi-account via comma-separated NT names, plus a beta Tradovate destination through CrossTrade's cloud. ATM tip: Kairos's bracket adapts to the market, so for an exact template match, turn on Use Manual Brackets and copy those fixed values into your ATM. Your Contracts setting must match the template's contract count.
• Rithmic accounts on PickMyTrade. Type your Rithmic connection name into the new field — exactly as it appears in your PMT dashboard. Full bracket, adaptive trailing stop, and multi-account carry natively. Tradovate users: leave it blank.
• PickMyTrade multi-account. Comma-separated account IDs trade from a single alert — works on Tradovate and Rithmic.
• Custom Template "Flatten Word." Set the exact close keyword your provider expects (default unchanged).
• Settings you can actually read. The webhook panel is now five clear sections with provider-aware field greying, every tooltip rewritten in plain English — and the dashboard has a new Webhook row showing your active route, with a warning if a key or account field is still blank.
• One field that's supposed to stay lit: "PMT — Trail Enable" also serves TradersPost (it's the broker-trail on/off switch for both), so it stays active when TradersPost is selected. Not a bug — it's your trail toggle there too.

Carried over from v1.3 / v1.4

• Ships pre-tuned. Profile defaults to Custom with our optimized configuration active out of the box — no setup needed beyond the broker connection. Conservative / Balanced / Aggressive remain as opt-in presets.
• Profile lock, made visible. The dashboard shows "preset locked" vs "CUSTOM" — custom input values only take effect on the Custom profile (or with Advanced Tuning enabled).
• Direction-aware entries. Waits for pullbacks instead of chasing extended price.
• Smarter confluence scoring. Scoring requires agreement across independent signal dimensions — the Confluence Gate is a true selectivity control.
• Wick Sensitivity (Advanced Engine): filters noisy wick signals.
• Session settings rebuilt — the old session string is gone (see below).
• PickMyTrade entries are explicit market orders (order_type: MKT) — no action needed on your side; this eliminates limit-order ambiguity at entry.
• Loss Circuit Breaker, clarified: when it trips, it halts new entries for the remainder of the day and resets at the next session (or on a win).

The input panel at a glance

Open the strategy's settings (gear icon on the chart) and you'll move through these groups top to bottom — everything in this section lives in one of them:

• Profile — the preset selector. Ships on Custom with the optimized configuration already active; switch to Conservative / Balanced / Aggressive only if you deliberately want a preset driving instead.
• Session — Active Hours, Session Timezone, and the Weekday Filter with its Mon–Sun checkboxes (detailed below).
• Risk controls — Daily Risk Limit, Daily Profit Target, Loss Circuit Breaker, Recovery Period, and the prop-firm compliance fields (daily reset hour, trailing drawdown, force-close).
• 🔗 Webhook & Broker — five sections as of v1.5: one Setup section everyone fills (the Webhook Provider dropdown: PickMyTrade / TradersPost / CrossTrade / Custom Template), then one section per provider. Fields grey out unless their provider is selected.
• Advanced Engine — power-user tuning, including the new Wick Sensitivity control: raise it to filter out noisier wick-driven signals, lower it to let more through. Inputs here (and any custom values) only take effect on the Custom profile or with Advanced Tuning enabled.

The on-chart dashboard is your live status readout. Alongside the session and P&L state, it always shows which configuration is actually driving: "preset locked" means a preset is in control and your manual inputs are ignored; "CUSTOM" means your own input values are live. If you ever change an input and nothing happens — check this readout first; you're almost certainly on a locked preset.

Providers — what changed and why

Kairos v1.5's Webhook Provider dropdown has four options: PickMyTrade, TradersPost, CrossTrade, and Custom Template — the same four offered by Paradox Algo v7.4. Same webhook system, both algos.

• CrossTrade — added in v1.5. Earlier versions skipped it because its webhook couldn't carry a per-trade trail; ATM mode solves that by letting your saved NinjaTrader template run the trail broker-side. Fixed-bracket mode is also available when you'd rather have exact chart prices with no trail.
• QuantLynk — removed. Its webhook can't carry stop / target / trailing data, and Kairos's exits live in broker-side brackets delivered at entry. Routed through QuantLynk, positions would sit unprotected at the broker and desync from the strategy. (QuantLynk is retired across the entire Paradox Algo lineup — migrate to a supported provider.)
• Generic (Universal) — removed. It was redundant with Custom Template.

Custom Template users: keep the {token} / {account} placeholders in the template itself and put your real credentials in the Auth Token and Account ID input fields — don't hardcode credentials into the template. The placeholder list now also includes {trail_enable}, {trail_offset}, and {trail_act}, and {sl_type} can resolve to trailing_stop.

Session settings — fully rebuilt

The old session string (e.g. 0800-1200:23456) is gone, replaced by a proper UI in the Session group of the input panel. Top to bottom, here's exactly what you'll find and what each control does:

• Active Hours — a start-time and end-time pair defining your trading window (e.g. 08:30 → 11:30). The strategy only opens new positions inside this window; outside it, signals are ignored.
• Session Timezone — a dropdown with six options: New York, Chicago, London, Tokyo, Sydney, UTC. Your Active Hours are interpreted in this timezone — not your chart's timezone and not your computer's. Set it once to your market's home exchange and your window stays correct year-round, DST included.
• Enable Weekday Filter — a toggle. Switched ON, the Mon–Sun checkboxes below it become active and the strategy only trades on checked days. Switched OFF, every day of the week is eligible.
• Mon–Sun checkboxes — one per day. The typical futures setup checks Mon–Fri and leaves Sat/Sun unchecked.

• 24/7 markets (crypto): check Sat + Sun and turn the weekday filter OFF — or set Active Hours to 00:00–23:59.
• Daily counters follow your timezone. Daily P&L, the trade limit, and the circuit breaker all reset at the selected timezone's day boundary — not your chart's.

Alert setup is unchanged: Condition = your strategy + Any alert() function call, Message box empty, fires once per bar close. Backtest disclaimers also unchanged — use a fixed-month contract for reproducible backtests.

#What To Expect Live.

A few things differ between the Strategy Tester and live execution — all of them normal. Knowing them up front prevents the usual "this is repainting / the script is broken" confusion.

• Fires on confirmed bar close. Signals are only emitted when a bar closes — never intra-bar. This is exactly what makes the strategy non-repaint: backtest and live both act on the same confirmed bar, so the report matches reality.
• Timestamps: bar-open label, bar-close fill. TradingView labels each trade by the bar's open time, but the fill happens at the bar close. A trade stamped 9:30 on a 3-min chart actually filled at that bar's close (~9:33). Your broker's fill log is the source of truth for the real fill time — not the TradingView label.
• Webhook latency is normal. Expect sub-second to a few seconds from bar close to broker fill, sometimes longer under heavy load. That's the nature of TradingView → bridge → broker, not a malfunction.
• Bar vs tick — they will differ. The backtest simulates the trailing stop on bar data; your broker runs it tick by tick. So live and backtest exits won't be identical — and the gap is largest with tight trails, which a single tick can trigger but a bar can't represent. Widen the trail if you want them to track closely.
• Use Bar Magnifier for a realistic backtest. In the strategy's Properties tab, enable Bar Magnifier — it backtests intrabar using lower-timeframe data and models the trail far more realistically. Note: Bar Magnifier requires TradingView Premium or higher.

#Tuning The Engines.

Each algo's input panel surfaces the specific options available for that engine, organized into clear groups (Confluence Engine, Order Execution & Risk, Risk Controls, Prop Firm Settings, Webhook & Broker, Session, Display). Most users only need to touch the preset profiles (Conservative / Balanced / Aggressive) to get a working configuration — Custom mode unlocks every advanced input for power users.

Prop Firm Compliance

• Daily Loss Cap: hard ceiling on daily loss before new entries are blocked. Set it to your firm's daily loss rule (minus a safety buffer). The cap includes open (floating) P&L, so it can trip before a position closes — the moment your unrealized loss reaches the cap, not just on a realized loss.
• Loss Circuit Breaker: halts new entries after N consecutive losses, then resets each session — it can't lock you out permanently across days. v7.3: the breaker and its cooldown count only bracket losses (real target / stop / trailing exits) — forced time or session exits no longer trip them, so entry pacing around those can differ slightly from v7.2.
• Daily Profit Cap: optional ceiling that auto-flattens once your daily profit target is hit.
• Multi-Day Loss Guard (trailing drawdown): tracks high-water-mark equity over a rolling window and blocks entries if the peak-to-current drop breaches the cap. Enable it for any firm with a trailing drawdown rule (most of them).
• Daily Reset Hour: the hour (in NY time) your daily P&L counter resets to zero. Match it to your firm's reset window — most CME-aligned firms use 18 (6 PM ET, the futures session open). Topstep, Apex, and Tradeify can differ, so check your firm's rule sheet.
• How to match your firm: set Daily Loss Cap and Multi-Day Loss Cap to your firm's actual dollar limits minus a 15–20% buffer, set the Daily Reset Hour to their reset time, and set Force Close to their end-of-day rule. Then the strategy enforces the rules before the firm's bridge ever has to.
• Session-based Trade Limits: max trades per session and per day, with minimum spacing between entries.

Risk Brackets (TP1 / TP2 / TP3 / SL / EP / Trail)

• Three-Tier Take-Profit (TP1 / TP2 / TP3): the strategy supports up to three partial scale-outs per trade. Configure each TP distance independently for both Long and Short side. Position size is split across the three legs based on your weighting.
• Stop-Loss (SL): hard ceiling on per-trade loss. Required input.
• Entry Placement (EP): offset from the signal price. Use a small positive offset to require price confirmation past the trigger before filling.
• Adaptive (recommended): TP, SL, and trail distances scale with live volatility. Risk stays proportional to conditions.
• Fixed: manual mode for deterministic stop sizes. Pick one format (% · Ticks · Points · Pips) and stay consistent across SL and all TP legs.
• Adaptive Position Exit (Trailing Stop): the adaptive trailing logic ratchets behind price using a volatility-derived buffer. Activates after TP1 by default. Recommended for trends. v7.3: a master trailing-stop toggle turns it on or off in one place — leave it on for the usual behavior, or switch it off for a clean take-profit / stop bracket (handy for mean-reverting setups, or to make live fills track the backtest as tightly as possible).
• Golden Rule: never set SL wider than TP1.
• Move SL to Entry After TP1: eliminates risk on the remaining position. Strongly recommended.

Manual Brackets & the Trail (read before you touch them)

• How Manual Brackets work (mix & match). When Manual Brackets is enabled, each manual field overrides the adaptive value only if it is greater than 0. Any field left at 0 keeps using the adaptive value. So you can set a fixed Manual SL and Manual TP while leaving the trail at 0 to stay adaptive — every component is independent.
• Tight trails exit you in seconds. A small trail distance on a fast instrument scalps you out almost instantly — a 1–10 tick trail on MNQ gets hit by normal noise within seconds of entry. Recommended starting range: 40–60 ticks on MNQ (scale up for ES / NQ). If trades keep closing the instant they open, the trail is too tight — widen it.
• Adaptive vs Manual — when to use each. Adaptive (the default) scales TP / SL / trail with live volatility, so risk stays proportional across regimes — best for most users, most of the time. Manual is for deterministic fixed bracket sizes — a prop firm requiring exact stops, or testing a specific fixed-tick configuration. Unsure? Stay Adaptive.

Trade Pacing & Cooldowns

• Cooldown Period: blocks new entries for N minutes after a position exits. Prevents revenge trading.
• Consecutive-Loss Circuit Breaker: auto-blocks new entries after N losses in a row. Forces a pause. Resets at the start of each session, so it can't lock you out permanently. v7.3: counts only bracket losses (target / stop / trail) — forced time/session exits don't trip it or its cooldown.
• Max Hold Time: auto-flattens any position open longer than your specified threshold. Useful for scalpers.
• Start with Max Trades = 1 until your discipline is proven and your results are consistent. Scale up only after that bar is met.

Session & Time Filtering

• Multiple sessions (v7.3): run up to three trading windows — your main hours plus, say, an overnight or Asia block. Windows 2 and 3 are opt-in and off by default, share one timezone and weekday filter, and each closes flat at its own window end. A single session behaves exactly as before.
• Time Zone: set UTC offset for your locale (e.g. UTC−5 for ET).
• Force Close: Don't Force · Day Close · Session Close · Custom Time. Required for funded-account end-of-day rules.
• Session Filter: NY · London · Tokyo · Sydney presets, plus custom HHMM-HHMM windows.
• Day-of-Week Filter: Mon–Fri toggles — disable holidays and low-liquidity days.

#The Core Rule.

• Example. Prop account max drawdown = $4,000. Daily risk limit = 10% × $4,000 = $400. That is your total allowable loss across every trade that day.
• Position sizing (NQ, the big E-mini). Stop = 20 ticks × $5/tick = $100 risk per contract. Daily limit $400 ÷ $100 = 4 contracts max. For a second trade: verify combined risk ≤ $400 or reduce size.
• Position sizing (MNQ, the micro). Stop = 20 ticks × $0.50/tick = $10 risk per contract. Daily limit $400 ÷ $10 = 40 contracts max. Micros let you scale granularly while you build live conviction.
• Tactical stops use indicator context — SignalWave reversals, EdgeFlow threshold crossings — for short-term placement.
• Structural stops sit at QuantumFlow order-block invalidation levels.
• Stop distance balance: too tight = stop-outs; too wide = violates position sizing.

Tick Value Cheat Sheet

Use this to size positions accurately on the most popular CME futures. Tick math is the #1 source of "I sized this wrong" mistakes in live trading. Bookmark this section.

MNQ vs NQ & symbol mapping

• Symbol mapping. The strategy's Broker Symbol input (e.g. MNQ1!) maps to the front-month contract on the broker side — for example MNQM6. MNQ1! is TradingView's continuous front-month alias; your broker fills the actual dated contract. Make sure the front month your broker resolves to is the one you intend to trade (watch for roll periods near expiration).
• Sizing math. Daily risk ÷ (stop in ticks × $/tick) = max contracts. Example, MNQ with a $400 daily cap and a 20-tick stop: 20 × $0.50 = $10/contract → $400 ÷ $10 = 40 MNQ max. The same stop on NQ: 20 × $5 = $100/contract → 4 NQ max. Size to your account, not to the chart.

Pre-Trade Checklist

• Does this trade fit within my daily risk cap?
• Will my stop-loss maintain acceptable per-trade risk?
• Am I using structural or tactical indicator context for stop placement?
• Have I tracked cumulative risk across the day?
• Is my prop-firm trailing drawdown still safe after this trade?

If any answer is "No" — do not trade.

#Live Execution Setup.

This is where almost every setup ticket comes from — and the fix is nearly always the same one step. Read the non-negotiable item first, then follow the exact setup for your provider. Bracket prices are computed on the strategy side and embedded in every alert, so there's nothing to parse on the bridge.

How signals flow from chart to broker

Alert condition — by provider

v7.4 ships four built-in providers in the Webhook Provider dropdown: PickMyTrade, TradersPost, CrossTrade, and Custom Template. All four use the same alert Condition — Any alert() function call with an empty Message box:

Per-provider field mapping

What goes in the strategy's Auth Token / API Key and Account ID inputs, by provider:

*TradersPost authenticates through your webhook URL, so the Auth Token and Account ID fields stay blank — they grey out automatically. Paradox builds the full bracket (market entry + take-profit + stop / stop-limit / trailing) into the payload it sends, so the position is protected broker-side.

Provider setup

Not sure which one? Tradovate account (most prop firms) → PickMyTrade. Rithmic account → PickMyTrade + your Rithmic connection name. NinjaTrader 8 → CrossTrade. Already on CrossTrade with Tradovate → CrossTrade with Destination = Tradovate. Anything else → TradersPost or Custom Template.

Where the webhook URL goes

In the TradingView alert dialog, open the Notifications tab → enable Webhook URL → paste your provider's endpoint there. Do not paste it in the Message box (that box is for the payload, which the strategy fills for the built-in providers). For PickMyTrade, copy the endpoint from your strategy detail page in PMT — it's the api.pickmytrade.io/v2/add-trade-data-latest address (or the .trade variant for Tradovate-only accounts).

TradingView plan requirements

Creating the alert — step by step

For the four built-in providers (PickMyTrade, TradersPost, CrossTrade, Custom Template), this is the whole flow. The Condition is Any alert() function call and the Message stays empty — the strategy supplies the payload, bracket prices and all.

1. Open a chart with the Paradox strategy loaded — not just the indicators. Strategies fire alerts on entries/exits; indicators only fire on visual conditions you wire up manually.
2. Make sure Auth Token / API Key and Account ID are both filled in the strategy's Webhook & Broker inputs (see the non-negotiable note at the top). Skip this and the order goes out with empty credentials.
3. Click the Alerts button (bell icon) in TradingView, then Create Alert.
4. In the Condition dropdown (first field), select the strategy's exact name — e.g. Paradox Algo Strategy v7.4 or Kairos Scalper [ParadoxAlgo], matching what appears in your Indicators → Invite-Only Scripts list.
5. In the second field, select Any alert() function call. (All four built-in providers use this. Only the legacy TradersPost order-fills path differs — see the TradersPost sections above.)
6. Open the Notifications tab, enable Webhook URL, and paste your provider's endpoint there.
7. Leave the Message field empty — the strategy injects its own JSON payload via alert() with bracket prices, ticker, and direction already filled in. Do not paste a template here (that's only for the TradersPost order-fills path).
8. Set the alert Expiration to Open-ended (Premium/Ultimate) or the longest available on your plan. Re-create when it expires.
9. Click Create. Verify the alert appears in the Alerts panel with a green dot (active).
10. Test once in your provider's paper/sandbox mode before going live. Use RequestBin or Webhook.site to inspect the raw payload if anything looks off.

#The Three-Gate Promotion Ladder.

Do not skip gates. Every gate exists because someone before you blew up by skipping it. Each step's pass criteria is concrete and measurable — there's nothing to interpret.

#Common Issues.

Webhook chain of custody — debug in order

When a webhook trade doesn't show up at your broker, the problem is in one of five places. Check each in order until you find the break.

Common-Issue FAQ

#Ten Rules To Live By.

1. Start with a preset profile (Conservative / Balanced / Aggressive). Adjust incrementally only after you've run at least 30 sessions on the baseline.
2. Use adaptive (volatility-scaled) brackets over fixed-tick brackets unless your prop firm specifically requires fixed sizes.
3. Set your Active Hours filter to a high-liquidity 3-6 hour window — never trade through low-liquidity overnight or holiday sessions.
4. Set Daily Loss Cap to your firm's actual rule minus a 15-20% safety buffer. Never push the firm's rule to the wire.
5. Enable Multi-Day Loss Guard for any prop firm with a trailing drawdown (Apex, Topstep — most do).
6. Verify the Daily Reset Hour matches your firm's reset window. Most CME-aligned firms use 18 (6pm NY).
7. Begin with Max Trades / Day = 1-2 until you have 30+ profitable sessions, then raise incrementally.
8. Trust the Recovery Period and Loss Circuit Breaker — when they halt you, the regime is bad. Re-entering immediately is how accounts die.
9. Never override a signal manually mid-session. If you don't trust the strategy enough to leave it alone, you're not ready to be live.
10. Follow the Three-Gate Ladder — Backtest → Paper → Live (1-unit) → Live (full). Every blown account skipped a gate.

#First Trade Walkthrough.

A concrete sequence for going from "just got access" to "first paper trade" in under 15 minutes.

1. Pick one instrument. Recommended for first session: MNQ1! (Micro Nasdaq). High liquidity, low contract size, prop-firm friendly. For chart timeframe, the simplest path is to import a preconfigured layout from Discord (see Shared Layouts) — otherwise pick a timeframe you've validated in the Strategy Tester.
2. Load Paradox Algo from Invite-Only Scripts. Click Indicators → Invite-Only Scripts → pick Paradox Algo Strategy v7.4. The strategy will load and run a backtest immediately.
3. Open the input panel. Click the gear icon next to the strategy name. Inputs are grouped by function: Entries, Exits, Risk, Compliance, Sessions.
4. Apply a preset. Under Risk, set the preset to Balanced. This auto-configures TP1/TP2/TP3, SL, EP, trailing logic, and pacing for the timeframe you're on.
5. Enable prop-firm compliance (if applicable). Set Daily Loss Cap, Trailing Drawdown, and Daily Reset Hour to your firm's actual rules. Set Force Close to Session Close.
6. Read the Strategy Tester report. Bottom panel of the chart. Check Profit Factor, Max Drawdown, Total Trades, and Equity Curve. If any of these look wrong for your account, change the preset or instrument before going live.
7. Set up an alert. Click the bell icon, select the strategy in Condition, then pick Any alert() function call from the second dropdown. Paste your webhook URL and leave the Message field empty — the strategy fills it automatically.
8. Paper-trade for one full week minimum. Track every trade. Compare alert payloads to actual fills. Do not skip this step.

#Understanding the PMT Payload.

If you inspect the JSON PickMyTrade receives, a few fields won't match the Pine script — and that's correct. Here's what the strategy sends versus what PMT adds on its own side, so you can tell a real issue from a non-issue.

What the strategy sends vs what PMT adds

The strategy emits a compact payload. PickMyTrade then adds its own internal fields on its side before routing to the broker — these are not from the Pine script, and seeing them does not mean the script is broken:

tp and sl showing 0 is correct

If you see tp: 0 and sl: 0 in the payload, that's intentional — the bracket is sent the other way. There are two methods:

• Absolute-price method: tp / sl would carry exact prices. The strategy does not use this path for PMT — hence the zeros.
• Distance method (what's used): the bracket is sent via dollar_tp and dollar_sl — the distance from entry in points. PMT builds the bracket as entry ± that distance. So tp: 0 / sl: 0 alongside non-zero dollar_tp / dollar_sl is exactly right.

Order type

Entries are market orders — confirmed in live testing. The strategy enters at market on the confirmed signal, and PMT attaches the bracket (from dollar_tp / dollar_sl) on the broker side.

#Glossary & Acronyms.

#Support Channels.

#Trade At Your Own Risk.

Paradox Algo and affiliated parties are not registered financial advisors. The tools provided are for educational purposes only and do not constitute financial advice. You must understand the risks involved and accept any level of loss. Past performance does not guarantee future results. You assume full responsibility for all trading outcomes.