Bitcoin Forum
June 21, 2024, 10:53:24 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED== on: December 27, 2022, 06:01:06 AM
And finaly the #115 was found. Congratulations Zielar and Jean_Luc_Pons  Smiley We are all wondering which was the privkey  Wink

Many thanks!
A valid private key that is solution #115 has already been placed in the main post table.

for #115 , you've got the wrong date in the main post Smiley
I saved #115 on  0ctober 3rd the private key and timestamp and I never did find any other source before that, I may be wrong can I find the official record?
2  Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED== on: December 27, 2022, 04:28:02 AM
So he would have to be a special idiot to buy progress files and then resell them, reducing his chances. In addition, this offer is rather addressed to people / groups who have been working on 120 for a long time, for whom these files will significantly increase the chance of finding the key faster, and not for people who will try to earn money on it. I put it only because some time ago someone somewhere asked me about these files, but then after searching my devices and being aware of how much space it took - I decided that I had to delete them (and that's how I answered this person). Yesterday it turned out something else - so my offer landed here :-) Oh and I would like to point out that I did not undertake work on #120 and definitely will not undertake it, so the buyer has no worries that I will somehow I will compete in finding the key.

I had asked last year about said progress files. So I was one of those individuals. However, the issue now is, since you did not know if you had them, work was started but not in the 115 range. Maybe someone else who inquired about the files, started working in the 115 bit range and can use them.
Best of luck to all.
I have the key for Puzzle#115 saved in my files dated 10/03 with a timestamp....  My question is do you have a record of the date and time that #115 was found?  I see a lot of maybes and no exact source.  I would like to be able to learn the proper protocol for participating in challenges and disclosure if I where to be so lucky?
3  Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED== on: December 21, 2022, 12:58:22 AM
I did NOT just find 66
Turns out it was a label 66 not actually puzzle #66 
I got excited 😆 sorry
Good prove it making a signature here: https://reinproject.org/bitcoin-signature-tool/#sign

Regards!
4  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: November 26, 2022, 08:23:18 PM
I get the same performance as you, but EC_POINT_add isn't the slowest step, it's the call to EC_POINT_point2oct.

So what if I am a newbie just glance at please?

x = int('11db93e1dcdb8a016b49840f8c53bc1eb68a382e97b1482ecad7b148a6909a5c, 16) y = int('b2e0eaddfb84ccf9744464f82e160bfa9b8b64f9d4c03f999b8643f656b412a3', 16)

point = ecdsa.ellipticcurve.Point(SECP256k1.curve, x, y) pubkey = Verifyingkey.from public point(point, SECP256k1)

def verify signature(hash, signature):

17 global pubkey

return pubkey.pubkey.verifies(hash, signature)

Do you know why EC_POINT_point2oct is slow? I called EC_POINT_get_affine_coordinates_GFp instead, but they seem to do the same thing. If EC_POINT_add stores the point in Cartesian coordination (X-Y), will extracting the public key be a trivial task?

Guys with brute force we won't go anywhere.

How precise is this formula?

I think all of us know that brute force is not viable for sure, but it is fun to estimate how long it will take to break the 51st, 52nd, ... addresses.

That division isn't the conventional division. It has perfect precision (http://www.johannes-bauer.com/compsci/ecc/#anchor07).

Well we wont get 5 TH/s or anything close for sure, but if we were able to generate 100 million keys per second we would break the #51 in about 3.5 months... And I believe it will be very hard to get to 100 million / s even with GPU.

Yes of course we can try it for the fun, but it wont be much fun when you get home and your GPU is burning plus your electricity bill Cheesy

But of course if your formula brings down the range of keys to generate then we can have some chance.

So, basically I was wrong because we have to calculate λ to add the two points.

If you find the right formula can you post the results for each address so we know exactly what ranges we can count with?
5  Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED== on: November 16, 2022, 12:10:46 AM


import ecdsa

1 import hashlib

Important enough, that I may be known openly."""

from ecdsa import VerifyingKey, SECP256k1

raw_message = """I do not want to be public, but, there is an issue with Segwit. If it is not fixed, there will be nothing and I would have failed. There is only one way that Bitcoin survives and it is important to me that it works.

x = int('11db93e1dcdb8a016b49840f8c53bc1eb68a382e97b1482ecad7b148a6909a5c, 16) y = int('b2e0eaddfb84ccf9744464f82e160bfa9b8b64f9d4c03f999b8643f656b412a3', 16)

point = ecdsa.ellipticcurve.Point(SECP256k1.curve, x, y) pubkey = Verifyingkey.from public point(point, SECP256k1)

16 def verify signature(hash, signature):

17 global pubkey

return pubkey.pubkey.verifies(hash, signature)

If this helps.

1JdrncTCNZyATqkWpWavjkNGWvXmymvAMb






hello guys, can someone tell me how to change DP modulo in this kangaro's version " https://github.com/JeanLucPons/Kangaroo "
i want to set it at  2^30

Will you be compiling yourself?


yes i use my GPU but the kangoros jump are small 2^20 is not enough so i asked how to change it in files so it jump 2^30
Are you searching in the 2^40 range? The avg jump size is determined by the rangePower. It's set to rangePower / 2 + 1.

It's in the Kangaroo.cpp file, around the 730s/740s lines (depending if you've made mods or the version you are using)

code:
Code:
void Kangaroo::CreateJumpTable() {

#ifdef USE_SYMMETRY
  int jumpBit = rangePower / 2;
#else
  int jumpBit = rangePower / 2 + 1;
#endif
6  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 29, 2022, 06:47:02 AM
I have found several of these puzzles including the very last one.  But I don’t know how to get $ inside of them seriously
7  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 29, 2022, 05:45:54 AM
Hi guys,

In continuation to this thread: https://bitcointalk.org/index.php?topic=1305887.0

While playing around with my bot, I found out this mysterious transaction:

https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

those 32.896 BTC were sent to multiple addresses, all the private keys of those addresses seem to be generated by some kind of formula.

For example:

Address 2:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU74sHUHy8S
1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
Biginteger PVK value: 3
Hex PVK value: 3

Address 3:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU76rnZwVdz
19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
Biginteger PVK value: 7
Hex PVK value: 7

Address 4:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU77MfhviY5
1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
Biginteger PVK value: 8
Hex PVK value: 8

Address 5:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Dq8Au4Pv
1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
Biginteger PVK value: 21
Hex PVK value: 15

Address 6:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Tmu6qHxS
1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
Biginteger PVK value: 49
Hex PVK value: 31

Address 7:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7hDgvu64y
1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
Biginteger PVK value: 76
Hex PVK value: 4C

Address 8:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU8xvGK1zpm
1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
Biginteger PVK value: 224
Hex PVK value: E0

Address 9:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUB3vfDKcxZ
1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
Biginteger PVK value: 467
Hex PVK value: 1d3

Address 10:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUBTL67V6dE
1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
Biginteger PVK value: 514
Hex PVK value: 202

Address 11:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUGxXgtm63M
1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
Biginteger PVK value: 1155
Hex PVK value: 483

Address 12:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUW5RtS2JN1
1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
Biginteger PVK value: 2683
Hex PVK value: a7b

Address 13:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUspniiQZds
1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
Biginteger PVK value: 5216
Hex PVK value: 1460

Address 14:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFVfZyiN5iEG
1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
Biginteger PVK value: 10544
Hex PVK value: 2930

and so on...

until the addresses 50 (1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk) it was already cracked by someone.

Any ideas what's the formula behind the generation of these addresses?

Address 2, pvk decimal value: 3
Address 3, pvk decimal value: 7
Address 4, pvk decimal value: 8
Address 5, pvk decimal value: 21
Address 6, pvk decimal value: 49
Address 7, pvk decimal value: 76
Address 8, pvk decimal value: 224
Address 9, pvk decimal value: 467
Address 10, pvk decimal value: 514
Address 11, pvk decimal value: 1155
Address 12, pvk decimal value: 2683
Address 13, pvk decimal value: 5216
Address 14, pvk decimal value: 10544
Address 15 and after, pvk decimal value: ?

The prize would be ~32 BTC Smiley

EDIT: If you find the solution feel free to leave a tip Smiley 1DPUhjHvd2K4ZkycVHEJiN6wba79j5V1u3
i also found this one just now Page #1.4947678577364E+75 out of #2.573157538607E+75 (58.0908%).
8  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: October 29, 2022, 05:30:55 AM
So how secure are satoshi's coins which were mined directly and put in a public address instead of a BTC address.

Because you are saying that reusing addresses is not good because its not as secure but if this was the case why wouldn't this person who is solving all these puzzles for less than <1 BTC instead try and crack Satoshi's early coins which are sitting in all those public key addresses?

I think why its faster is because the search space is much small compared to the entire 128 bit search space, so its still safe to re-use addresses since as far as we know ECDSA hasn't been cracked yet or some exploit found.
Few people deal with this issue, as soon as it is put on stream then This  standard ECDSA will quickly split. Roll Eyes Roll Eyes Roll Eyes
because I don’t know how, but I’m responsible for about  3 puzzles I have not received any Of the funds because I don’t know how to do it
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!