Get DowGold — Top Recommended EA →
/* Only complements native navigation; native search and Woo actions stay unchanged. */ (()=>{ const key='cfHeaderDraft40435'; window[key]?.dispose?.(); const abort=new AbortController(),media=matchMedia('(max-width:1024px)'); const header=()=>document.querySelector('.elementor-40435.elementor-location-header'); const toggle=()=>header()?.querySelector('.cf-header-nav .elementor-menu-toggle'); const expanded=t=>t&&(t.getAttribute('aria-expanded')==='true'||t.classList.contains('elementor-active')); const close=focus=>{const t=toggle();if(expanded(t)){t.click();if(focus)t.focus();}}; document.addEventListener('keydown',event=>{ if(event.key==='Escape'&&expanded(toggle())){close(true);event.preventDefault();} },{signal:abort.signal}); document.addEventListener('pointerdown',event=>{ const nav=header()?.querySelector('.cf-header-nav'); if(media.matches&&expanded(toggle())&&nav&&!nav.contains(event.target))close(false); },{signal:abort.signal}); const change=()=>close(false);media.addEventListener('change',change); const disposeCart=cfEnhanceDraftCart(header()); window[key]={dispose(){abort.abort();media.removeEventListener('change',change);disposeCart();}}; /* Proposal only. Call inside the draft header's existing behaviour IIFE: * const disposeCart = cfEnhanceDraftCart(header()); * Include disposeCart() in that IIFE's existing dispose method. * Native cart toggling, fragments and checkout links remain untouched. */ function cfEnhanceDraftCart(header) { if (!header || header.getAttribute('data-elementor-id') === '353') return () => {}; const abort = new AbortController(), owned = new Map(); let wasOpen = false, closing = false, frame = 0; const refs = () => { const widget = header.querySelector('.cf-header-cart'); return {widget, pane:widget?.querySelector('.elementor-menu-cart__main'), trigger:widget?.querySelector('.elementor-menu-cart__toggle_button'), close:widget?.querySelector('.elementor-menu-cart__close-button, .elementor-menu-cart__close-button-custom')}; }; const open = r => !!r.widget?.classList.contains('elementor-menu-cart--shown'); const attribute = (el, name, value) => { if (!el || el.getAttribute(name) === value) return; if (!owned.has(el)) owned.set(el, new Map()); const values = owned.get(el), old = values.has(name) ? values.get(name).old : el.getAttribute(name); values.set(name, {old, value}); el.setAttribute(name, value); }; const prepare = r => { if (!r.pane) return; if (!r.pane.id) attribute(r.pane, 'id', 'cf-cart-dialog-' + header.getAttribute('data-elementor-id')); attribute(r.pane, 'role', 'dialog'); attribute(r.pane, 'aria-modal', 'true'); if (!r.pane.hasAttribute('aria-label') && !r.pane.hasAttribute('aria-labelledby')) attribute(r.pane, 'aria-label', 'Shopping cart'); attribute(r.pane, 'tabindex', '-1'); attribute(r.trigger, 'aria-haspopup', 'dialog'); attribute(r.trigger, 'aria-controls', r.pane.id); if (r.close) { if (!r.close.matches('button, input[type="button"]')) attribute(r.close, 'role', 'button'); attribute(r.close, 'tabindex', '0'); if (!r.close.hasAttribute('aria-label') && !r.close.hasAttribute('aria-labelledby')) attribute(r.close, 'aria-label', 'Close shopping cart'); } }; const focusable = pane => [...pane.querySelectorAll('a[href],button,input,select,textarea,summary,[tabindex],[contenteditable="true"]')] .filter(el => el.tabIndex >= 0 && !el.matches(':disabled') && !el.closest('[hidden],[inert],[aria-hidden="true"]') && el.getClientRects().length && getComputedStyle(el).visibility === 'visible'); const focusInside = () => { const r = refs(); if (!open(r) || closing || !r.pane) return; (focusable(r.pane)[0] || r.pane).focus({preventScroll:true}); }; const returnFocus = () => { const t = refs().trigger; if (t?.isConnected) t.focus(); }; const sync = () => { const r = refs(); prepare(r); const now = open(r); if (now && !wasOpen) { closing = false; cancelAnimationFrame(frame); frame = requestAnimationFrame(focusInside); } else if (!now && wasOpen) { closing = true; cancelAnimationFrame(frame); returnFocus(); closing = false; } else if (now && r.pane && !r.pane.contains(document.activeElement) && !closing) { cancelAnimationFrame(frame); frame = requestAnimationFrame(focusInside); } wasOpen = now; }; const closeNative = () => { const r = refs(); if (!open(r)) return; closing = true; returnFocus(); // Invoke the existing handler; never change its internal isCartOpen state. (r.close || r.trigger)?.click(); if (open(refs())) { closing = false; focusInside(); } }; document.addEventListener('keydown', event => { const r = refs(); if (!open(r) || !r.pane) return; if (event.key === 'Escape') { event.preventDefault(); event.stopPropagation(); closeNative(); return; } if ((event.key === 'Enter' || event.key === ' ') && r.close?.contains(event.target) && !r.close.matches('button, input[type="button"]')) { event.preventDefault(); closeNative(); return; } if (event.key !== 'Tab') return; const list = focusable(r.pane), first = list[0], last = list[list.length - 1], current = document.activeElement; if (!first) { event.preventDefault(); r.pane.focus({preventScroll:true}); } else if (!r.pane.contains(current) || (event.shiftKey && (current === first || current === r.pane))) { event.preventDefault(); (event.shiftKey ? last : first).focus({preventScroll:true}); } else if (!event.shiftKey && current === last) { event.preventDefault(); first.focus({preventScroll:true}); } }, {capture:true, signal:abort.signal}); // Move focus before native click handlers apply aria-hidden to the pane. document.addEventListener('click', event => { const r = refs(); if (!open(r) || !r.pane) return; if (r.close?.contains(event.target) || !r.pane.contains(event.target)) { closing = true; returnFocus(); queueMicrotask(() => { if (open(refs())) { closing = false; focusInside(); } }); } }, {capture:true, signal:abort.signal}); document.addEventListener('focusin', event => { const r = refs(); if (!closing && open(r) && r.pane && !r.pane.contains(event.target)) focusInside(); }, {capture:true, signal:abort.signal}); const observer = new MutationObserver(sync); observer.observe(header, {subtree:true, childList:true, attributes:true, attributeFilter:['class','aria-hidden']}); sync(); return () => { observer.disconnect(); abort.abort(); cancelAnimationFrame(frame); for (const [el, attrs] of owned) for (const [name, {old, value}] of attrs) { if (el.getAttribute(name) !== value) continue; if (old === null) el.removeAttribute(name); else el.setAttribute(name, old); } }; } })();

GoldRunnerPro EA MT5 Review: Basket Management and Cent Accounts

By /

GoldRunnerPro EA MT5 combines automated gold basket management, pending orders and recognition of existing trades after restart. Its appeal is the coordination of an entire trading structure. Our assessment is that account compatibility and total basket exposure deserve more attention than the rising line in its gallery: the developer requires a cent hedging account, while the public record does not yet establish a separately monitored result for this EA.

Ready to Buy GoldRunnerPro EA MT5?

$399.96 with crypto · $499.95 by card

Official version · Instant download · Future updates included · 7-day money-back guarantee

Download GoldRunnerPro here

GoldRunnerPro EA MT5 promotional cover
CheaperForex promotional artwork based on the product identity; not a trading result.

Evidence checked 25 September 2026. We inspected Ravikant Rajkumar Shete’s listing, four original gallery images, release notes and public comments. We have not run GoldRunnerPro or verified its account statements independently.

Basket management is the defining feature

The listing explains the order-management architecture more clearly than the entry strategy. It says the EA coordinates several positions, watches their combined floating result and handles pending orders, protective levels and closing. Selected operations use asynchronous processing, which means trade requests can be handled without waiting for each request to complete in a strictly sequential workflow. It does not establish a guarantee that every request fills successfully.

The developer keeps the underlying strategy parameters protected. Consequently, there is insufficient public detail to classify its complete entry model as a particular indicator crossover or breakout formula. Nor does the available text justify a no-grid or no-martingale claim. Those labels would require evidence about position additions and lot progression, beyond the general description of a basket.

GoldRunnerPro XAUUSD M15 trade history
Original developer M15 chart with dense entry and exit markers. Retrieved 25 September 2026; markers alone do not establish risk or profitability.

The M15 screenshot shows many entry and exit markers clustered across successive gold moves. This supports the description of multi-position activity, but the chart does not reveal the peak simultaneous volume, equity drawdown or margin use. A busy chart is not a substitute for the complete trade and equity record.

The cent-account instruction matters

The overview explicitly calls for a cent account with hedging support. It recommends US$1,000 of starting funds and 1:500 leverage, and the latest release note gives Tier 1 a 0.03-lot example. These values belong together with the broker’s contract definition. A lot on one cent instrument must not be assumed to have the same cash exposure as a lot on a standard account.

The practical compatibility check is therefore more specific than asking whether a broker offers MT5. Confirm that opposite positions can coexist, that the account is denominated as expected, and that the gold contract’s minimum volume and increment accept the intended inputs. Higher leverage changes margin requirements; it does not remove the market loss on an open position.

The gallery contains M5 and M15 chart views. The public overview does not select one as the required attachment timeframe. We would follow the supplied instructions rather than turn a screenshot’s chart label into an unsupported deployment rule.

What changed in the early releases?

The listing was published on 24 September 2026. Dated notes on 25 September describe new user-configurable tier sizes followed by a simplification of those settings. The earlier note lists examples for three tiers, while the latest note retains only a Tier 1 default in its explanation. That is a reason to check the inputs of the supplied current file instead of copying an older set of numbers from a review.

The same distinction applies to the word recovery. Here the developer describes detecting positions and pending orders after an EA or platform restart. It is operational continuity, not proof of a loss-recovery algorithm or an assurance that a losing basket returns to profit.

Reading the original terminal report

GoldRunnerPro developer terminal report
Original developer terminal report, retrieved 25 September 2026. The displayed report includes both robot and manual trading; currency denomination and full account risk are not established.

The screenshot’s horizontal axis runs from 31 August to 23 September 2026. It displays a result of 9,904.30 and a profit factor of 1.32, but does not establish the account currency denomination or cash starting balance. Given the explicit cent-account instruction, we would not label the displayed result as US-dollar profit.

More importantly, the report separates 2,536 robot deals from 55 manual deals. It therefore does not isolate this EA’s contribution. The report also predates the latest input changes and does not expose the full equity history in this view. We cannot calculate a credible return on capital or maximum drawdown from this screenshot alone.

A public monitored account with its account type, deposits, withdrawals, equity drawdown and complete trade history would materially strengthen the evidence. None was linked on the product or seller page at this check. There were also no buyer reviews or published comment discussions available to assess. These are gaps in the present evidence, not proof that the software cannot work.

What a useful demo check should establish

  1. Confirm the account supports the required cent denomination and hedging mode.
  2. Compare each configured tier with the actual cash exposure and volume opened.
  3. Observe the combined basket’s floating result, margin use and exit behaviour.
  4. On demo, verify that an ordinary terminal restart resumes management of existing EA trades without duplicating orders.
  5. Retain the journal and trade list so execution issues can be distinguished from strategy decisions.

The buying decision should rest on whether that workflow suits your account and risk limits. The software’s management features are concrete; a durable trading edge and a maximum exposure bound are not established by the current gallery.

Also from Ravikant Rajkumar Shete

Compare GoldArbitrage EA MT5 and our GoldArbitrage review. GoldArbitrage monitors a difference between two configured gold instruments; GoldRunnerPro manages a coordinated position basket. They are separate trading systems, not alternate platform editions.

Verify it yourself

View GoldRunnerPro EA MT5 and current pricing