#951 - A Game of Chance
Two players play a game using a deck of \(2n\) cards: \(n\) red and \(n\) black. Initially the deck is shuffled into one of the \(\binom{2n}{n}\) possible starting configurations. Play then proceeds, alternating turns, where a player follows two steps on each turn:
- Remove the top card from the deck, taking note of its colour.
- If there is a next card and it is the same colour as the previous card they toss a fair coin. If the coin lands on heads they remove that card as well; otherwise leave it on top of the deck.
The player who removes the final card from the deck wins the game.
Some starting configurations give an advantage to one of the players; while some starting configurations are fair, in which both players have exactly \(50\%\) chance to win the game. For example, if \(n=2\) there are four starting configurations which are fair: RRBB, BBRR, RBBR, BRRB. The remaining two, RBRB and BRBR, result in a guaranteed win for the second player.
Define \(F(n)\) to be the number of starting configurations which are fair. Therefore \(F(2)=4\). You are also given \(F(8)=11892\).
Find \(F(26)\).
Problem text © Project Euler, licensed under CC BY-NC-SA 4.0. Original: projecteuler.net/problem=951. Published Saturday, 21st June 2025, 11:00 pm. Solved by 423 members at time of mirroring.
Why this is useful
Probability Statistics. Expectation and state-based probability reasoning underpin pricing, risk, and statistical inference (Phases 7, 11, 13).
We classify relevance honestly - not every Euler problem is a trading application.
Prerequisites
Lessons that prepare you:
13.2 Monte Carlo Estimation and Error Analysis · 19.8 Bit Manipulation and State Compression · 19.7 Dynamic Programming: Memoization and Tabulation · 7.3 Independence, Conditional Probability, and Conditional Expectation · 7.2 Expectation, Moments, and Key Inequalities · 7.1 Probability Spaces, Random Variables, and Distributions
Recommended stepping-stone problems: #313 · #692 · #961
Concepts: game-theory probability
Likely techniques: bitmask-dp
Learning mode
Pick how much scaffolding you want. Your choice is remembered per problem.
Understand the problem
- What exactly is the input to problem 951? Is it a bound (11892), a supplied dataset, or a definition you must generate from?
- What is the required output - restate it precisely: a single exact integer.
- Which objects exactly are in scope, and which are excluded by the wording (strict vs non-strict inequality, 'distinct', 'proper', 'below' vs 'up to')?
- What do the arguments of F(n), F(2) mean, and what is the value's type (count, sum, probability)?
- What are the edge cases: the smallest legal object, zero/one, ties, and the boundary at exactly 11892?
- Why is brute force hard HERE specifically? Estimate the number of candidates implied by 11892 and the cost of testing one.
- Which game-theory fact would, if true, collapse the search - and can you state it as a testable claim before you look for a proof?
Predict & plan (before you code)
- Predict the strategy: in one sentence, what will your solution do? (The classification says game-theory / bitmask-dp - do you agree, and why?)
- Predict the complexity of your intended method in terms of N = 11892, and the wall-clock time you expect. Write both down now.
- Predict the key data structure: what is stored, keyed by what, and how large will it get at full scale?
- Predict the failure mode: what is most likely to break - an off-by-one on the bound, a definition misread, precision, or memory?
- Predict the output of the small case from rung 3 BEFORE running it (the statement says: "For example, if n=2 there are four starting configurations which are fair: RRBB, BBRR, RBBR, BRRB.") - then run it. A surprise here is worth more than an hour of debugging later.
Scratchpad
Mathematical notes, formulas, pseudocode, hypotheses, complexity notes. Saved automatically with your progress.
Python workbench
Real Python (Pyodide) in a sandboxed Web Worker - no network, no filesystem, no DOM access. Ctrl/Cmd+Enter runs. Escape leaves the editor. Stop terminates the worker.
Check your answer
Answers are checked against a salted hash held in a separate file - not printed in this page. This prevents accidental spoilers; it is not cryptographic protection (see the build notes).
Progressive hints
Optimization
You have a correct answer. That is the start of the learning, not the end.
- Reduce the time complexity. What is the bottleneck, and what mathematical fact removes it?
- Reduce memory. Can you stream, or keep only the last k states?
- Replace brute force with a closed form, a sieve, a recurrence, or a symmetry argument.
- Prove the optimized version computes the same thing.
- Compare two implementations and time them.
Explain it
Which step of your solution were you least confident about, and what evidence would settle it?
What did you try first, and what specifically made you abandon it - a proof, a timing, or a wrong small-case answer?
Where did the game-theory structure do the real work? Name the single observation that collapsed the search space.
Could you have reached the bitmask-dp idea faster? Which words in the statement were pointing at it, and did you notice them?
What was the bug that cost you the most time, and what CLASS of bug was it (off-by-one, definition misread, precision, state under-specified)?
How would your solution change if the bound 11892 were multiplied by 1000? Does it survive, or does it need a different idea?
What is the honest complexity of what you wrote (not what you intended), and where is the remaining slack?
Which problem you have already solved is this most similar to, and what is the shared skeleton - is it really 'bitmask-dp' underneath?
State the transferable technique in one sentence, without mentioning this problem's story at all.
Self-assess (mastery is not a correct number)
You reach Mastered only when you have solved it, rated yourself at least Solid across the dimensions, and written a real explanation.
Confidence
Low confidence schedules this problem for spaced review, even if you solved it.
Mastery check
- Variation: change the bound (or a rule) in the statement. Does your method still work? What breaks first?
- Constraints: if the limit were 10× larger, which step fails, and what would you replace it with?
- Related problem: #313 · #692 · #961
- Transfer: where else does this technique appear? Name a lesson and a real computational setting.
- Spaced re-attempt: come back after the review interval and re-solve it with no hints.