Skip to main content

The Problem Pit: The Pit of Egyptian Fractions

 

The Pit of Egyptian Fractions: Sploding Rational Numbers Into Unit Fractions

There are problems that hide their teeth. They grin at you like puzzles for children, then drag you into quicksand. Egyptian fractions are one of those problems.

The rule is simple:

Problem. Write any rational number pq\tfrac{p}{q} as a sum of distinct unit fractions:

pq=1a1+1a2++1ak,aiZ+ distinct.\frac{p}{q} = \frac{1}{a_1} + \frac{1}{a_2} + \cdots + \frac{1}{a_k}, \quad a_i \in \mathbb{Z}^+ \text{ distinct}.

The Egyptians did this thousands of years ago. They refused to write 34\tfrac{3}{4} as “three-fourths.” Instead, they would say:

34=12+14.\frac{3}{4} = \frac{1}{2} + \frac{1}{4}.

At first, I thought: how charming, how elementary. Surely this would be the lightest kind of math to play with.

Instead, it became a pit.


Step 1: The Honeymoon Phase

I began with easy cases:

  • 23=12+16.\tfrac{2}{3} = \tfrac{1}{2} + \tfrac{1}{6}.

  • 34=12+14.\tfrac{3}{4} = \tfrac{1}{2} + \tfrac{1}{4}.

  • 56=12+13.\tfrac{5}{6} = \tfrac{1}{2} + \tfrac{1}{3}.

So clean! I imagined there must be a simple formula for everything.

Then 45\tfrac{4}{5}:

45=12+14+120.\frac{4}{5} = \frac{1}{2} + \frac{1}{4} + \frac{1}{20}.

Not bad. Slightly more work, but still tidy.

I was lulled into confidence.


Step 2: The Greedy Algorithm

The classic method is the greedy algorithm:

  1. Given pq\tfrac{p}{q}, pick the largest unit fraction 1n\tfrac{1}{n} such that 1npq\tfrac{1}{n} \leq \tfrac{p}{q}.

  2. Subtract it.

  3. Repeat with the remainder.

It always works. That sounds comforting. But in practice, it’s a slippery rope down the pit.


Example A: 5121\tfrac{5}{121}

  • Largest unit fraction ≤ 51210.0413\tfrac{5}{121} \approx 0.0413 is 125=0.04\tfrac{1}{25} = 0.04.

Subtract:

5121125=5251213025=1251213025=43025.\frac{5}{121} - \frac{1}{25} = \frac{5\cdot25 - 121}{3025} = \frac{125 - 121}{3025} = \frac{4}{3025}.
  • Now largest ≤ 43025\tfrac{4}{3025} is 1757\tfrac{1}{757}.

Subtract:

430251757=475730253025757=302830252292925=32292925.\frac{4}{3025} - \frac{1}{757} = \frac{4 \cdot 757 - 3025}{3025 \cdot 757} = \frac{3028 - 3025}{2292925} = \frac{3}{2292925}.
  • Next: largest ≤ 32292925\tfrac{3}{2292925} is 1764309\tfrac{1}{764309}.

Subtract:

322929251764309=376430922929252292925764309=229292722929251753637943825=21753637943825.\frac{3}{2292925} - \frac{1}{764309} = \frac{3\cdot764309 - 2292925}{2292925 \cdot 764309} = \frac{2292927 - 2292925}{1753637943825} = \frac{2}{1753637943825}.
  • Next: largest ≤ 21753637943825\tfrac{2}{1753637943825} is 1876818971912.5\tfrac{1}{876818971912.5}.

And so on…

What started as 5121\tfrac{5}{121} quickly exploded into denominators in the billions. The fraction itself wasn’t exotic. But the greedy expansion became grotesque.


Example B: 37\tfrac{3}{7}

Greedy steps:

  • Largest ≤ 370.428\tfrac{3}{7} \approx 0.428 is 130.333\tfrac{1}{3} \approx 0.333.

Subtract:

3713=9721=221.\frac{3}{7} - \frac{1}{3} = \frac{9 - 7}{21} = \frac{2}{21}.
  • Next: largest ≤ 221\tfrac{2}{21} is 111\tfrac{1}{11}.

Subtract:

221111=2221231=1231.\frac{2}{21} - \frac{1}{11} = \frac{22 - 21}{231} = \frac{1}{231}.

So:

37=13+111+1231.\frac{3}{7} = \frac{1}{3} + \frac{1}{11} + \frac{1}{231}.

Neat! This one ends quickly. The greedy method feels like magic here.

But you never know which way it will go: tidy or monstrous. That unpredictability is part of the pit.


Step 3: False Hope in Patterns

I started wondering: maybe there are formulas?

