D-Wave Quantum Soars 4.73% as Trading Volume Surges to $530M Ranking 193rd in Market Activity

, 2025, , , . The stock's performance reflects renewed investor interest in the quantum computing sector.

The company recently appointed as Chief Information Security Officer, signaling a strategic emphasis on cybersecurity amid rapid expansion. This move aligns with broader efforts to strengthen its position in the quantum technology landscape, particularly as it competes with peers like Rigetti Computing and IonQ within the Defiance Quantum Computing ETF, .

Financially, , supported by its Advantage2 system and partnerships. Despite negative profit margins, , providing flexibility for R&D and market expansion. Analysts highlight the company's focus on solving complex for industries like energy and finance, which could drive long-term demand.

Strategic developments, including ETF inclusion and executive appointments, have bolstered market confidence. However, the sector's inherent volatility and reliance on speculative growth remain risks. , though slow asset turnover suggests a long-term R&D-driven business model.

To set up an accurate back-test I need to pin down a few practical details about the strategy and the data universe. 1. Stock universe • Do you want all U.S. listed common stocks (≈ 7,000 tickers) or a defined index/segment (e.g., S&P 500, Russell 3000, NASDAQ)? • Should ETFs, ADRs, or preferred shares be excluded? 2. Ranking & weighting • “Top 500 by daily trading volume” – ranked by dollar volume (price × shares) or by share turnover? • After selecting the 500 names each day, should the position be equal-weighted across them, value-weighted, or some other scheme? 3. Trade execution & holding period • Buy at that day’s close and sell at the next day’s close (close-to-close), or buy at next-day open and close at next-day close (open-to-close)? • Any transaction costs or slippage to include? 4. Benchmark / metrics • Any particular benchmark to compare against (e.g., SPY)? • Beyond cumulative return and drawdown, any other metrics you’d like (Sharpe, hit rate, etc.)? Once I have these details I can generate the retrieval plan, pull the necessary data, and run the back-test.