Rules-based signal engine
A rotating cycle of XAUUSD and major crypto pairs, driven by defined entry, exit and invalidation rules — not by a promise.
HOLYTRADING AI is a supervised automation workspace for crypto and metals. A rules-based signal engine proposes every move, risk limits approve it, and every order lands in a ledger you can audit — line by line.
The platform
Most bots ask you to trust an opaque strategy. HOLYTRADING AI exposes the parts that matter: what the engine sees, what it is allowed to do, and what happened after it acted.
A rotating cycle of XAUUSD and major crypto pairs, driven by defined entry, exit and invalidation rules — not by a promise.
Position size, per-cycle risk and balance checks are enforced by the system before any order is recorded. Limits are visible, not implied.
Deposits, withdrawals, trades and admin actions produce ledger entries. Filter, export and reconcile without asking support for a screenshot.
BTC and USDT (TRC20 / ERC20) deposit addresses are issued by the administrator. Each transfer is matched to exactly one ledger credit.
Requests reserve funds immediately, then move through review, processing and completion with an on-chain TXID recorded at the end.
Trading and withdrawal access can be switched per account. Every permission change is written to the audit log with actor, time and target.
How it works
The workflow is deliberately boring. Boring is what keeps automation accountable.
Register with a unique account ID, confirm your email and enable two-factor authentication.
Request a deposit address, send BTC or USDT, attach the transaction ID and wait for review.
Once funded, follow the cycle status, open positions and recorded performance from one screen.
Submit a payout request, watch it move through review, and receive the TXID when it completes.
Security and transparency
Money movement is the part of a trading product that deserves the most suspicion. We handle it with explicit states, private proof storage and a permanent paper trail.
“If an action can move money, it must leave a trace.” — the internal rule this build is held to.
Illustrative sample entries from the demo environment.
FAQ
No. The public demo runs on simulated balances stored in your browser. It is a product walkthrough for the interface, permissions and ledger behaviour. Real funding is only enabled after a separate, explicit onboarding.
No. The engine follows predefined rules with a per-cycle risk cap. Targets are risk parameters, not promises. Trading crypto and leveraged metals involves substantial risk, including loss of principal.
Each deposit request is tied to a transaction ID. The administrator verifies the transfer against the request before crediting. A transaction ID can only be used once, which prevents duplicate credits.
The amount is reserved from your available balance immediately. The request moves through review and processing; once the payout is sent, the on-chain TXID is attached and the status becomes completed. If rejected, the reserved amount returns to your balance.
Only you and the administrators. Proof images are served from a private bucket behind access rules, not from a public URL.
Yes. Administrators can disable trading or withdrawals for a specific account. The restriction is visible in the interface, and the change is recorded in the audit log.
Open the demo, fund a simulated balance, run a cycle and inspect the ledger. No card, no real deposit.