Yes, sometimes:

  • 2n=1n/2+1nn/2.\tfrac{2}{n} = \frac{1}{\lceil n/2 \rceil} + \frac{1}{n \cdot \lceil n/2 \rceil}.

  • 3n\tfrac{3}{n} has known formulas too.

But patterns fall apart fast. For instance:

417=15+130+1510.\frac{4}{17} = \frac{1}{5} + \frac{1}{30} + \frac{1}{510}.

Looks systematic. Then try 419\tfrac{4}{19}… and you’re in chaos.

I scribbled pages of attempts, trying to find clean rules. Nothing stuck.


Step 4: The Live Wires — Open Problems

That’s when I realized this wasn’t just a playground. Egyptian fractions touch open research.

  1. The 2/n Problem (still unsolved):
    For every integer nn, can 2n\tfrac{2}{n} be written as a sum of three unit fractions?
    Verified for vast ranges, but no proof.

  2. Erdős–Graham Conjecture (proved in 2003 by Erdős–Straus–Spencer team):
    If you partition the integers into finitely many classes, one class contains a finite subset whose reciprocals sum to 1. Egyptian fractions everywhere, hiding in Ramsey theory.

  3. Denominator Growth:
    How fast can denominators blow up in the worst case? The greedy algorithm guarantees a solution, but at the cost of numbers so huge they look absurd.

  4. Efficiency:
    What’s the minimal number of terms needed for a given pq\tfrac{p}{q}? Even simple fractions defy quick answers.

These are not solved by clever tricks. They’re still open territory.


Step 5: Climbing Out (Sort Of)

By the end of my descent, I had learned:

  • The greedy algorithm always finds a decomposition — but often drags you into enormous denominators.

  • Some fractions collapse beautifully, others expand hideously.

  • Egyptian fractions aren’t just historical curiosities; they’re tied to deep modern number theory.

The problem looks like a toy. In reality, it’s a pit that connects elementary arithmetic with unsolved conjectures.


Takeaway

What drew me into this pit was the illusion of simplicity. It looked like a problem about splitting candy bars. Instead, I met the Hydra of denominators, the chaos of greedy expansions, and open problems that mathematicians are still wrestling with.

That’s what The Problem Pit is all about: stepping into traps you didn’t know were traps.



Comments

Popular posts from this blog

Sharp Extremal Bounds for Angular Occupancy (Behind the Curtains)

you can find the full paper here First Attempts, and the Limits of Energy When I first began thinking about angular occupancy, I wasn’t looking for a brand-new problem. I was chasing a theme that has long fascinated me in discrete geometry: how do we measure the geometric richness of a finite set of points? This fascination is not unique to me. Erdős, way back in 1946, posed the distinct distances problem : given n points in the plane, how many distinct distances can they determine? That question alone gave birth to entire decades of work in combinatorial geometry. Later, Fishburn and Füredi asked about distinct angles , while Pach and Sharir studied repeated angles . Each time, the same underlying itch was being scratched: when you place points in the plane, what kinds of diversity can they generate? Why angles, why bins? It was natural to think of angles — after all, distances and directions had already been well studied. But if you go straight for “distinct angles,” you run in...

The Art of Goodbye

  The Art of Goodbye: How Relationships End and Why It Matters The friendship had been slowly dissolving for months. What used to be weekly coffee dates became monthly check-ins, then sporadic text messages, then silence. No fight precipitated the ending, no dramatic confrontation or betrayal. It simply... faded. One day you realized you hadn't spoken to someone who was once central to your life, and you weren't sure when the relationship had officially ended or even if it had. This ambiguous loss left you with a peculiar grief – mourning someone still alive, still accessible, but no longer present in your world. This experience is incredibly common yet rarely discussed. While we have cultural scripts for how relationships begin – meet-cutes, first dates, friendship origin stories – we have few models for how they end. We talk extensively about building connections but rarely about gracefully releasing them. This gap in our social understanding leaves many people unprepared ...

Getting Stuck: When Dijkstra Meets Negative Edges

  Getting Stuck: When Dijkstra Meets Negative Edges One of the joys (and pains) of computer science is when you take a tool you know, confidently apply it, and then watch everything break down in surprising ways. This happened to me recently when I decided to revisit shortest path algorithms — specifically, Dijkstra’s algorithm — only to get stuck in a swamp of negative edges. Setting the Scene The problem was classic: Given a directed, weighted graph and a source vertex, find the shortest path to all other vertices. This is the kind of problem that every CS student learns early, usually with Dijkstra’s algorithm. I already knew Dijkstra like an old friend: Keep a priority queue of distances. Always expand the node with the current smallest distance. Relax its edges. Simple, elegant, efficient ( O((V + E) log V) with a binary heap). So when I started coding a graph utility for my project — a tool to analyze transportation networks — I confidently plugged in D...