Gold scalpers: symbol naming and contract specs will wreck a journal if you assume every “XAUUSD” is identical.
Things I double-check on IC (and any broker) before I trust gold size math:
• Exact symbol (XAUUSD vs variations / account type differences)
• Contract size / pip value assumptions in the platform vs my risk sheet
• Min stop / freeze level on gold specifically (often uglier than majors)
• Whether mobile/web flatten behaves the same as desktop on gold tickets
I’m not doing a fan thread — I want practical quirks people hit when they move between raw accounts, symbols, or VPS setups.
If you trade XAU on IC: any symbol/contract gotchas that surprised you on sizing or SL modify?
Execution discussion; DYOR; not financial advice. Affiliate relationships may exist on this forum — treat numbers as your own logs.
IC Markets symbol swap and contract size quirks for XAUUSD
-
LondonScalper
- Posts: 701
- Joined: Sat Sep 05, 2026 7:54 am
-
PropScalpDesk
- Posts: 273
- Joined: Sat Sep 19, 2026 7:50 pm
Re: IC Markets symbol swap and contract size quirks for XAUUSD
XAUUSD specs before gold size math
Symbol naming and contract size will wreck a journal if you assume every XAUUSD is identical. Before I trust gold lots on any broker — IC included — I verify exact symbol, contract size, and pip/point value against a tiny live ticket, not against a blog table.
Frankfurt checklist:
When a broker adds a suffix or swaps a gold feed, I re-run the micro verification trade before any normal size. Assumptions decay. Verification is cheap.
Have you ever caught a silent contract-size difference only after a week of mis-sized gold — and how do you verify after a broker back-end change?
Symbol naming and contract size will wreck a journal if you assume every XAUUSD is identical. Before I trust gold lots on any broker — IC included — I verify exact symbol, contract size, and pip/point value against a tiny live ticket, not against a blog table.
Frankfurt checklist:
- Confirm symbol string on the account type I actually fund
- Compute risk in account currency from stop distance using platform contract specs
- Log one micro trade’s PnL versus expected to catch swap/spec surprises early
When a broker adds a suffix or swaps a gold feed, I re-run the micro verification trade before any normal size. Assumptions decay. Verification is cheap.
Have you ever caught a silent contract-size difference only after a week of mis-sized gold — and how do you verify after a broker back-end change?