Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED== - page 24. (Read 57113 times)

It looks like pending inputs from my side. Not sure anyone can confirm. They not outputs, just unconfirmed in. Available but not.

yes that's right that's why I said it's strange .....I try to understand how this can happen but

Oh, you are rigth seems interesting.



But there is no any output

ok albert0bsd but my remark came from the fact that the explorer shows $2.07 sent as well as the difference between the total received and the final balance...so why 

It is not an output, is in input to the puzzle 66, nothing strange there.

It's strange did you notice that on #66 there is an output awaiting validation  2.07$  
https://www.blockchain.com/fr/explorer/addresses/btc/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
It is not validated so the pubkey is not broadcast but the scale takes it into account without any validation   Total Received 6.60036526 BTC   Final Bitcoin Balance 6.60028826
It doesn't exist on the other # yet. How can this happen?

I think he want to work on the law of averages. So work on either side of long gaps so to speak. I could be off base though.

I still do not understand what you are asking/implying.

In the 64-bit range, there should be an estimated 2,483 addresses that start with 16jY7qLJnx.

You are looking at a very small sample size in the list of addresses you posted.

it remains only theoretical and probabilistic the distribution is obviously not linear if not on range #64 by adding an additional character to 16jY7qLJnx ex H ==> 16jY7qLJnxH it should come out <1 but in this case there are 2 whereas for 16jY7qLJnx N or P only one address but it stands

Yeah, not sure what you really mean then. How can you be certain a 16jY7qLJnx prefix isn't in a range without checking every key?

You said all addresses starting with 16jY7qLJnx, so maybe I am misunderstanding your question. Are you wanting 100% certainty or more like 30% lol.

No, I do not think so because it covers the whole range #64 with this prefix 16jY7qLJnx
So 18 obtained on a purely theoretical and probabilistic distribution of 21 on this range with this prefix 16jY7qLJnx

EDF9CD60356DCC19        17147962869286816793            16jY7qLJnx2ixrxCnTLSraerkgyB3YYAiT
AF6F7A0015695AA4        12641456819830086308            16jY7qLJnx4enVJC2Ao3wRv3tRusseu5Yb
EBE2EB35503B43E4        16997406557861528548            16jY7qLJnx4f4yqNvmp7LtnaatiUuwgUwW
CF32BE01449CE45D        14930204627341993053            16jY7qLJnxABQQMzyUZ8qsJ3sHaPDZVxJ7
C9DDAD024A7C3688       14545972596827764360            16jY7qLJnxBo3HMqG3wP2MRh9CQXcgSVcf
EEB9AB334DF2770D         17201968488557737741            16jY7qLJnxHBp3dqwV2kzYq1LucfZzgxsH
CE1EB402A0085C60         14852506544482311264            16jY7qLJnxHHepGawzcc4xcNVZZdpFD8xu
C33AE60173B94230         14067809279956042288            16jY7qLJnxN3ec4QBdgpT8pYg77c8Wt6A9
D461BAACE35DB135        15303718260493365557            16jY7qLJnxPwmtRgVS3HBg2RtAoHe1koZF
F7051F27B09112D4          17799667357578236628            16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
B0D6BBB249F4D96F          12742578570110753135            16jY7qLJnxcZQ1ff7Y6ascX2FwkVfMEqcn
C42B8F0185753E8C          14135549092129226380            16jY7qLJnxgQD6f6rp4js9MiqCMkB3gAY5
E5CC7336D5283C4A          16558736609276083274            16jY7qLJnxhMwuUoPD7J3GTmDqLH7MaU6h
9357254130F9270A          10616995608473970442            16jY7qLJnxht5HL2NBywuoC8jK34rz8NJv
C8841802AA8BE839          14448699904241690681            16jY7qLJnxiepip11xyDZitPPsHssCRKT2
C4230300DFE089AF          14133143357909666223            16jY7qLJnxoBx9Zhsa1tN62rfZXX1bgKNp
AF3F2501F141A44C          12627852570442966092            16jY7qLJnxpsj9dmx9WAuRgxkk9pPvuFXw
8EC5EDB376AEB55A          10287890278843856218            16jY7qLJnxtt8FSYMze4DRVMWQF47auU8M

You would have to run the entire range, in the range you are wanting to search.

How to get all addresses + privateKey starting with 16jY7qLJn from #64?
More interesting all those on this same range of 64 starting with 16jY7qLJnx?

how much size have work file saved by 4090?

Out the box, non modded Kangaroo with 128x128 grid size. Should be in the 2200-2300 range.

I believe @ _Counselor implemented this method; he would know if it gave any significant speed up. But if I remember, I believe he said it did not.

Substaction jmp distance from kangaroo position will give a doubling in the speed of finding  DP.
But will these additional points give a result?
If you found another solution, then well done. I only found this way.

For example my BSGS version is almost times 3 times 9 times faster that the Original BSGS from JLP, that is almost 300% 900%

just saying...

---

edit

click for proof 🖼️

With the same RAM JLP did that range in 3 hours, i did it in 20 minutes that is 900% faster...

I will bet you whatever you have to lose 😎

Etar, you are a smart programmer. It’s really not that much to mod. I made some simple mods and increased speeds by at least 3x on most cards.

But hey, y’all can say what you want to. Water off my back.

Maybe I’ll make a video to compare how many DPs JLP’s stock Kangaroo can get in x amount of minutes and then compare that to mine. But even then, there would be doubters.

But we can do a test; a timed test. Someone can give me a range, say a 44 bit range and I will run it with my mod at DP 29, and post results. 44 bit range with DP 29 should yield 2^15 DPs in 38 minutes using 1 RTX 4090.