Search content
Sort by
Showing 20 of 20 results by ActiveC
Re: [CHALLENGE] 5 BTC Reward – ECDSA Structured Nonce k Puzzle (1M Signatures)
Quote
Nice & Simple Logic.
@jvaimamu: Is this still a challenge, or you gave up, since nobody will make you billionaire like this ?!
I still see the target pubkey address empty, that's why I ask 
Re: [CHALLENGE] 5 BTC Reward – ECDSA Structured Nonce k Puzzle (1M Signatures)
I don't want anything, I just showed the OP that anybody can do that, exactly as you described it!
The OP did similar, did choose the values to fit the math, hashless signature. This is why I was asking for a signature from the public key he posted or a plain text "z" he could show, not only the hash of it
I don't waste time with useless things - so not solving anything regarding this "challenge" either, but I feel the whole game goes for finding a related key, which from the currently crafted r,s,z pairs won't happen anyway!
The OP did similar, did choose the values to fit the math, hashless signature. This is why I was asking for a signature from the public key he posted or a plain text "z" he could show, not only the hash of it
I don't waste time with useless things - so not solving anything regarding this "challenge" either, but I feel the whole game goes for finding a related key, which from the currently crafted r,s,z pairs won't happen anyway!
Re: [CHALLENGE] 5 BTC Reward – ECDSA Structured Nonce k Puzzle (1M Signatures)
⭐ Merited by jvaimamu (1)
There we go jvaimamu:
r = 0xef12ac841e7c99482a7f732bec4ea634b36b08642496bf8f7bd057519566ff99
s = 0x10ed537be18366b7d5808cd413b159ca0743d4828ab1e0ac4402073b3acf41a8
z = 0xc9b70b2c7147a867a3401ea0284fc3a1554bcb7e9f8094ae0ed7dc22a9d4290e
Pubkey: 04c1c1e912c51061424286bdea075e0a19a96be1869566f4ebc9ea3e565f9c334d1779371fd313e dc2955b14f3eaabf8af027f77a7b3e1e908839d4f7ee81aef28
What now?!
r = 0xef12ac841e7c99482a7f732bec4ea634b36b08642496bf8f7bd057519566ff99
s = 0x10ed537be18366b7d5808cd413b159ca0743d4828ab1e0ac4402073b3acf41a8
z = 0xc9b70b2c7147a867a3401ea0284fc3a1554bcb7e9f8094ae0ed7dc22a9d4290e
Pubkey: 04c1c1e912c51061424286bdea075e0a19a96be1869566f4ebc9ea3e565f9c334d1779371fd313e dc2955b14f3eaabf8af027f77a7b3e1e908839d4f7ee81aef28
What now?!
Re: [CHALLENGE] 5 BTC Reward – ECDSA Structured Nonce k Puzzle (1M Signatures)
Really? Post a signature from the 5BTC reward wallet at least, it shouldn't be hard
Convince us by publishing the first message "z" in plain text, not only the hash of it...
My guess is that this has nothing to do with any quantum-resistant development! Prove me wrong!
Spectacular would be to see a signature from the wallet of the pubkey you published
Genius, trying to make others solve anything for you, but I doubt it will work!
My opinion is that you are interested only about the private key of: 0337cb099a32bdc5e3b790b0ad94a2c0d1184a1bba7a2b688223a183ff7bdbdf33
End of story: that could be in relation with your real target?!
!!! Thanks, but no thanks!!!
Convince us by publishing the first message "z" in plain text, not only the hash of it...
My guess is that this has nothing to do with any quantum-resistant development! Prove me wrong!
Spectacular would be to see a signature from the wallet of the pubkey you published
Genius, trying to make others solve anything for you, but I doubt it will work!
My opinion is that you are interested only about the private key of: 0337cb099a32bdc5e3b790b0ad94a2c0d1184a1bba7a2b688223a183ff7bdbdf33
End of story: that could be in relation with your real target?!
!!! Thanks, but no thanks!!!
I wonder why the original OP doesn't reply at all?!
Maybe @RetiredCoder will
Re: [CHALLENGE] 5 BTC Reward – ECDSA Structured Nonce k Puzzle (1M Signatures)
⭐ Merited by garlonicon (1)
Post a signature from the 5BTC reward wallet, it shouldn't be hard
Hi there!
It looks like you all are crazy for nonces and signatures, so I have some special values for you
It looks like you all are crazy for nonces and signatures, so I have some special values for you
Code:
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x24c8a42e8fe11d670633fa66ebedb1672c71a517a30cbbaa9e14f2d5a15a3783
z=SHA256('This is test 1.')
PubKey=0x3e42b3151f310f5f417f11b4c32d8360b22109dcc6432339243332b56cd596de, 0x7903116327cab6891b810588e4c909273c7eb013aea2162fa63afa1f11562b3a
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x768a0e3b0cfb3c8d9b7899f59f480555176ef25eefa1e96d3ac575ba4ffe85fd
z=SHA256('This is test 2.')
PubKey=0xc79fa242694e3148c8d50e667010e0c221f6004d108692c5040ff139595ed081, 0x525bd76c21c8e2d45725a378c973a646d5971acd8f240322e5f1fdf0ed4f8589
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0xd17c5ed9fb37692cd152f381c4a3f16a896f96d26100310fe818d6963c402b25
z=SHA256('This is test 3.')
PubKey=0xc03657988e2baf31a1a1061a87fa3da20f166dc8a22c02658f6d325dec722d84, 0x97ffbac6bec2de2b8d9f9bcaeced8e56abdd0b3996b48153cf0a1a92dc2d5529
Btw. I think that those who do serious research of this topic do not need your script, but all contributions are welcome, of course.s=0x24c8a42e8fe11d670633fa66ebedb1672c71a517a30cbbaa9e14f2d5a15a3783
z=SHA256('This is test 1.')
PubKey=0x3e42b3151f310f5f417f11b4c32d8360b22109dcc6432339243332b56cd596de, 0x7903116327cab6891b810588e4c909273c7eb013aea2162fa63afa1f11562b3a
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x768a0e3b0cfb3c8d9b7899f59f480555176ef25eefa1e96d3ac575ba4ffe85fd
z=SHA256('This is test 2.')
PubKey=0xc79fa242694e3148c8d50e667010e0c221f6004d108692c5040ff139595ed081, 0x525bd76c21c8e2d45725a378c973a646d5971acd8f240322e5f1fdf0ed4f8589
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0xd17c5ed9fb37692cd152f381c4a3f16a896f96d26100310fe818d6963c402b25
z=SHA256('This is test 3.')
PubKey=0xc03657988e2baf31a1a1061a87fa3da20f166dc8a22c02658f6d325dec722d84, 0x97ffbac6bec2de2b8d9f9bcaeced8e56abdd0b3996b48153cf0a1a92dc2d5529
JohnnyTX, thank you, all these look very special, indeed! Let's play some more:
r=0x9bd63465dcad42dc46e702e8d82d8f0006db4048d1b55f24dc6bf9feffcef0d1
s=0xc3e9b322e9c1e6e7d338753b9688e1740765094085725f34f5d4cfe731190eca
z=0x8749f9a34fbe328e820dcb46cd7811b3778e08b8171d9ef314ad24815dae679c
PubKey=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6, 0x49f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f
Quote
Well, then I have two more for you, but this public key doesn't point to the puzzle #130 it seems...
# Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
# Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
Code:
# rsz 1
r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
With k2 = k1 + 1.r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
Private key: 0x37ed68dbebdb0963a45d2831709d58cae674db2fd5aa48c09aee364cbdfc5de8
Nonce k1: 0x443a78852adc3739b5aabadc32268c1a3bc6add7ee1ec5c07d9f1531ca4f361f
Nonce k2: 0x443a78852adc3739b5aabadc32268c1a3bc6add7ee1ec5c07d9f1531ca4f3620
@JohnnyTX please allow messages from Newbies or contact me, thank you!
-----BEGIN BITCOIN SIGNED MESSAGE-----
RetiredCoder was right
-----BEGIN SIGNATURE-----
1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua
H7n0u91l2kntxg9rTFleDFlqTpVo3jVlguGF1T9vAfORf/GpCqtplt+VYrYR5HL3oKHkAijYFiNFdvVHXJHf+rQ=
-----END BITCOIN SIGNED MESSAGE-----
RetiredCoder was right
-----BEGIN SIGNATURE-----
1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua
H7n0u91l2kntxg9rTFleDFlqTpVo3jVlguGF1T9vAfORf/GpCqtplt+VYrYR5HL3oKHkAijYFiNFdvVHXJHf+rQ=
-----END BITCOIN SIGNED MESSAGE-----
Hmm, it's strange
Please allow me in your setting to message you or message me, it is not about this mini-puzzle
No rude messages here, I remove them.
Thank you, keep it clean please, most of the persons (some looking newbies) are here to learn, not to fight with mongrels
I feel it in the air that we are close to solving it, just we don't consider something really important, which could lead to some relation. I don't ask you (OP) to give hints, but users who attend this talk should continue to brainstorm...
For now we have these, feel free to extend with ideas (we can never know when something is useful, even if it looks a bad idea):
- 7 pairs of R,S,Z,
- a quote from Jules Verne's Around the World in Eighty Days
- the public key (which was already public, but plays an important role)
Yes, you should have some understanding of ECDSA signature vulnerabilities.
2 most common vulnerabilities are repetitions of K for the same private key and weak KWe have only 2 signed messages and their signature r does not match, only the weak K remains.
I checked 02/03838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc in the 80-bit range it is not there.
sha256 from the message also does not reveal r, as well as double hashing.
The rabbit hole is too deep. I'm tired))
6 signatures in total, not only 2, you find another 4 on the blockchain
LLL ?!7
Enlighten us please, 2 been here on the forum, another 4 can be extracted from the withdrawal tx, which is he 7th?!
The one that allowed the private key to be searched, e.g. the first tx out.
Yes, true, still not enough for Lattice attack, unless some weak K, which RetiredCoder affirmed it is not!
Who knows any other signature vulnerabilities which can be exploited with a small number of R,S,Z pairs?
Yes, you should have some understanding of ECDSA signature vulnerabilities.
2 most common vulnerabilities are repetitions of K for the same private key and weak KWe have only 2 signed messages and their signature r does not match, only the weak K remains.
I checked 02/03838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc in the 80-bit range it is not there.
sha256 from the message also does not reveal r, as well as double hashing.
The rabbit hole is too deep. I'm tired))
6 signatures in total, not only 2, you find another 4 on the blockchain
LLL ?!7
Enlighten us please, 2 been here on the forum, another 4 can be extracted from the withdrawal tx, which is he 7th?!
Yes, you should have some understanding of ECDSA signature vulnerabilities.
2 most common vulnerabilities are repetitions of K for the same private key and weak KWe have only 2 signed messages and their signature r does not match, only the weak K remains.
I checked 02/03838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc in the 80-bit range it is not there.
sha256 from the message also does not reveal r, as well as double hashing.
The rabbit hole is too deep. I'm tired))
6 signatures in total, not only 2, you find another 4 on the blockchain
LLL ?!Same K or weak K would be too easy
This riddle is just one step more complex.
This riddle is just one step more complex.
I play around with Jules Verne now, but if you have better ideas, share it
Guys, I'm bored today again, so let's have some fun: a mini-puzzle for puzzle #130.
As you requested, this time it's a bit more challenging
Message: Anything one man can imagine, other men can make real
Signature: IIONt3uYHbMh+vUnqDBGHP2gGu1Q2Fw0WnsKj05eT9P8KI2kGgPniiPirCd5IeLRnRdxeiehDxxsyn/VujUaX8o=
There is about 700$ in BCH there, so hurry up!
And thanks to creator of original puzzles (Satoshi??) for a lot of fun!
PS. No BS here please, I will remove it.
PPS. For history, previous mini-puzzle is here: https://bitcointalk.org/index.php?topic=5518896
As you requested, this time it's a bit more challenging
Message: Anything one man can imagine, other men can make real
Signature: IIONt3uYHbMh+vUnqDBGHP2gGu1Q2Fw0WnsKj05eT9P8KI2kGgPniiPirCd5IeLRnRdxeiehDxxsyn/VujUaX8o=
There is about 700$ in BCH there, so hurry up!
And thanks to creator of original puzzles (Satoshi??) for a lot of fun!
PS. No BS here please, I will remove it.
PPS. For history, previous mini-puzzle is here: https://bitcointalk.org/index.php?topic=5518896
Now yes, I liked it, a difficult puzzle lol, don't give any more tips to this bunch of parasitic worms, no @
RetiredCoder
Did you look in the mirror lately?
Just be polite, that's how it works out the best! If you read up, I gave my opinion on solving and a few more valid R and S values for the address, I didn't ask for any hint!I wish to talk with @RetiredCoder about how to change SOTA way for even faster, that is why I asked him to contact me. ...and I didn't expect a lamer to troll, so don't be one!
The main vulnerability of signatures is the use of the same value of K, which gives the same value of r.
for the first message the values of r and s were:
r 0xde97092bfb7c02148a827b4f8b62db1e189a739c77815799df5e6fb35ae88a1f
s 0x3f4fa38bcbb17615446fabc6fbebceefbb7d052eca9ce136b3a4a67b7f0d4f42
for the second message the values of r and s were:
r 0x838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc
s 0x288da41a03e78a23e2ac277921e2d19d17717a27a10f1c6cca7fd5ba351a5fca
I don't see the same r values here, maybe I'm being stupid.
for the first message the values of r and s were:
r 0xde97092bfb7c02148a827b4f8b62db1e189a739c77815799df5e6fb35ae88a1f
s 0x3f4fa38bcbb17615446fabc6fbebceefbb7d052eca9ce136b3a4a67b7f0d4f42
for the second message the values of r and s were:
r 0x838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc
s 0x288da41a03e78a23e2ac277921e2d19d17717a27a10f1c6cca7fd5ba351a5fca
I don't see the same r values here, maybe I'm being stupid.
@Etar where did the first r and s come from? I didn't find the same values
From the message RetiredCoder posted earlier with the message "RetiredCoder is a winner for 120,125,130".
The main vulnerability of signatures is the use of the same value of K, which gives the same value of r.
for the first message the values of r and s were:
r 0xde97092bfb7c02148a827b4f8b62db1e189a739c77815799df5e6fb35ae88a1f
s 0x3f4fa38bcbb17615446fabc6fbebceefbb7d052eca9ce136b3a4a67b7f0d4f42
for the second message the values of r and s were:
r 0x838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc
s 0x288da41a03e78a23e2ac277921e2d19d17717a27a10f1c6cca7fd5ba351a5fca
I don't see the same r values here, maybe I'm being stupid.
for the first message the values of r and s were:
r 0xde97092bfb7c02148a827b4f8b62db1e189a739c77815799df5e6fb35ae88a1f
s 0x3f4fa38bcbb17615446fabc6fbebceefbb7d052eca9ce136b3a4a67b7f0d4f42
for the second message the values of r and s were:
r 0x838db77b981db321faf527a830461cfda01aed50d85c345a7b0a8f4e5e4fd3fc
s 0x288da41a03e78a23e2ac277921e2d19d17717a27a10f1c6cca7fd5ba351a5fca
I don't see the same r values here, maybe I'm being stupid.
This is why I said that this can be solved only if the relation between the nonces are known
And here are some more r and s values:
r 0x1b6ab2549e885f738c89d8d57536e1a73cbeb9378630bb78e216b9b67f870eed
s 0x51c726a81cb1eef5396652f2d20187ca7be319d712501ba145a7ad6c0abdc4a9
r 0x72eb5d544fffa7db8bb197e0325c04ae275aa59f3698356ec259bb2efc5a2b30
s 0x3c2a50a80b05550a0af8f5b61006dea217630123b61ce3bfc391ef29286904ed
r 0x1a4f32a50802cf0d934af5fb73d96f097f39370124672c2fdea465ed99950b84
s 0x2a0b1ae7ec8b1f570c174c03a3fb90282583b52463954cc3da6633de142693f5
r 0x5ad3dea7329c9c3b1af267d4f2ef9cbd7806e31b2a67c733659ece873d428103
s 0x597007c96a01d437054d33432b40e7c8000508dd1b883b68fdeccf523ac4804a
Still, without relations of the nonces, I don't see any way to compute the private key.
@RetiredCoder: please message me, I can't message you because of your message settings
@RetiredCoder: Since you provided 2 (yes, 2 ) valid signatures for the same address, my humble opinion is that this current mini-puzzle can be solved only if you also leak the relation between the K1 and K2 nonces. 
) valid signatures for the same address, my humble opinion is that this current mini-puzzle can be solved only if you also leak the relation between the K1 and K2 nonces.