Skip to main content
← Back to Cryptography samples
🔐Cryptography·15 min·Sample Lesson

Elliptic Curve Cryptography

When your phone sets up a secure connection to a website, it often does the equivalent of a 3072-bit RSA key's worth of security using a key only 256 bits long. That's roughly 12 times smaller for the same protection level. The reason is a strange piece of math: points on a curve shaped like y² = x³ + ax + b, where you can "add" two points together and get a third point back on the same curve. This is elliptic curve cryptography (ECC), and it now secures most of the encrypted web, Bitcoin wallets, and Signal messages.

What You'll Learn

- What an elliptic curve is and what point addition means geometrically - Why the "elliptic curve discrete logarithm problem" is hard to reverse - How ECC achieves RSA-level security with much shorter keys - Where ECC is actually used today (TLS, Bitcoin, Signal)

The Curve and Point Addition

An elliptic curve for cryptography has the form y² = x³ + ax + b (with constants a and b chosen so the curve has no sharp cusps or self-crossings). Pick any two points, P and Q, on the curve. Draw a straight line through them; it will hit the curve at exactly one more point. Reflect that point across the x-axis, and you get P + Q, a third point that's also on the curve. This operation, called point addition, is the entire engine of ECC. Now do something odd: add a point P to itself, over and over, k times. The result is a new point, often written kP. This repeated addition is called scalar multiplication, and it's fast to compute even for enormous k, using a doubling trick similar to fast exponentiation.

The One-Way Trap Door

Here's the trick that makes it secure: if I show you the starting point P and the final point kP, figuring out the number k is called the elliptic curve discrete logarithm problem (ECDLP), and for a well-chosen curve it is believed to require roughly 2^128 operations to crack for a 256-bit key — computationally impossible with any known classical algorithm, even at datacenter scale. So your private key is just a giant random number, k. Your public key is the point kP, computed using a curve and starting point (called the base point) that are publicly standardized. Anyone can verify signatures using your public point, but nobody can work backward to find your secret number k.

Why Smaller Keys Matter

RSA's security relies on the difficulty of factoring huge numbers, and that problem gets easier relative to key size faster than ECDLP does. To match the strength of a 256-bit ECC key, RSA needs roughly a 3072-bit key. Smaller keys mean less data to transmit, faster computation, less battery drain, and easier storage in tiny devices. That's why curve25519 (a specific, widely-audited elliptic curve) is the workhorse behind Signal's end-to-end encryption and behind SSH key exchange on most modern servers.

Named Curves You'll See in the Wild

secp256k1 is the exact curve Bitcoin and Ethereum use for wallet key pairs. curve25519 (created by Daniel J. Bernstein in 2005) is used in Signal, WhatsApp, and modern SSH. P-256 (also called secp256r1) is a NIST-standardized curve used across much of TLS/HTTPS today.

In elliptic curve cryptography, what is the actual secret (private key)?

Why can ECC use a 256-bit key to match the security of a 3072-bit RSA key?

🎯

Trace Point Addition by Hand

Using graph paper or a free online tool (like a Desmos graph of y² = x³ - x, a real elliptic curve), plot two points P and Q on the curve. Draw the straight line through them, find where it crosses the curve a third time, then reflect that point over the x-axis to find P + Q. Deliverable: a labeled sketch showing P, Q, the line, the third intersection, and the final result P + Q, with coordinates marked for each point.

A Real-World Failure

In 2010, Sony was found to be reusing the same random number k for every PlayStation 3 firmware signature instead of generating a new one each time. That single mistake let researchers solve for Sony's entire private signing key algebraically, letting anyone sign homebrew firmware as if it were official Sony code. The math was never broken — the implementation was.

Want to keep learning?

Sign up for free to access the full curriculum — all subjects, all ages.

Start Learning Free
Elliptic Curve Cryptography | Free Sample | HYVE CARES | HYVE CARES