docs(experiments): assess Trade Nation; refuse it on the instrument, not the transport - #210
Merged
Merged
Conversation
…not the transport Trade Nation came up as a candidate execution venue. This records the answer so the question is not re-litigated from scratch, following the house form set by the Coinbase asset-class study and the cTrader assessment. The verdict is no, and the refusal is structural. What distinguishes this from cTrader is that a technically usable Python order path DOES exist here: MT4 accounts are self-serve, Expert Advisors are an advertised feature, and open source MQL4-to-Python bridges are a solved problem. So the refusal cannot rest on "there is no API" — it rests entirely on what is being traded. Trade Nation is CFD and spread-betting only. There is no unleveraged spot ownership anywhere in its product range, so rails 17, 18 and 19 and the curation screen each reject it independently, and rail 19's own comment records that spot-only is the charter with no config field to widen it. The no-API finding is established by enumeration rather than by a failed search: 1,420 sitemap URLs plus 160 support URLs with zero connectivity pages, seven direct path probes returning 404, and no vendor to appeal to -- FINSA EUROPE LTD is Trade Nation Financial UK Ltd, same company, so TN Trader is proprietary and there is no white-label API doc to read. Documentation review only. No account was opened; api.tradenation.com is a private backend for their own apps and was deliberately not probed. Builds nothing: no adapter package, no dependency, no entry point. Closes #204 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #204.
Trade Nation came up as a candidate execution venue. This records the answer so the question is not re-litigated from scratch, following the house form set by
docs/experiments/2026-08-05-coinbase-asset-class-feasibility.mdand the cTrader assessment in #203.Verdict
No — and the refusal is structural, resting on the instrument rather than the transport.
What distinguishes this from cTrader is that a technically usable Python order path does exist here. MT4 accounts are self-serve, Expert Advisors are an advertised feature (
Automate using Expert Advisors (EAs)on their own platforms page), the live server name is public, and open-source MQL4-to-Python bridges are a solved problem. A determined engineer could have Python placing live orders at Trade Nation inside a weekend. So the refusal cannot rest on "there is no API" — and the document deliberately builds that counter-case at full strength before answering it.It is answered on the only ground that matters: every keel gate is a gate on what is traded, not on how the order arrived. A bridge does not launder gharar.
Trade Nation is CFD and spread-betting only — leveraged, financed, non-deliverable, short-symmetric, with no rights of ownership (UK Client Agreement cl. 3.5). There is no unleveraged spot ownership anywhere in its product range, so rails 17, 18 and 19 and the curation screen each reject it independently, and rail 19's own comment records that spot-only is the charter with no config field to widen it.
On the missing API
The negative is established by enumeration, not by a failed search, so it is falsifiable rather than an absence of evidence: 1,423 sitemap URLs plus 160 support URLs with zero connectivity pages, seven direct path probes, and "API" appearing zero times on six key pages. There is also no vendor to appeal to —
FINSA EUROPE LTDisTRADE NATION FINANCIAL UK LTD(Companies House 07073413, renamed 2022), socom.finsa.*is a legacy in-group namespace and TN Trader is proprietary. No white-label API doc exists to read.Scope
Documentation review only. No account was opened;
api.tradenation.comis a private backend for their own apps and was deliberately not probed. Builds nothing — no adapter package, no dependency, no entry point, no conformance fake.Review
Independently reviewed by a fresh reviewer before this PR: verdict APPROVE WITH CHANGES, all 6 required changes applied. The reviewer verified all 55
file:linecitations (zero errors after an earlier fix pass corrected 7) and 9 of the KB quotations verbatim, and independently falsified two details of the enumeration — which the method is designed to permit. Corrections applied cover the stale §66.7 crypto claim (since partially closed by §71/§72/§85), real platform-specific instrument names, the/api/302, dividend adjustments, and the primary-source ownership clause. The reviewer's strongest attack — the swap-free/"Islamic" account — is now pre-empted in the document: it removes the riba on the rollover and leaves gharar and cash-settlement-no-delivery untouched.Note on the rails' limits
The document volunteers where the rails stop rather than overstating them. A cosmetic rename to
EUR-USDis a faithful transliteration that clears rails 18 and 19 outright, leaving only rail 1 and the curation screen — and #202 is why the screen is not claimed as an unconditional defence. That residual is stated plainly rather than papered over.