I've modified the r-scan Python code to look beyond the 50 Txs the Blockchain.info API usually returns.

My modifications take all the r values for my address and look for duplicates, but a commented out section of code makes mention of just checking the TxIDs which have more than one input script.

Is it only Txs with multiple inputs that are the problem?

1 Answer 1


Any reused nonce is a problem, it's not restricted to a single transaction.

No competent software will ever reuse nonces accidentally, so using a scanning script like that is just ruining your privacy for no real benefit. Bitcoin Core, Electrum and Armory all use RFC 6979 deterministic nonces so there is no room for RNG failure in these cases, though any software faulty enough to fall at that hurdle will have used the same RNG to make the private keys as well.

  • 1
    I have to add that reused nonce while signing with differrent privkeys is also a problem. Even in different crypto-currencies
    – amaclin
    Jun 28, 2015 at 16:30
  • @amaclin I think you're wrong (but please correct me if I'm wrong). Given two signatures with identical r values signed by different privkeys, how can you calculate the k value (the nonce)? (Although if you do have the k value, you can find the privkey which signs any message using that same k (and therefore the same r) value.) Jun 28, 2015 at 21:39
  • 1
    k = ( digest + r * privkey ) / s If I know one privkey, I can find k and another privkey
    – amaclin
    Jun 29, 2015 at 5:43
  • 1
    @amaclin Thanks, but I was rather assuming that the privkeys were, well, private. I was trying to say that you need either a compromised privkey or a compromised k (either of which initially requires two sigs with the same privkeys and ks) before you can start looking for related "chains" of privkeys/ks. Still, your point about avoiding k reuse (unless the message/z and privkey are the same) is certainly good advice.... Jun 29, 2015 at 23:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.