how it worked

quantihack ran in two stages — both with cash prizes

online platform — 22nd–27th march

teams competed on our simulated exchange to finish with the highest portfolio value, while taking on mini challenges along the way — with cash prizes for both. players traded manually, wrote algorithms, and reacted to live market events. the top performers qualified for the in-person finals.

in-person finals — 28th march

an all-day hack event in london for the qualifying teams. teams built a project, tackled bounty challenges, and presented to a panel of judges — with the option to invite additional players for finals day.

online platform

teams competed for the highest profits on the platform. here's what they worked with.

feature 01

live trading

teams traded assets in real time on our simulated exchange, watching their portfolio value change tick-by-tick as they competed against other teams on the live order book.

feature 02

algorithmic trading

players wrote algorithms that traded on their behalf using our built-in IDE — deploying strategies in Python or JavaScript that executed automatically against the live market.

feature 03

emergency events

breaking news and emergency market events landed throughout the week. sudden shocks tested each team's ability to adapt their strategies under pressure — just like real markets.

in-person finals — 28th march, london

the top performers from the online week were invited to an all-day hack event in london, with the option to bring in additional players for finals day. this is where it all came together.

finals 01

the hack day

an open-ended hackathon — teams built any data or tech project they liked. the only constraint was a quantitative focus: AI, agents, data visualisation, automation — anything went. teams had the full day to build something impressive and present it to the judges.

finals 02

the challenge board

a board of bounty-style challenges worth varying points ran throughout the day. broadly tech-themed and designed to be accessible — no deep domain expertise required. completed challenges contributed 40% of each team's total score.

finals 03

judging

the remaining 60% came from a panel of judges evaluating each team's main project — weighing creativity and originality, technical difficulty, and how far the team got. judge scores combined with challenge board scores for the final ranking, and prizes went to the top teams.