Source code
Buying EA Source Code: A Practical Pre-Purchase Checklist
Before buying EA source code, verify what is editable, what can be compiled, which version is delivered, what the licence permits and what evidence supports the seller's claims. “100% source” should describe a concrete delivery, not substitute for those answers.
Ask for the complete delivery list
Request the main source file, required includes, external dependencies, presets and documentation. Establish whether any part of the implementation remains inside a compiled library or DLL. A screenshot of readable code does not by itself establish completeness.
Use the file-extension guide to separate source from executables and settings. For every dependency, ask whether it is supplied, freely obtainable or separately licensed, and whether the build instructions explain its location.
Separate three different identities
- Product identity: the strategy or product name used in the listing.
- Delivered release: the precise source package you receive.
- Tested build: the executable and settings used for the supplied evidence.
A new version on another marketplace does not prove that a source package has been updated to match it. Ask whether the implementation is original, ported or independently rebuilt, and what was actually compared. Similar names or screenshots do not establish behavioral equivalence.
Match each claim to evidence
| Claim | Useful evidence |
|---|---|
| You can build it | Source inventory, dependencies and a reproducible compilation record. |
| It follows described rules | Documented scenarios with expected and observed events. |
| It was backtested | Full report, settings, dates and execution assumptions. |
| It was observed on a chart | Dated operating logs and a stated demo/live environment. |
None of these proves future profit. Be especially careful when a sales argument jumps from a selected backtest to a guaranteed outcome. The CFTC's forex fraud guidance discusses high-return, low-risk sales claims.
Read the licence and support scope
Editable source does not automatically grant redistribution or resale rights. Read the actual licence for the activities you intend to perform. If the intended use is unclear, ask for written clarification before paying rather than assuming “source included” means unrestricted use.
Establish which problems qualify for bug fixes, how long support lasts, what evidence is needed and whether new features or modifications are included. Read delivery timing and refund terms together, including any applicable statutory-rights exceptions. This is a purchasing checklist, not an interpretation of a particular jurisdiction's law.
Prepare an acceptance record before payment
Write down the promised files, release, dependencies and instructions. On delivery, compare the package with that record, compile it and perform the documented checks. Preserve discrepancies with enough detail for the seller to investigate.
For MQLume's current offerings, inspect the release, parameter guide and testing boundaries on Quantum Titan MT5 or The Gold Reaper MT5, then read the applicable licence and support terms. Evaluate the particular package; do not infer its capabilities from a brand name alone.
Back to top