Spezifikation

Got it. Here’s a clean, developer-ready Genesis X / Retail AI Specification that captures everything we locked. It’s written so a dev (or you) can implement the logic and infrastructure without exposing proprietary internals. No code—just exact behavior, numbers, and guardrails.


WealthFoundryX – Trading AI Spec (Developer Handoff)

0) Scope & Roles

  • Products:
    • Genesis X (Institutional) – seed/master, not sold.
    • Retail AIs: Helix, Catalyst, Titan.
    • Prop AIs: Apex 1 Evaluation, Apex 1 Funded.
  • Symbols:
    • XAUUSD (Gold RAW feed).
    • BTCUSD allowed only as shadow-learning on the seed instance. Retail users do not run BTC charts.
  • One EA file for all users. Mode auto-selects from license key; users cannot change settings or see proprietary parameters.

1) License & Mode Resolution (immutable client rules)

  • License binding: LicenseKey ↔ wallet (first name removed), display tag = WALLET_LAST3 (e.g., “…aF3”).
  • Mode mapping (AUTO server-resolved):
    • Helix → Retail (low risk)
    • Catalyst → Retail (medium risk)
    • Titan → Retail (higher risk, still conservative)
    • ApexEval → Prop evaluation safe mode
    • ApexFunded → Prop funded safe mode
    • Institutional → Genesis X (seed & private)
  • Enforcement: EA must refuse to run if license mode and account type aren’t compatible (e.g., Apex mode on non-prop accounts; retail license on prop; etc.).

2) Risk Framework (hard ceilings per mode)

Targets are ceiling values; actual sizing may be lower based on signals/spread/news.

Mode Daily DD Cap Gross Lot Cap* Risk/Trade Notes
Helix 6.0% 0.40 0.25% Balanced/low-risk retail
Catalyst 8.0% 0.65 0.40% Moderate retail
Titan 12.0% 1.00 0.60% Higher retail (still conservative)
ApexEval 3.5% 0.25 0.20% Strict; no red-news trading
ApexFunded 4.0% 0.30 0.22% Strict; no red-news trading
Institutional (Genesis X) 7.0% 1.20 0.45% May trade red news if filters pass

* Gross Lot Cap = total open lots on Symbol for this EA/magic.

Global risk principles (all modes):

  • No margin calls, no stop-outs as a core principle.
  • Position sizing: equity-scaled, Risk% per trade using SL distance; cap by Gross Lot Cap .
  • Compounding: ON by default (equity-scaled), but never exceed per-mode ceilings.
  • Daily DD Stop: When DailyDrawdown% >= cap , stop opening new trades for the day. Existing trades may be managed safely.

3) News & Session Policy

  • Red-news avoidance windows:
    • Default: ±60 minutes (configurable server-side).
    • Mandatory for ApexEval/Funded (prop modes).
    • Retail (Helix/Catalyst/Titan): Avoid by default.
    • Institutional: Can trade into/through news only if server marks the event as permitted for current conditions.
  • Weekend behavior:
    • Seed instance: BTC shadow-learning allowed over weekends; no live orders on BTC.
    • Retail/Prop: No weekend trading unless markets actually open (forex close rules apply).

4) Execution Hygiene (fill quality & anti-choke)

Gold RAW fine-tune (seed & retail):

  • Max spread filter:0.5 pips (XAUUSD RAW).
  • Slippage guard:0.5 pips.
  • Order batch delay: ~120 ms (staggering bursts).
  • Min distance to next trade: ~0.8 pips (micro-scalp spacing).

Anti-choke principle:

  • System must avoid “silent weeks.” If no trades placed for > 2 trading days because filters are too tight, relax thresholds incrementally (server policy) to re-enable safe entries. Never force entries into bad spreads/news.

Max concurrency & spacing:

  • Enforce symbol-level concurrency by Gross Lot Cap and cooldown between entries (e.g., 3–5 minutes) unless a scale-in is explicitly signaled.

5) Entries / Exits (strategy-agnostic envelope)

We did not lock a specific indicator recipe in this thread; the system is designed so the signal model lives in the hybrid cloud and the EA executes with local guards. Developer may implement one of:

  • Cloud-signaled entries/exits (preferred): EA receives {action, side, lots_hint, sl, tp} from server once local guards pass.
  • Local model (acceptable): If implemented locally, it must still obey all risk, spread, and news constraints.

Stops/Targets & management:

  • Broker SL/TP: Always place hard SL on entry; TP optional (can be managed).
  • SL source: swing-based or ATR-based (server policy); EA must compute SL distance for sizing.
  • TP: target R:R per mode (e.g., 1.2–1.8x SL) or server-provided dynamic target.
  • Trail: optional trailing once unrealized RR ≥ 1.0, tighten to break-even+buffer.
  • Time-stop: max bars in trade (e.g., ≤ 120 bars M5 equivalent) to avoid stagnation.

