By HalalCrypto Research Team · Published 2026-04-26 · Updated 2026-04-26
On this page
Deterministic simulation seeded from a 30-day window. NOT live trading data, NOT customer trades. Use it to compare the volatility profile across tiers — same halal screen on every coin in every tier.
Simulated data only. Past simulated returns do not predict future returns. The bot executes spot-only trades on your connected exchange account; performance depends on market conditions, liquidity, and the halal universe in effect at the time.
The system is organised as six cooperating engines, each with a single responsibility. Decoupling responsibilities is what allows us to update one engine without disturbing the others — for example, refining the Signal Engine without touching the Halal Filter — and what makes the Halal Filter's veto authority absolute. These six engines form the shared pipeline every AI agent passes through. The number of specialised AI agents per tier (Conservative 7 · Moderate 13 · Multi-X 20) reflects how many dedicated agents are running simultaneously for your subscription, each with its own signal focus, all passing through this same six-stage control pipeline.
Engine 1
Identifies high-probability setups using rolling volatility, volume profile, structural breakout detection, and a learned classifier trained on multi-year spot data. Outputs candidate trades with a confidence score and a recommended notional size.
Engine 2
Checks every candidate against the four-gate AAOIFI-aligned framework. Rejects any signal on a coin currently failing any gate. The Halal Filter has absolute veto authority — no signal, however high-confidence, proceeds without its approval.
Engine 3
Sizes the surviving signals against current portfolio heat, tier-specific concurrency caps, and rolling 14-day ATR of the candidate coin. Vetoes any trade that would push portfolio heat above its tier's cap. Outputs a final order ticket with size, stop, and target levels.
Engine 4
Cross-checks the order ticket against OFAC, UN, EU, and equivalent sanctions lists in real time; Refreshes daily. Vetoes any order against a sanctioned coin or counterparty. This is a hard regulatory gate as well as a Shariah-aligned one.
Engine 5
Places the spot order against the user's exchange (Binance, Bybit, OKX, or Kraken depending on tier) using the encrypted API key. Registers the stop-loss and take-profit triggers on the exchange. Confirms fill, then notifies the Observability Layer.
Engine 6
Reconciles exchange state with internal state, computes performance metrics, and generates the user-facing dashboard. Surfaces anomalies (stale orders, unexpected balance changes, exchange API errors) to the operations team. Sends weekly summary emails to users.
From candidate setup to closed position:
Total elapsed time from signal emission to order placement is typically under 2 seconds. Total elapsed time from order placement to fill is exchange-dependent (typically under 1 second on Binance for our routing sizes).
Three distinct data domains, each with its own storage and access controls.
We do not share data with marketing partners, analytics providers, or third-party services beyond what is operationally necessary. Sentry-style error logs strip identifiers and never log API keys or trade-specific dollar amounts.
Exchange API keys are the most sensitive data we hold. They are stored in a hardware-backed key vault separate from the application database. Encryption is AES-256-GCM with per-user encryption keys derived from a master HSM key.
The Execution Layer reads a user's key on demand at trade time, decrypts in memory, places the order, and discards the plaintext immediately. The key never appears in logs, never crosses an external service boundary, and never persists in plaintext anywhere on disk.
We additionally require that withdrawal permissions be disabled on the key. With withdrawals off, even a worst-case scenario — full compromise of our infrastructure — cannot result in user funds leaving the exchange. The bot's authority is bounded by the API key's permissions, and those permissions exclude the only operation that could move funds.
Every position has four possible exit conditions, evaluated continuously by the Execution Layer:
All four are registered as orders on the exchange itself, not just in the bot's internal state. That means the exchange enforces them even if our infrastructure goes down — your stop will trigger regardless. Resilience comes from defence in depth, not from any single component.
Halal screening is not a one-time check. The Halal Filter re-evaluates every coin on every trade decision against the latest gate state. Beyond that, three triggers fire event-driven re-screens:
If a coin transitions from pass to fail and you currently hold a position in it, the system suspends new entries immediately and unwinds the existing position in an orderly manner — typically over the next available exit window rather than a forced market dump. You receive an email notification within 24 hours explaining what changed, why the verdict shifted, and what the unwind looked like.
Are my exchange API keys safe?
Keys are encrypted at rest with AES-256-GCM, never logged in plaintext, and never sent to external services. The execution layer reads them on demand from a hardware-backed key vault and discards them after each call. We additionally require that withdrawal permissions be disabled on the key, so even a complete compromise cannot result in funds leaving your account.
How does the bot decide what to trade?
The Signal Engine identifies high-probability setups using rolling volatility, volume profile, and structural breakout detection. The Halal Filter rejects any signal on a coin that fails our four-gate screening. The Risk Engine sizes the surviving signals against current portfolio heat. Whatever passes all three reaches the Execution Layer.
What if the bot loses internet connection?
Existing positions retain their stop-loss and take-profit orders on the exchange, which the exchange enforces independently. The bot will not open new positions during disconnection. When connection restores, the Observability Layer reconciles the state and resumes within a few seconds.
How often are positions re-screened?
Every position is checked against the halal filter on every trade decision. If a coin's screening status changes mid-position (a Gate 1 or Gate 4 failure), the system unwinds the position in an orderly manner regardless of P& L. Customer email goes out within 24 hours.
Where does the data live?
Trade history, performance data, and portfolio state live in our application database (encrypted at rest, region-isolated). API keys live in a separate hardware-backed key vault. Customer-identifying data is segregated from trade execution data and accessed only by the dashboard layer.
Can the bot ever go rogue?
No. The Execution Layer is bounded by tier-specific concurrency caps and per-trade size limits enforced in code. The Halal Filter cannot be bypassed by any signal. The API key permissions exclude derivatives and withdrawals. There is no scenario in which the bot can place a non-halal trade or move funds off the exchange.
Your halal portfolio, always
Screener detects change
Verdict flips: Cleared → Blocked
Bot closes position
Spot-only exit within risk rails
News Watcher confirms
Cross-checks live news signals
User notified
Alert with reason + authority refs
Portfolio stays halal
Exposure removed, audit trail logged
Other cornerstone guides in this series.
Is crypto halal?
The full Shariah picture — riba, gharar, maysir, and how spot trading earns a permissive verdict.
Halal trading strategy
Asymmetric multi-X targeting (3% in 4h, 5% in 1h, pyramid). No scalping, no leverage.
AAOIFI-aligned screening
Our framework follows AAOIFI standards, with Saudi Permanent Committee and leading Saudi Islamic bank guidance.
Why not derivatives, futures, margin
Why every leverage product, perp, and option is structurally excluded from every tier.
Halal crypto vs halal stocks
Where crypto fits next to halal equity portfolios — volatility, liquidity, and screening differences.
Halal crypto vs cash
Inflation, opportunity cost, and the case for putting some halal capital to work.
Multi-X tier — full six-engine pipeline running 20 AI agents at maximum concurrency. $99/month.
Start with Multi-X — $99/mo