It is a well-known secret that ECDSA needs to be set up properly, else the private key could be revealed. In the worse case, Eve could reveal Alice’s Bitcoin private key from the ECDSA signatures. One of the weaknesses is where the same nonce value is used for different messages. So let’s crack.

With an ECDSA signature, we sign a message with a private key (*priv*) and prove the signature with the public key (*pub*). A random value (a nonce) is then used to randomize the signature. Each time we sign, we create a random nonce value and it will produce a different (but verifiable) signature. The private key, though, can be discovered if Alice signs two different messages with the same nonce. In this case, we will use SECP256k1 (and which is used in Bitcoin).

In ECDSA, Bob creates a random private key (*priv*), and then a public key from:

Next, in order to create a signature for a message of *M*, he creates a random number (*k*) and generates the signature of:

The signature is then (*r*,*s*) and where *r* is the x-coordinate of the point *kG*. *H*(*M*) is the SHA-256 hash of the message (*M*), and converted into an integer value. Now let’s say we have two messages (*m*1 and *m*2) and have hashes of:

Now let’s say that Alice signs the messages with the same private key (*priv) *and the same nonce (*k)*, we can…