ProjectX

@Wepth @CoachDBA Open API; Exceptional Mobile Experience; Faster & Deeper Data... oh wait, that's us.

@CoachDBA Only thing project x has better is lockout tools nothing else

Hot Take: Tradovate would be number 1 Platform if they fixed their risk settings like Project X. Came back to my TP being hit and my accounts being in longs/reversed after, losing my pnl for the day. Luckily I caught it quick and hit my TP again.

@NinjaTraderProp This is some next level creativity.

If you can relate... ...throw us a follow 👀

@Tradovate you good or nah?

ProjectX + New Plans: Go-Live Schedule 📣 Tradovate Users Updated Plans Go-Live: Friday, September 12 @ 8:00 AM EST Reminder: Details of plan changes here - help.tradeify.co/en/articles/12… 📣 ProjectX ProjectX will be available as a platform option for new accounts: Sunday, September 14 @ 5:00 PM EST Get ready - bigger & faster payouts, cleaner rules, and a new platform option! 📈 tradeify.co

@FvckYourHedge @Topstep Do you have Level 2 Depth of Market data enabled?

Guys this is not hate, but for people like me that barely see charts and never used time series Candles. This is freaking horrible, Projext x is useless for me, and I come to Quantower, and ALL PLATFORM IS EMPTY, I cant even SEE MY INDICATORS. @Topstep Guys, please fix this. For real, this sucks. I am punished to watch 5 minutes charts and my volume candles, have very short data.

@Khldfx The choice is clear

What platforms should we add on #fundingticks. Comment below 👇🏽 please 🙏🏽

This drama is dragging longer than it should with everyone suddenly acting like a coder. In our beta integration with ProjectX we assumed accountId was unique. Docs and metrics identified nothing, a month of testing was clean. When we scaled to more users, a clash appeared; one follower account ID existed twice. Causing a trade to copy to the wrong follower of another Tradesyncer user. Maybe we shouldn’t have assumed. But after a month of clean testing, focus naturally shifted to other edge cases and improvements. Regardless, we caught it and fixed in 3 minutes. Not a ProjectX issue. Issue closed.

@jmutrades @vwapx @Wepth @Topstep @MichaelPatak This

@vwapx @projectxtrading @Wepth @Topstep @MichaelPatak This is the case where two users both gave access to a 3rd party tool and the 3rd party tool failed to isolate the accounts from each other.

🚨 BREAKING 🚨 Project X has been found to use the exact same ID for different traders. One user has found in their sleep someone gambling CPI on their account and was linked with theirs through third party software/api. @Topstep @MichaelPatak @projectxtrading please look.

@vwapx @Wepth @Topstep @MichaelPatak That is not what happened here

@projectxtrading @Wepth @Topstep @MichaelPatak Okay, I don’t program so that means nothing to me — what I see here is that a third party program makes it possible for your customers to trade with your other customers accounts ☠️ Isn’t that something you guys would want to fix

@vwapx @Wepth @Topstep @MichaelPatak Every database in existence has a userId = 1. All of our clients have separate databases (and connection URI's) as we do not use single tenancy, which is best practice for a B2B SaaS like us.

@projectxtrading @Wepth @Topstep @MichaelPatak That is really embarrassing to see project X try to pas the issue off to TradeSyncer instead of correct the identification issue. Other providers don’t identify accounts this way — probably for reasons like this. The saying “ignorance of the law is no excuse” comes to mind

@UncleBugatti @dotjosh @Wepth @Topstep @MichaelPatak It seems that Tradesyncer is saying their integration with us is in beta. Not that ProjectX is in beta. We have many services integrated successfully like @TradersPostInc etc

@dotjosh @Wepth @Topstep @MichaelPatak @projectxtrading so tradesyncer just blaming Projectx for their mess up? is it safe to use copier with projectx?

@dotjosh @UncleBugatti @Wepth @Topstep @MichaelPatak You are correct @dotjosh

@UncleBugatti @Wepth @Topstep @MichaelPatak @projectxtrading This looks like TradeSyncer's assumption on how the IDs worked at ProjectX was just wrong. Unless I'm misunderstanding.

@Travisdaman713 @aw_trades_ You set a PDPT which is simply a pending market order awaiting a trigger event. It triggered on the low liquidity news event (in your favor), and exited you where it could at the current best market price.

OMFG I GOT HIT WITH $10,000 OF SLIPPAGE!! In my favor! 😂😂😂 and I passed my 5th TOPSTEP. Time to get back on that leaderboard with @aw_trades_

@crypt0_reaper @Tradovate It was isolated to a single load balance and did not effect all data recipients.

Today, at 12:39 CT, an upstream market data load balancer failed at the CME Chicago data center. This caused market data to stop flowing into our platform until 12:45 CT when fail-overs kicked in. The issue was resolved and the faulty hardware replaced.

Slippage Comparison Test #2 using stop market orders: FOMC Minutes (High Volatility period) 7/30/2025 ProjectX: 1 tick slippage (execute @ 23562 fill @ 23562.25) Tradovate: 1 tick slippage (execute @ 23562 fill @ 23562.25)

@TheSeanTrades Hint: it's not "everyone" :)

I’ve been trading topstepx in 5 xfa accounts. Plus multiple other prop firms on tradovate/rithmic. I have yet to experience wild slippage in any of the accounts. Normal slippage yes but not seeing what everyone is complaining about. Just my experience and I mostly trade using limit orders.

Slippage Comparison Test using stop market orders: FOMC Event 7/30/2025 ProjectX: 2 ticks on each order Rithmic: 12 ticks order #1 / 14 ticks order #2 Tradovate: 4 ticks order #1 / 2 ticks order #2

@zoofxing We understand your concern, but this claim is entirely inaccurate. You can verify your fills against CME raw tick data at any time to see the exact market conditions, ( bid/ask order book). This is possible because, unlike forex, futures trade on a single centralized exchange

@projectxtrading You control the software, meaning you change the trade conditions just like in the MFF case “slip them to hell” all over again