== Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==

[digaran]

even if he does not intervene with his nickname it seems that he has read and listened to you digaran making it even more attractive

#66 and #67 should not last long because it becomes very interesting (profitable) to rent a strong computing power to reach them

Lol, honestly he did over and beyond my expectations, this is good though, as it will attract more serious people, however I was thinking about moving 1000 BTC to a high bit range key, and I'd imagine the actual scientists would be interested to solve a problem in order to get at least $30M.

Though that would be counter intuitive right?😉

I can not imagine the face of the #120 solver when he realized prizes were ten folded,  Satoshi could have been waiting for it to be solved to increase the amount for the rest of the keys though.🤣

[warui]

this is soo good   OMG guys its now my fulltime job

[digaran]

Is there gonna be an updated topic saying 900 bitcoin puzzle or what?

[ProjectSe7en]

Is there gonna be an updated topic saying 900 bitcoin puzzle or what?

I say that we should not make noise, only those of us who are already aware.

 

[cryptoDEADBEEFFFFF]

Is there gonna be an updated topic saying 900 bitcoin puzzle or what?

I say that we should not make noise, only those of us who are already aware.

 

Human greed is under the test right now

[678AFDB0]

I think the real question is who withdrew 2600 USD from key 0x01 in under six minutes

[cryptoDEADBEEFFFFF]

I think the real question is who withdrew 2600 USD from key 0x01 in under six minutes

I am sure that are bots watching the mempool of probably multiple chains.. If it's done on ETH it should disappear as well.

[racminer]

Where to find source for zielar's latest vanitysearch the site http://zielar.pl/vslinux is not longer accessible.

[noecp]

#125 need 2^63.10 ops

23330 days (559920 hours) of work one RTX 3090 (4.8 GKey/s) modified kangaroo

1 hours price is $0,117/hrs

need ~$65510 for 1 months rent 777 pcs (97 rigs of 8x3090)

~$65510 need for get $340082 (12.40 btc)

[WanderingPhilospher]

#125 need 2^63.10 ops

23330 days (559920 hours) of work one RTX 3090 (4.8 GKey/s) modified kangaroo

1 hours price is $0,117/hrs

need ~$65510 for 1 months rent 777 pcs (97 rigs of 8x3090)

~$65510 need for get $340082 (12.40 btc)

I always like numbers!

First, what is this modified kangaroo program?

Verified that a 3090 gets 4.8G Key/s??

Let us suppose that a 3090 does get that speed, it would take 777 RTX 3090s 41 days to find the key, not 1 month. And it would take a single 3090, 32,561 days to find the #125 key.

Also, I come up with roughly 2^63.55 ops, not 2^63.10 ops. If using JLPs kangaroo with range shift, then yes 2^63.05.

Edit: If a 3090 can get 4.8 GKey/s, then your numbers are pretty close...around 29-30 days!

[GR Sasa]

Edit: If a 3090 can get 4.8 GKey/s, then your numbers are pretty close...around 29-30 days!

Nono, i don't think so. A 3090 gets around 1500Mkey/s using Jean's Kangaroo. So maybe more than half the time, maybe around 90 days. Still pretty a lot of time with a lot of electricity and GPUs to afford and to get. But it'll be worth the work in the end if Bitcoin gets to 100k any time soon..

[racminer]

#125 need 2^63.10 ops

23330 days (559920 hours) of work one RTX 3090 (4.8 GKey/s) modified kangaroo

1 hours price is $0,117/hrs

need ~$65510 for 1 months rent 777 pcs (97 rigs of 8x3090)

~$65510 need for get $340082 (12.40 btc)

I always like numbers!

First, what is this modified kangaroo program?

Verified that a 3090 gets 4.8G Key/s??

Let us suppose that a 3090 does get that speed, it would take 777 RTX 3090s 41 days to find the key, not 1 month. And it would take a single 3090, 32,561 days to find the #125 key.

Also, I come up with roughly 2^63.55 ops, not 2^63.10 ops. If using JLPs kangaroo with range shift, then yes 2^63.05.

Edit: If a 3090 can get 4.8 GKey/s, then your numbers are pretty close...around 29-30 days!

If I remember well, a huge amount of RAM and HDD space is also required. It is not juste a matter of ops.

[noecp]

I always like numbers!
First, what is this modified kangaroo program?
Verified that a 3090 gets 4.8G Key/s

This is not JeanLucPons version of Kangaroo
this have a lot of unnecessary checks that slow down the process.

The plain cuda version of secp256k1 and several optimize changes have this speed.

RTX 3070 with power limit 170w 2.4 GKey/s  GPU Ram Usage 3.5GB
RTX 3090 with power limit 350w 4.8 GKey/s  GPU Ram Usage 8.0GB

And one dedicated server for check
have 32GB RAM ( 8gb+ ram need for bloom filters )
~140Gb of nvme used for kvrocks storage for store 2^31.10 of DP32
or 35Gb if use DP34