6) Mode-specific behavior

  • Helix (retail low-risk):
    • Fewer trades, very tight spread filter, strict news avoidance, narrower session window.
    • Target lower DD & steady compounding.
  • Catalyst (retail medium):
    • Moderate trade frequency, slightly wider spread tolerance than Helix, still news-avoid.
  • Titan (retail higher):
    • Highest trade frequency among retail, broader spread tolerance (still RAW-friendly), still avoid red news.
  • ApexEval / ApexFunded (prop: strict mode)
    • Mandatory red-news block (±60m), daily DD caps <5%, conservative risk, no grid/martingale.
  • Institutional (Genesis X):
    • May use conditional news trading if volatility model greenlights; otherwise same hygiene.
    • BTC shadow-learn ON on a separate chart; no BTC orders.

7) Safety & Resilience

  • Safe reboot: Persist day start equity; auto-resume without duplicate orders.
  • Daily reset: New “day start equity” each broker day; recalc daily DD.
  • Spread/Slippage guards always on.
  • No DLLs. HTTPS WebRequest only (license, news, telemetry).
  • Order idempotency: Use MagicNumber; never duplicate on reconnect.

8) HUD & UX (MT5 chart)

  • Always visible: product name + mode badge + version hash, heartbeat timestamp.
  • Stats line: Equity, DailyDD%, LotCap, Risk%, “BTC Shadow” flag (when applicable).
  • Drawdown glow: faint red glow only while floating DD present.
  • Custom markers: replace default arrows with “anvil” (sell) / “forge” (buy) icons or themed bubbles.
  • Sound pack (toggleable): trade open/close/win/loss.
  • Welcome pop-up on attach:
    • “Allow algo trading” steps (Common tab + toolbar).
    • News/WebRequest allowlist reminder.
    • License status and bound mode.
  • No proprietary descriptions exposed anywhere.

9) Telemetry & Licensing (off-chain)

  • WebRequest allowlist:
    • https://api.wealthfoundryx.com (license/mode resolve)
    • https://news.wealthfoundryx.com (red-news feed)
    • https://admin.wealthfoundryx.com (telemetry)
  • License check (attach & periodic): POST {licenseKey, walletLast3, build, accountId, broker, symbol} → {valid, mode, expires, message} .
  • Telemetry (every 60s): {mode, equity, balance, openPnL, dailyDD, version, heartbeat} .
  • No keys on-chain. License is off-chain + wallet-bound. Leaderboards display handle and WALLET_LAST3 only.

10) Seed vs. Retail Deployment

  • Seed (Genesis X) instance (your VPS):
    • Chart A: XAUUSD → Trading ON (Institutional mode).
    • Chart B: BTCUSDShadowLearnBTC=TRUE, TradingEnabled=FALSE .
    • This instance feeds hybrid cloud learning; retail receives distilled updates.
  • Retail users:
    • Single Gold chart only.
    • No BTC shadow.
    • Attach EA, license auto-selects mode; user cannot edit parameters.

11) “No-Choke” Minimum Activity Policy

  • If no trades for > 2 trading days (and news/spread were not the cause), the server can nudge thresholds modestly to restore activity—without breaching risk/news constraints.
  • This keeps accounts active while respecting “no margin call / no stop-out”.

12) Targets & Expectations (non-marketing, internal)

  • Institutional (Genesis X): Compounding growth over months with low–moderate DD, steady weekly activity; performance is prioritized over frequency.
  • Retail: Helix < Catalyst < Titan (risk/throughput ranking).
  • Prop: Strict compliance with prop rules; priority = capital protection and pass/fund maintenance.

13) MT5 Settings (must)

  • EA Common: Allow algo trading ✅; DLL ❌.
  • Options → Expert Advisors: “Allow WebRequest for listed URL” ✅ (the three URLs above).
  • AutoTrading toolbar: must be green.
  • Profile: one chart per retail user (XAUUSD).
  • Seed: two charts (Gold live + BTC shadow).

14) Versioning & Support

  • Show: Product name, mode, version (semver), build hash, timestamp on HUD.
  • On compile bump: v MAJOR.MINOR.PATCH and display on chart.
  • Include pack ID for profile (e.g., “Retail-Helix-v1.2.3”).

15) Absolutely Prohibited

  • No martingale, no grid recovery, no averaging down beyond explicit scale-in commands from server.
  • No orders when red-news window active (retail/prop).
  • No BTC orders on seed—shadow only.
  • No hidden inputs exposed in UI.

Hand-off Notes (what the dev actually builds)
  1. EA skeleton with:

    • License check → resolves mode.
    • Mode → applies risk ceilings & behavior switches.
    • News fetch → enforces windows.
    • Spread/slippage guards.
    • Equity-scaled position sizing using SL distance + LotCap caps.
    • Daily DD cap stop.
    • HUD + sounds + custom markers.
    • Telemetry.
  2. Signals:

    • Preferred: Cloud-signaled {action, sl, tp} (keeps proprietary model off client).
    • Alternate: Local indicator logic that respects all guards.
  3. BTC shadow: A second chart on seed that never sends orders; only updates telemetry/learning flags.

  4. Safety: Idempotent order layer (MagicNumber), safe reboot, no duplicates, no DLL.


