Quote from: ranochigo on December 24, 2020, 04:06:34 PM

Code:

30450221009caa9cfc1d305536b1144e1e90b01212f1d68101b9f6a5738bb8a3bbc48a587702203c225b31571ae1ef20d544be97566c0e09d44adc4199ef684e1313a31cf11ee701
30450221008ce6c48db27fc84eedb200377089a21f7e05f6a87f8e0db65c7e24bb151cd2ce022028f017a89c941d69fe4b84e190bea7fde1f822da762dac0e0d52bdce33174a6601
30440220535c98daf8fff2a1d7a1ffdded07b07885ced19cf87e99dc0914df2855c4659502204217ae44efa956120a21cfd6fcea259728255c2dd555ddc8d31ccda53d77231f01
30440220628148e928b3a4dd0497b92c475d6a2bce1c0f88f8f26e6aa562a01edeefac0a02207fbe0fef95e02c6703a86ddcc21a9782f32f38058e49f199258bb1e3fb1c5e8601

Relevant signatures for those who wants to give it a go. There's nothing similar about the signature, which is common for reuse r values. Johoe posted it here[1] years back. And for this, AFAICT, isn't vulnerable with the reuse r values. Guess you're just trying to steal some coins?

[1] https://bitcointalk.org/index.php?topic=1431060.0

Yeah, these signatures aren't reusing R at all, or it would be glaringly obvious.

It's even stated in the thread that the owner of the compromised addresses ( keys) should sign for this address, because this one isn't compromised.

@OP what are you doing? Where did you get this address from?

Quote from: Hope451 on December 24, 2020, 12:24:02 PM

But I dont know how find msghash1 mshhash2 what is it?in ruby script,I already entered sig1 hex sig2 hex,it is r1 r2

if a signature is in DER format, you can decode it like this

Code:

30450221009caa9cfc1d305536b1144e1e90b01212f1d68101b9f6a5738bb8a3bbc48a587702203c225b31571ae1ef20d544be97566c0e09d44adc4199ef684e1313a31cf11ee701

Code:

30 <length> 02 <r length > <rhex> 02 <s length> <s hex>

so for the above sig,

30450221009caa9cfc1d305536b1144e1e90b01212f1d68101b9f6a5738bb8a3bbc48a587702203c225b31571ae1ef20d544be97566c0e09d44adc4199ef684e1313a31cf11ee701

lent