orbit23

Hey all, I stumbled upon a pretty intriguing case related to the Bitcoin address "1LN4yp6rQALjwg53SKsi44teq1fp2v5wqR", which reused the same nonce k in two separate transactions signed with the same private key.…

amaclin1, Thanks, I understand now. As mentioned earlier, all these addresses are compromised. For one address containing just over 2 BTC, there are 6 RSZ signatures in total. The second signature for this address…

hello send me a message

amaclin1 Have you ever seen a similar exploitable case or an optimized brute-force method for this kind of situation?

amaclin1, these P2PKH addresses are compromised no matter what—around 4 BTC is at risk. The transactions accidentally reused the R value between addresses due to a biased PRNG. I’m looking for a brute-force method to…

In the scenario I mentioned earlier in the thread, where the same nonce 𝑟 is reused between different public keys, I have noticed that sometimes we observe two instances of reuse between two keys, or even three…

I suppose that A1, A2, A3, A4, A5, A6, A7, A8, etc. are children of Ax, as the transactions from A1, A2, and A3, which shared the same nonce as Ax, were made towards Ax on the same date, sometimes even within the same…

here’s the latest news on the addresses I’m currently working on. I’m trying to determine the possible links between them. I don’t know any of the private keys (d1 to d7), nor k1, k2, or k3 — which I assume are large.…

Alright, thank you for your help. I managed to recover the dB key! It turns out it was using the same K, but actually -K (so the same R, but with a negative K). Now, I’ve identified other pairs of signatures (P2PKH…

mcdouglasx I only have the private key for Ax; I didn't recover the ones that shared the nonce with Ax because they are empty. The addresses that interest me are those that shared between themselves sending to Ax,…

Sometimes in the same transaction Trx 1 : Ax: 1AxP2pkhFakeAddressExample1111>> A1: 1A1P2pkhFakeAddressExample2222>> A2: 1A2P2pkhFakeAddressExample3333>> Ax: 1AxP2pkhFakeAddressExample1111 A3:…

more context: Ax: 1AxP2pkhFakeAddressExample1111 a1: 1A1P2pkhFakeAddressExample2222 a2: 1A2P2pkhFakeAddressExample3333 a3: 1A3P2pkhFakeAddressExample4444 a4: 1A4P2pkhFakeAddressExample5555 a5:…

Hey folks, I stumbled upon something strange while looking into some old addresses that used the same nonce k (the same R value in the signature), but with different private keys. I found an original thread about it…

Hey folks, I stumbled upon some P2PKH address pairs that were generated in a cloned and biased virtual setup, which caused them to use the same nonce r. Here's what I found: Transaction 1 Nonce (r) = 5c16a3fbafc1ef0…

Hey folks, I was digging into some transactions with P2PKH addresses and noticed that the nonce r was reused across different public keys. What’s wild is that it looks like all these addresses came from a cloned VM…

Hey folks, I've noticed that the k values look a bit too predictable and deterministic. R1 = 0x5660647957179a737ee9f43d69ea7923ed179680acaea311986ba7bde67dd321 R2 =…

I came across a situation with several Bitcoin P2PKH transactions where the same ECDSA nonce r is being reused for different private keys. The addresses are mathematically linked, and the total amount at stake is about…

Hey folks, I’m still trying to crack a puzzle I found here. Right now, I’m digging into a specific key that could make solving part of the puzzle way easier. This key’s address is empty at the moment, and I’ve gathered…

Hey all, Just reposting my issue with some updates, but I'm still at a standstill. Anyone got ideas or solutions? So here’s the deal: We’ve got 9 signatures and 7 private keys: d1, d2, d3, d4, d5, d6, d7, along with 3…