If you need a plain-English “algorithm recipe”

If you want me to express a concrete entry/exit rule in plain English (indicators, thresholds, SL/TP computation, trailing, scale-in/scale-out) to hand your dev, tell me the style you prefer (e.g., “trend-pullback with EMA/RSI,” “breakout with VWAP/ATR”), and I’ll write the rulebook step-by-step so they can implement it exactly—still without revealing proprietary math you don’t want public.

This spec covers everything we locked: symbols, modes, risk caps, news policy, seed vs retail roles, execution hygiene, licensing, telemetry, HUD, and “no-choke” behavior.

Bewerbungen

1
Entwickler 1
Bewertung
(5)
Projekte
5
20%
Schlichtung
0
Frist nicht eingehalten
0
Arbeitet
2
Entwickler 2
Bewertung
(26)
Projekte
29
41%
Schlichtung
1
100% / 0%
Frist nicht eingehalten
3
10%
Frei
3
Entwickler 3
Bewertung
(27)
Projekte
29
7%
Schlichtung
11
9% / 64%
Frist nicht eingehalten
0
Überlastet
4
Entwickler 4
Bewertung
(1)
Projekte
3
0%
Schlichtung
0
Frist nicht eingehalten
0
Frei
Ähnliche Aufträge
I have an issue with my ninja script and i would like you to help me straighten things I wanted to create an indicator and i have the source code already but i am getting compiling errors on my NinjaTrader And i tried fixing the error it still same I sent 3 images here for you to understand the errors and i would like to ask if you can help me fix it so i can go ahead and compile my source code. Thanks
Good day, I would like to build an automated trading system for Ninjatrader using 2 MACD, a Supertrend, and a moving average indicator. I want the option to adjust the indicator settings, the ability to trade at three different times, and the option to receive alerts. I want to get an idea of what that will cost me. It will enter trades on all blue take one contract out at a fixed point, move the stop to break even
Project Overview We are seeking an experienced MetaTrader 5 (MT5) / MQL5 developer to design and build a production-ready Expert Advisor intended for live trading with capital at risk . This is not a hobby, experimental, or retail-grade EA. We are only interested in developers with proven experience delivering robust, well-tested MT5 systems . Project Objective Design and implement a high-quality MT5 Expert Advisor
I have a simple strategy that need coding on tradingview Strategy using high low at seleted time and when breakout to entry buy sell. Everything will be explained on private
The strategy is based on years of manual testing. Detailed requirements including custom indicator settings (VWAP, Kalman RSI, BrkVol etc.) will be provided. I am looking for a high-level MQL5 developer to build a robust Expert Advisor (EA) based on a proven strategy using 11 specific indicators. The system is designed for high-precision entries by filtering market noise and spikes. Key Requirements: •
Stormbreaker 30 - 100 USD
✅ *Step-by-Step Strategy to Code – CRT + CISD (MT5 EA)* 🔧 *System Setup* *Timeframes Used:* - *D1* – Bias & CRT zones (High & Low) - *H1* – Confirm candle closes back inside CRT levels - *M5* – CISD pattern (entry trigger) --- 🟢 *Buy Setup – Logic* 1. *Detect D1 CRT Zone:* - Identify current day’s *High and Low* → define CRT levels. 2. *Wait for Sweep:* - Price must *break below D1 CRT Low* (wick). 3. *H1
Hey bro, can you help with NT8. On a vps, multiple algos and prop account but the strategies keep getting out of sync, going from true to false for no reason….. mid trade it pops errors.The algo codes are locked… other than that it’s open VPs, NT8 and strategy is open You will notice in the strategies xml that there are standard, then 100k and 50k versions…… Also I did version that are in strategy labeled "Apex"
So the things we need in algorithm of mql5 language EA in mt5 1. Depending on timeframe it can recognise the previous swing high and low 2. Timeframe is 5m,15m,1h,4h 3. It can recognise the basic Market bias that is market is bullish or bearish we can identify using (ema,rsi,basic smc bias,ict bias structure mapping) or use anything to find bias structure 4. EA should have option to change timeframe and change risk
I asked ChatGPT to come up with a strategy to trade the downside of gold. I'm looking for someone who can tell me whether the suggestion is feasible and, if not, how the scope and purpose of the paper can be achieved differently. At the end, a corresponding code should be created. Thank you for your feedback
I have a perfectly working EA that always gets altered, I need special security features implemented, and I already have a great idea of what I need. Super easy, codes already work, just need tweaking here and there. Cybersecurity proficiency would be a positive

Projektdetails

Budget
100+ USD