ps4all. Possibly I'll find time for compare if you have dp's (or work file fromJeanLucPons Kangaroo ) for still determine 120 and check wild/tame and later
(in compared dp's included buyed from zielar)

But i rarely come here.

[WanderingPhilospher]

I always like numbers!
First, what is this modified kangaroo program?
Verified that a 3090 gets 4.8G Key/s

This is not JeanLucPons version of Kangaroo
this have a lot of unnecessary checks that slow down the process.

The plain cuda version of secp256k1 and several optimize changes have this speed.

RTX 3070 with power limit 170w 2.4 GKey/s  GPU Ram Usage 3.5GB
RTX 3090 with power limit 350w 4.8 GKey/s  GPU Ram Usage 8.0GB

And one dedicated server for check
have 32GB RAM ( 8gb+ ram need for bloom filters )
~140Gb of nvme used for kvrocks storage for store 2^31.10 of DP32
or 35Gb if use DP34

ps4all. Possibly I'll find time for compare if you have dp's (or work file fromJeanLucPons Kangaroo ) for still determine 120 and check wild/tame and later
(in compared dp's included buyed from zielar)

But i rarely come here.

I never doubt people on improvements, unless they obviously do not seem to understand basic concepts.

Anywho, congrats on the speed boost on your modified kangaroo program, kudos! I hope you find #125 key soon!

[_Counselor]

This is not JeanLucPons version of Kangaroo
this have a lot of unnecessary checks that slow down the process.

JLP uses assembly instructions to perform GPU computations, also overall process of jumping is pretty good optimized in my opinion. Can you please give an example of non-optimal computations in JLP code, by optimizing which we can get a such increase in speed?

[digaran]

Wait, you can use work files? People sell them for money? Lol in order of P. I have deleted near 1 GB of them because I thought they were useless, actually every time I start I delete the previous work file, I just kept a few of them.😅

[noecp]

This is not JeanLucPons version of Kangaroo
this have a lot of unnecessary checks that slow down the process.

JLP uses assembly instructions to perform GPU computations, also overall process of jumping is pretty good optimized in my opinion. Can you please give an example of non-optimal computations in JLP code, by optimizing which we can get a such increase in speed?

this is not two byte changes
need rewrite or many many refactoring.

1. split search either looking for tame or wild
2. remove realtime collision checks
3. modify check for prefixes of founded kangaroo
4. try other cuda implementations of ecp VanitySearch, BitCrack and forks here have many ideas

Wait, you can use work files? People sell them for money? Lol in order of P. I have deleted near 1 GB of them because I thought they were useless, actually every time I start I delete the previous work file, I just kept a few of them.😅

workfiles contain poins and a collision can be found by comparing all previously found tame and wild points.
could you may  have already found  a collision several times today with the found earlier but already erased ;0

[digaran]

Wait, you can use work files? People sell them for money? Lol in order of P. I have deleted near 1 GB of them because I thought they were useless, actually every time I start I delete the previous work file, I just kept a few of them.😅

workfiles contain poins and a collision can be found by comparing all previously found tame and wild points.
could you may  have already found  a collision several times today with the found earlier but already erased ;0

I have no ideas, tame, wild and dp points are alien language to me. Everytime I see average time is around 4 minutes for hours, everytime I see too much dead kangaroos on my hands, and everytime it says 19876 y, I assume something is not working and I just change the key and it's range. Lol.

[WanderingPhilospher]

With the injection of more BTC and some friends & offline members expressing interest, I have a pool up and running for #125. If there is a good interest here, I will post how to setup and connect to it. Let me know who is interested in helping search for 12.5 Bitcoin.

If interested, let me know. You can message me and let me know your setup so I can get a good idea of speed/timeframes, etc.

Once I gauge the interest, I will post how to setup and message those interested, the applicable port number(s).

For those without CPUs or GPUs, but still want to participate and have the chance at making a decent size return on your Invesment, you can rent with vast and I can show you how to do so. It's extremely easy to set up.

Standard pool, meaning we pool our resources, and split the BTC reward based off of DPs submitted and accepted.

Message me if you have any questions or have a possible other avenue. All help is appreciated!

[WanderingPhilospher]

This is not JeanLucPons version of Kangaroo
this have a lot of unnecessary checks that slow down the process.

JLP uses assembly instructions to perform GPU computations, also overall process of jumping is pretty good optimized in my opinion. Can you please give an example of non-optimal computations in JLP code, by optimizing which we can get a such increase in speed?

this is not two byte changes
need rewrite or many many refactoring.

1. split search either looking for tame or wild
2. remove realtime collision checks
3. modify check for prefixes of founded kangaroo
4. try other cuda implementations of ecp VanitySearch, BitCrack and forks here have many ideas

Splitting the search for wild or tame does not increase speed, it just targets one or the other. I've been doing this for at least 2 years. Find enough tames, then switch to wilds.
Real-time collision checks only happens on server side (if using a server) so that shouldn't slow down the GPUs, they just send the DPs to the server.
What do you mean by modify check for prefixes of founded kangaroo??