Understanding Zhigolds Trading Signals
Zhigolds provides structured Trading Signals and market analysis. A Signal describes a potential market scenario, including direction, Entry Zone, risk levels, and possible targets. It is not an instruction that automatically places a trade.
This guide explains the information Members see, how recorded outcomes become Signal History, and what the Official Signal Ledger can—and cannot—prove.
Public Signals & Member Access
Public previews may show selected Signal information. Registered Members may see more detailed information through the Signals Dashboard, subject to access permissions.
A public preview, Member view, and Broker trading account are separate. Viewing a Signal does not execute a trade.
How to Read a Signal
Start with the instrument (such as XAUUSD or BTCUSD), the BUY or SELL direction, timeframe, Entry Zone, Stop Loss (SL), Take Profit (TP1–TP3), and latest update time.
Read the analyst’s current scenario and its conditions. Entry Hit means a Signal event was recorded; it does not establish that your Broker executed a trade at the same price.
This is not a live Signal or a Trading recommendation.
Market Structure & Trading Analysis
Analysis may use HH, HL, LH, LL, BOS, CHoCH, Liquidity, Order Block, and FVG to describe market structure. Each term is an analytical reference, not a prediction with guaranteed accuracy.
A BOS describes a break of a relevant structure level; CHoCH describes a change in the observed structural behavior. The significance of a level depends on the analysis context.
Pullback
Pullback describes price returning toward an analytical area. Validation means the scenario’s stated conditions remain supported; Invalidation means those conditions no longer support the scenario.
These analytical references do not guarantee a market reversal, trend continuation, or an accurate Entry price. Always use the levels shown in the latest analysis.
Signal Status & Trading Progress
Signal availability and Trading progress must be read separately. Labels such as Active, Waiting, or Paused may describe how a Signal is presented or made available. They do not by themselves confirm Entry Hit.
Trading progress is based on recorded events. An Entry Zone may be Waiting, Active, or resolved, while the overall Signal can be Partially Resolved or Completed. A Completed Signal is historical, not a fresh Entry.
Active / Waiting / Paused — availability or public presentation, where configured.
Waiting / Active / Partially Resolved / Completed — recorded Signal or Entry Zone progress.
Independent Entry Zones & Targets
A Signal may contain up to three Entry Zones. Each zone has its own setup parameters, such as Entry From, Entry To, SL, TP1–TP3, and Recommended Protection. Different zones can have different BUY or SELL directions when configured.
Each Entry Zone is monitored independently. One zone reaching TP does not mean another zone reached TP. Outcomes should be recorded per zone before being reflected in the combined Signal result.
Pullback settings are optional analytical inputs; they are not an automatic Entry, execution, or ledger outcome.
Signal Events & Trading Outcomes
A recorded event may include Entry Hit, TP1 Hit, TP2 Hit, TP3 Hit, SL Hit, Activate Official BE, BE Hit, Manual Close, or Setup Failed / Cancel Zone. The actions available depend on the zone’s current state.
A zone cancelled before Entry does not represent an executed losing trade. Signal completion occurs when the relevant zone outcomes have been resolved and the Signal is finalized.
These records describe Zhigolds Signal tracking. They do not place, amend, or close orders at your Broker.
Stop Loss, Take Profit & Official BE
SL is the planned invalidation or risk level; TP1–TP3 are potential target levels. Broker spreads, slippage, and execution can cause real outcomes to differ from displayed levels.
Recommended Protection is analytical guidance and does not activate Official BE. Official BE must be recorded as a separate action. BE Hit is calculated from the recorded Official BE reference and may not equal zero Pips or zero cash profit.
Signal Edit History & Audit Trail
When an analyst updates a Signal, supported changes can appear in Signal Edit History. One Update Signal action may group several Before → After field changes into a single “Signal Updated” record, with the affected Entry Zone identified.
Audit Trail helps explain recorded activity and any supported correction or Undo action. A correction should be distinguishable from the original event; an update must not silently be presented as an unchanged historical fact.
The visibility of these records depends on the Dashboard. They do not prove independent external verification, and they are not a substitute for a Broker statement.
Signal History & Performance
Signal History and Performance should use the same Official Signal Ledger outcomes. This avoids a separate display calculating a conflicting Win, Loss, BE, or Pips total.
Each Entry Zone contributes its applicable current final result. Earlier TP milestones are not added again when replaced by a later TP outcome for that same zone.
Performance summaries describe recorded Signal outcomes. They are not account equity, realized Member profits, independently audited returns, or a promise of future performance.
Official Pips Calculation
Pips are calculated according to the configured instrument rules and recorded reference prices. For an illustrative XAUUSD Entry range of 4121–4100, the midpoint is 4110.5. Under the stated rule of 10 Pips per 1.0 price movement, a BUY result at 4200 equals +895 Pips.
For one Entry Zone, TP2 replaces its earlier TP1 contribution; the system does not add both as separate final outcomes. SL Hit may produce negative Pips. Manual Close uses the recorded Close price. Cancel before Entry contributes zero Pips. Official BE Hit uses its recorded BE reference and is not necessarily zero Pips.
Instrument-specific calculation rules may differ. Pips are a standardized Signal result in this system, not a Member’s cash profit, executed price, or Broker-verified return.
Previous Signal & New Signal
When a new Signal is prepared for an instrument with an existing Signal, the analyst may need to confirm how the previous scenario is resolved. An older Signal should not be mistaken for the current opportunity.
The latest Signal, its status, and the relevant Entry Zone direction should always be checked together.
Signal Updates & Notifications
Review the latest Signal status and update time in the Dashboard. Alerts and notifications may be delayed, and a screenshot can become outdated.
Manage any open trades through your Broker and use your own risk controls. Notifications do not replace live execution monitoring.
Member Login & Registration
Use the official Zhigolds Signals Dashboard at /signal-dashboard/ to register or sign in. The available features depend on Member access.
Zhigolds Signals Dashboard accounts and Broker Trading accounts are separate services. Zhigolds provides Trading Signals and market analysis as a reference. Users independently open and close positions through their own Broker accounts.
Trading Risk & User Responsibility
Trading involves risk. Always use proper risk management. Market volatility, leverage, spreads, and slippage can cause losses and different real execution outcomes.
A Signal, ledger record, or historical performance result does not guarantee an accurate Entry or a profitable trade.
Frequently Asked Questions
Does the Dashboard trade for me? No. Does Active always mean Entry Hit? No. Can zones have independent directions and outcomes? Yes, when configured.
Does TP2 add TP1 twice? No. Does a cancelled, untriggered zone count as a losing trade? No; its Pips contribution is zero under the described rules. Is BE Hit always zero Pips? No.
Are ledger records independently audited? Not by default. Can I treat the displayed Pips as my Broker profit? No. Can a completed Signal be treated as a new Entry? No.
Official Signal Ledger & Calculation Transparency
The Official Signal Ledger is the system record of Signal events and their calculated outcomes. When a zone reaches Entry, TP, SL, BE, or a recorded Close, the applicable event is reflected in the official results. Signal History and Performance should read these same results rather than maintaining separate totals.
The purpose is consistency: one current final outcome per Entry Zone, no duplicate TP counting, and an identifiable record of supported changes. Analysts may record outcomes, but they should not manually type arbitrary Performance totals as if those totals were system-calculated.
An automatically calculated result is not the same as an independently verified market event. The accuracy of the input event, its timestamp, and its price reference still matter. Members should be able to understand the calculation method and distinguish recorded changes from original events.
Transparency status: This guide does not claim that records are immutable, tamper-proof, externally audited, or verified against independent market data. Such claims require separately implemented, tested, and publicly demonstrable safeguards.
Example: From Signal Event to Ledger Result
Consider a hypothetical XAUUSD BUY Entry Zone with reference Entry 4110.5. Entry Hit is recorded, then TP1 Hit. If TP2 Hit is later recorded, the zone’s current final contribution is recalculated using TP2 rather than adding TP1 and TP2 together.
If a different Entry Zone reaches SL, that zone has its own negative contribution. The combined Signal result reflects the applicable outcomes of each resolved zone, under the configured rules. The result is then presented in Signal History and Performance.
This example illustrates the calculation flow only. It is not a live Signal, a Broker trade, or proof that a particular market price was reached.
Trading Terminology
Entry Zone: analytical price area. Entry Hit: recorded zone activation. TP Hit: recorded target outcome. SL Hit: recorded Stop Loss outcome. Official BE: a separately activated Break Even reference. BE Hit: recorded outcome using that reference.
Pullback: price return toward an analysis area. Validation: conditions supporting a scenario. Invalidation: conditions that no longer support it. Signal Edit History: supported Before → After changes. Audit Trail: record of supported system actions. Official Signal Ledger: source of recorded outcomes and calculations. Pips: calculated price movement, not cash profit.
Official Support & Next Steps
Before following a Signal, check the latest analysis, Entry Zone, Trading progress, and risk information. Contact Zhigolds Support if you need help understanding the Dashboard.
Never share passwords, OTP, recovery codes, Broker passwords, or other sensitive credentials with anyone through email, WhatsApp, or social media.
Questions about Signals or Member access?