It's obvious for half a year and already known to those interested.
Setting -g X, Y ... Ultimately Y is 128, while raising this value to 256 or 512 increases the speed. What a sly man - he gave news.

To Jean Luc
if checking 64 bit, and save.work file 1 gb and found in 6 min

 ./kangaroo -winfo save.work
Kangaroo v1.5
Loading: save.work
Version   : 0
DP bits   : 8
Start     : 0
Stop      : FFFFFFFFFFFFFFF
Key       : 034B7DBF84F4AF9B9E5B9C15EEDE9C671FF5194FAF5290CE61DF4D2396A9FF22F0
Count     : 8657043456 2^33.011
Time      : 05:44
DP Size   : 518.0/654.0MB
DP Count  : 16908283 2^24.011
HT Max    : 105 [@ 035B51]
HT Min    : 31 [@ 03A140]
HT Avg    : 64.50
HT SDev   : 8.02
Kangaroos : 4194304 2^22.000

-------
if some tool change pubkey inside save.work, and this save work recalculate within all his record, how much time its take to find changed pubkey for same 64 bit

Yes, precomputation works best when the Tame Kangaroos are randomly distributed in a given search interval. Not necessarily so when only using a single output from the previous run.

Guys, how are you from Public Keys, coordinates define? I tried how many on the site http://gobittest.appspot.com/Address I do not understand how??? Teach me please!

y, now some show

You have funny memory problems (as -d 42).
I remind you that I got zero because you did not fulfill your part of the contract.
It was a simple job and (simultaneously) checking you for competence and honesty.
You failed miserably. Work with you? It’s useless to talk to you. Your word is zero, sad but true.

Read more about the events of September 2019.
VanitySearch1.17fix successfully adapted for vanitypool.appspot.com
Agreed, my fix, u gpurigs, 50/50.
Just on the calculated day, the reward leaves the account.
..And zielar disappears for a month! (wow, nice coincidence, y?)
Upon returning, he declares that he has nothing to do with the transaction!
Ok, look at the blockchain:
#60: 1Kn5h2qpgw9mWE5jKpk8PP4qvvJ1QVy8su -> 14yX9jrgmtJByn5YSTdA2uZM6kFQ9z9BUu -> 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL
#61: 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB -> 13aNcjjyQYgQZxnxz6Ar9eRqQENexDBPjh -> 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL
#62: 1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi -> bc1q055ws5xnrnjtf767cxuklrjl8vw5sst2j4a9lm -> 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL
#63: 1NpYjtLira16LfGbGwZJ5JbDPh3ai9bjf4 -> bc1qdqtkkmwtxk5ce0xvp57k46hnx8t43ngw97twmx -> 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL
and..
1ThePiachu -> 18A3UeLrcJbi58jci1s7xQss8v8QK8YJPK -> 1JSVnxtzLxNpW6YkXQbV1guW6FdZAaKM4L -> 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL
Tadaaa!
Even if 35HzrskKgRekhB9RgFGNrfhNbdqC1PvEUL does not belong to zielar..
..already in the third transfer, money RANDOMLY passes through this wallet.
And here I have to believe that zielar has nothing to do with what is happening)))
Its epic, really.

Open eyes. This is either you or your partner (the one you trust).
And, probably, the events in January are connected with this.

The truth is somewhere nearby, but I still will not see my piece of money.
So by right of verification I declare once again to everyone - be careful with zielar.

Some "unusable sticky thing" by me
https://github.com/Telariust/VanitySearch-appspot/releases
https://github.com/Telariust/VanitySearch-bitcrack/releases
danger! very unusable)


y, brutal insolent)


this phrase very expresses the attitude of the hero to the people around him.
if google it, this is not the first time he has said this.
lack/ignore of arguments and explosive emotionality. love it


Apparently, brichard19 also refused twice. Five times in a row.
(I recall how he answered in issues that he could not improve the program because he did not have enough money for a modern video card. But who read issues?)
Oh, it simple, BitCrack is also a "sticky thing", and brichard19 needs "get to work better", y.


y, i have big complex. intolerance of irresponsible people


i say, how about transfer to brichard19, let be 10% of #59-63, ~=0.35BTC
Transfer, if there is still something to keep.

Gentlemen, the time of bets - is whether the transfer will take place or if there will be another excuse.


..When the world record is set, remember, at what cost.

Suckers: the biggest dp I've set is 28. 42 you have degrees of fever because you let out of jealousy that you are an inefficient aunt.  You don't deserve anything and as a result you are conducting some private investigations ... it's probably from this ineptitude.  you are just a beetroot with which I am lucky - I have nothing to do with it anymore.  Go program your magic and test dp 42.  Thank you for unnecessary deliberation on your problem that you cannot solve.  I believe that you have convinced someone here with this lecture if anyone reads it at all.

BTW: did it take you half a year to think?

I have software that works. I am preparing to release it soon. I was running it non-stop since March 31st without any issues in my attempt to solve #110.

Yes, that is me (brichard19).

It is not a secret that keys #62 and #63 were found by zielar. He wrote about this on this forum (another thread). https://bt.irlbtc.com/view/5166284.msg52396107#msg52396107

He also wrote somewhere that he found #63 faster than #62.

But what is your problem with zielar? He found the keys, so he received the bounties. If you had some negotiations with him but he did not meet his part of the contract - unfortunately it is only your deal. And better to discuss it between you only, but not with the whole public. Bitcointalk also has its own trust system - so you can make your comments in zielar's profile if you can prove them (of course).