01Fingerprint
Characterize observable container properties, architecture signals, integrity conditions, build indicators, and version-sensitive constraints.
02Map
Recover accessible code and data regions, candidate functions, references, call relationships, control flow, constants, strings, and platform interactions.
03Observe
Collect reproducible runtime evidence when target, authorization, supported tooling, and defined test conditions permit it.
04Lift
Transform low-level findings into a normalized, architecture-aware intermediate representation.
05Explore
Evaluate competing interpretations under structural, data-flow, type, calling-convention, platform, and runtime constraints.
06Reason
Use authorized high-capability AI as a specialist analysis layer, never as an unchecked oracle.
07Challenge
Compare passes, expose contradictions, reject incompatible hypotheses, and return ambiguous regions for deeper analysis.
08Score
Label each result by evidentiary strength and make unresolved ambiguity visible.
Machine-code structure, mapped & cross-examined
The static-analysis layer recovers accessible machine-level structure. IDA output is treated as evidence — not a one-click verdict, and not proof of the author's exact original source.
·Candidate function boundaries
·Control-flow graphs & branches
·Cross-references & call relationships
·Code, data & reference regions
·Memory access patterns
·Constants, strings & imports
·Stack & calling-convention signals
·Compiler-generated patterns
·Data dependencies & platform ops
Machine code in. Structural intelligence out.
Runtime evidence under controlled conditions
Static analysis shows what an accessible path appears capable of. Runtime evidence shows what the target demonstrably did under specific, recorded test conditions — correlating captured execution events, memory transitions, module activity, and observed call paths with static findings.
x64dbg may support authorized specialist research or manual laboratory cross-checking. It is not represented as an unattended production stage unless a compliant headless interface, exact invocation, versioned identity, inputs, outputs, timestamps, exit status, and repeatable evidence are documented.
Static clues begin it. Controlled observation challenges it.
Where raw assembly becomes reviewable structure
Assembly is precise but too low-level to be the final reconstruction language. The backend lifts recoverable findings into a normalized intermediate representation that models:
·Instructions & basic blocks
·Control-flow edges & calls
·Definitions, uses & state transitions
·Registers, memory & side effects
·Arguments, returns, types & conventions
·External & platform-facing operations
·Provenance, uncertainty & confidence
The disassembler sees instructions. The IR reasons about relationships.
An evidence graph, not a pile of tool output
The pipeline connects instructions, blocks, calls, references, constants, state transitions, data dependencies, build-profile knowledge, runtime observations, and confidence changes into an evidence graph. A candidate interpretation is challenged against distant facts — not judged only by the few instructions surrounding it.
The answer rarely lives in one address. It emerges when the graph stops contradicting itself.
FREQUENTLY ASKED QUESTIONS
Straight answers, explicit limitations
What is EX5 reconstruction?+
Extracting, correlating, and organizing defensible technical intelligence from a compiled MetaTrader 5 artifact. It may include structural recovery, data-flow interpretation, platform-interaction mapping, controlled behavioral analysis, and scoped high-level reconstruction. It is not equivalent to guaranteed restoration of the author's exact original project.
Can you recover the exact original MQ5?+
Exact original MQ5 cannot responsibly be guaranteed for every EX5. Compilation can remove or transform identifiers, comments, formatting, macros, abstractions, source-file boundaries, and project structure — and different source programs can produce materially similar compiled behavior. We recover the strongest technically defensible representation the evidence supports and distinguish verified facts from inference, tentative interpretation, and unresolved ambiguity.
Do you guarantee a complete decompilation?+
No. An initial review determines which evidence is available and which recovery depth is technically supportable. Build generation, artifact integrity, compiler transformations, protection mechanisms, runtime availability, and engagement scope can all affect the result.
Is this just AI-generated pseudocode?+
No. AI is one analysis layer inside a pipeline governed by observable static structure, runtime evidence where supported, versioned profiles, deterministic constraints, independent comparisons, and confidence checks. Fluent output that conflicts with the binary is rejected or downgraded.
Which AI models do you use?+
Authorized high-capability OpenAI and Anthropic API models may assist defined analysis roles. Exact model selection, routing, prompts, evaluator logic, and orchestration are proprietary and can change as capability, authorization, provider availability, and scope evolve. The platform does not claim unauthorized, bypassed, or jailbroken access.
How much does the software cost?+
The software license is $6,000 USD as a one-time payment. There is no recurring software subscription. External AI usage, taxes, processing costs, optional services, support, upgrades, and other separately stated items are not silently included in that figure.
Is there a free trial?+
The published licensing model does not include a trial or feature-limited product license. The checkout currently shown on this site is only an interface preview: it does not accept payment, create an account, issue a license, or provide software.
Is the license tied to a user and machine?+
Yes. The license is issued to a registered user and associated with a verified activation profile that can include IP and hardware identity. The registered user may request up to two legitimate IP and/or HWID profile changes per calendar month. Exact activation, reset, transfer, abuse-prevention, and recovery rules are stated in the final license agreement.
Are AI credits included in the $6,000 price?+
No. AI usage is pay-as-you-go. When provider-cost pass-through is enabled, supported OpenAI and Anthropic API usage is charged using the applicable official provider list rate without a platform markup. Taxes, currency conversion, processing fees, enterprise commitments, and optional service charges may still apply.
Do I pay for every EX5 file?+
The software license does not impose a separate software-license charge for each authorized EX5 file analyzed by the registered user. This does not guarantee successful reconstruction of every file, and external AI consumption or optional services can create separate usage charges.
Is EX4 supported?+
EX4 support is coming soon — a roadmap item, not a currently promised production capability. Availability, scope, pricing, compatibility, and upgrade entitlement will be announced when the feature has passed its release gates.
Do you use IDA?+
Authorized analysis environments may incorporate IDA tooling where the product edition is correctly licensed, configured, and genuinely used. Independent parsers and validation stages prevent any single disassembler from becoming ground truth. IDA Pro is not implied unless that exact commercial edition is licensed and deployed.
Do you use x64dbg?+
x64dbg may be used for authorized manual research or specialist laboratory cross-checking where appropriate. It is not represented as a headless production stage unless an unattended, repeatable, provenance-recorded integration is actually available for the target workflow.
Does candidate search mean random brute force?+
No. Candidate exploration is bounded by binary structure, control flow, data flow, calling conventions, inferred types, product-profile rules, and runtime observations where available. It compares evidence-compatible explanations and rejects contradictions; it does not invent arbitrary programs or brute-force encryption.
Can every EX5 be analyzed?+
Every submitted artifact can be assessed, but available analysis depth varies. Compiler generation, build profile, file integrity, protection, accessible code regions, runtime conditions, and requested scope all affect recoverability. No universal compatibility or recovery guarantee is implied.
Can the system handle future MetaTrader builds?+
The architecture is designed around versioned product profiles and host adapters so verified build-specific knowledge can evolve. This is an adaptability design — not a promise that an unreleased or newly changed build is already understood or supported.
What happens when evidence conflicts?+
Confidence is reduced. The affected region may return for deeper analysis where within scope, or it is reported as tentative, contradictory, or unresolved. Conflicts are not silently blended into a more impressive-looking answer.
Why are findings confidence-scored?+
Different regions can have different evidence quality. Confidence scoring prevents a verified call relationship and a tentative semantic interpretation from being presented as equally certain.
How do I know the output is not invented?+
Findings are tied to available evidence. Depending on scope, provenance can include input hashes, tool identities and versions, recorded stages, validation outcomes, repeat-run comparisons, explicit blockers, and confidence history.
Will you expose my trading strategy?+
Public capability materials do not disclose customer-specific binaries, recovered logic, source, traces, or strategy details without explicit written permission. The exact handling, access, provider, retention, and deletion controls are defined in the applicable engagement terms.
Is the service legal?+
The service is restricted to software the customer owns or is explicitly authorized to analyze. Applicable laws, licenses, and contractual restrictions can vary by jurisdiction and use case. Customers are responsible for confirming their authority, and the service may require supporting authorization information.
What do you need to get started?+
Typically confirmation that you own or are authorized to analyze your EX5 files, your activation profile, your recovery, migration, audit, or compatibility objective, and any permitted runtime conditions. Exact requirements are confirmed at licensing.
How long does analysis take?+
Timing depends on artifact size, build generation, integrity, protection, runtime access, requested scope, and validation depth. A timeframe is defined after license activation and an initial review; no instant-recovery promise is implied.
What will I receive?+
Deliverables are defined by the engagement and may include an artifact assessment, structural map, scoped reconstruction, evidence notes, confidence classifications, validation context, limitations, blockers, and recommended next steps.
Will the report reveal your proprietary methods?+
No. Reports can disclose technical provenance and result confidence without publishing private heuristics, signatures, prompts, routing, scoring weights, pruning logic, internal transformations, or recovery recipes.
Technical Integrity, Licensing, and Authorization Notice
EX5 reconstruction is inherently evidence-dependent. Compilation, optimization, build variation, corruption, protection mechanisms, unsupported regions, and missing runtime context can limit recovery. Exact original MQ5 source, original identifiers, comments, formatting, file organization, and developer intent cannot be guaranteed. Functional similarity under bounded tests does not prove universal semantic equivalence.
Named third-party tools are referenced only where they are appropriately licensed, genuinely used, and accurately described. Product names and trademarks belong to their respective owners; their mention does not imply endorsement, certification, partnership, or affiliation.
Where AI is enabled, model access must be provider-authorized and policy-compliant. Model output is treated as an analysis hypothesis and remains subordinate to available binary evidence and validation. Confidentiality, access, processing environment, permitted provider use, retention, and deletion terms must be defined by documented engagement controls before customer artifacts are processed. No unstated security certification, zero-retention guarantee, air-gap claim, or absolute secrecy promise is implied.
This service is intended only for software the customer owns or is explicitly authorized to analyze. It is not offered for strategy theft, license circumvention, access-control defeat, safeguard evasion, or unauthorized protection removal.
No magic. No fake certainty. Just a binary forced through an evidence gauntlet.
EX5 artifacts — with evidence you can inspect.
BTC · 
ETH · 
USDT (TRC-20 / ERC-20). No cards, no PayPal.