#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)

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..

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.

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

---

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

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!

Current progress towards #125
Testing server capabilities and keeping track of users DPs (thanks to NotATether).

Hello,

Due to the situation that happened in this challenge - I allowed myself to refresh the topic - I corrected the name of the thread, added a new date to "important dates", changed the image of the remaining amount of BTC up for grabs, and restored the functioning of my website zielar.pl from which you can now restart download the VanitySearch builds, because I saw somewhere earlier that someone mentioned that the links are out of date. It's a fact - they were outdated because I didn't extend the hosting :-) Nevertheless, everything is fine now. I'm also considering re-entering with some power... therefore, to shorten the necessary time to refresh the news about currently running programs - give me the details of any latest and greatest versions you are currently using (VanitySearch, Kangaroo) - and whether poolem 66bit also works pool fighting for 125?

Regards

<3

Any requirements for joining the pool?