Pages:
Author

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

jr. member
Activity: 114
Merit: 5
Here are some statistics I updated from a previous poster from a couple of years ago in the old archived thread!

format #n x%    --> n is case #n and x is how far in % is the key from the lower bound of the corresponding keyspace.

#08 75% ,  #09 82% ,  #10 00% ,  #11 13% ,  #12 31% ,  #13 27% ,  #14 29% ,  #15 64% ,
#16 57% ,  #17 46% ,  #18 52% ,  #19 36% ,  #20 65% ,  #21 73% ,  #22 43% ,  #23 33% ,
#24 72% ,  #25 98% ,  #26 63% ,  #27 67% ,  #28 70% ,  #29 49% ,  #30 92% ,  #31 96% ,
#32 44% ,  #33 66% ,  #34 65% ,  #35 17% ,  #36 23% ,  #37 46% ,  #38 07% ,  #39 18% ,
#40 83% ,  #41 33% ,  #42 32% ,  #43 68% ,  #44 75% ,  #45 14% ,  #46 46% ,  #47 70% ,
#48 36% ,  #49 45% ,  #50 09% ,  #51 83% ,  #52 87% ,  #53 50% ,  #54 11% ,  #55 67% ,
#56 23% ,  #57 92% ,  #58 39% ,  #59 82% ,  #60 97% ,  #61 24% ,  #62 69% ,  #63 94% ,
#65 66% ,  #70 64% ,  #75 19% ,  #80 83% ,  #85 09% ,  #90 40% ,  #95 29% ,  #100 36% , 
#105 44% , #110 68% , #115 52%

Here is the resulting histogram (10 bins) which display's how the found keys are distributed:

  0% -  10%         ∎∎∎∎
 10% -  20%        ∎∎∎∎∎∎
 20% -  30%        ∎∎∎∎∎∎
 30% -  40%        ∎∎∎∎∎∎∎∎
 40% -  50%        ∎∎∎∎∎∎∎∎∎
 50% -  60%        ∎∎∎∎
 60% -  70%        ∎∎∎∎∎∎∎∎∎∎∎∎
 70% -  80%        ∎∎∎∎∎∎
 80% -  90%        ∎∎∎∎∎∎
 90% - 100%       ∎∎∎∎∎∎
member
Activity: 406
Merit: 47

Thank you $upermoney for advice.

I just doubt about series number of puzzle, it is pick by manual random or pick number by using some formula (using math) or some algorithm calculate for pick number

I try already with both Pollard's kangaroo ECDLP solver C# and Python3 script
seem is still random bitcoin address by method buy is random by curve line (not normal dot random)
that is good idea for using random by that method pattern, and yes it is better than random by normal one dot pick

(but that random not solve by calculate series number list)
I just think about puzzle challenge for calculate formula for pick bitcoin address  private key or not (create math formula series? or make challenge to random to found bit coin adress (pick by manual pric by hand)

How many people still work on this puzzle next address? ( How many people give up?)
look like both thread not talk a massive a long time
newbie
Activity: 23
Merit: 0
Hi,

Done any one still work progress random generate key for this bitcoin puzzle?

My question about puzzle

Series of this puzzle is not formula or algorithm right?

I think this puzzle is pick manual number by hand, I am correct right?

If this puzzle is number of some algorithm or formula it is can possible to crack it and if some one can solve this formula (algorithm) it can possible to get all bitcoin

But this (all address) is pick by random manual so this way never possible calculate by any formula , calculate, algorithm

Can anybody help to confirm me about all bitcoin address puzzle all take by use algorithm or custom formula for pick bitcoin address?


Here is some good reading for you: https://bitcointalksearch.org/topic/pollards-kangaroo-ecdlp-solver-5244940
member
Activity: 406
Merit: 47
Hi,

Done any one still work progress random generate key for this bitcoin puzzle?

My question about puzzle

Series of this puzzle is not formula or algorithm right?

I think this puzzle is pick manual number by hand, I am correct right?

If this puzzle is number of some algorithm or formula it is can possible to crack it and if some one can solve this formula (algorithm) it can possible to get all bitcoin

But this (all address) is pick by random manual so this way never possible calculate by any formula , calculate, algorithm

Can anybody help to confirm me about all bitcoin address puzzle all take by use algorithm or custom formula for pick bitcoin address?
newbie
Activity: 4
Merit: 6
Hello i am a tree in this but i have an nVIDIA rtx 3090 how do i use kangaroo? with Kangaroo.exe settings -gpu -ws -w save.work -wi 30 in.txt only 400-600 Mkey Sad. Thanks.
jr. member
Activity: 114
Merit: 5
Thanks. Looking for a way via code...

I don't think it's possible to calculate the public key from anything via code unless you use an api or something
newbie
Activity: 18
Merit: 1
Thanks. Looking for a way via code...
jr. member
Activity: 114
Merit: 5
Hello, everyone,

Kinda offtopic for this thread, but how exactly to get pubkey of an address from bitcoin transaction which sent out coins?

I'm using this python bitcoin parser (https://github.com/alecalve/python-bitcoin-blockchain-parser) and I can see tx inputs and outputs, I can see output addresses for most txs. And I can see input script. But how to get pubkey of that address which send tx out?

TIA

If you search the transaction on blockchain.com and look at the inputs SigScript the public key will be displayed.
newbie
Activity: 18
Merit: 1
Hello, everyone,

Kinda offtopic for this thread, but how exactly to get pubkey of an address from bitcoin transaction which sent out coins?

I'm using this python bitcoin parser (https://github.com/alecalve/python-bitcoin-blockchain-parser) and I can see tx inputs and outputs, I can see output addresses for most txs. And I can see input script. But how to get pubkey of that address which send tx out?

TIA
jr. member
Activity: 114
Merit: 5
Can someone help me out,I switched laptops at Christmas and I lost the website that can look-up a PKV and it gives the corresponding Hex,I can't find it now.



this one? https://brainwalletx.github.io/#converter
member
Activity: 93
Merit: 26
Can someone help me out,I switched laptops at Christmas and I lost the website that can look-up a PKV and it gives the corresponding Hex,I can't find it now.

hero member
Activity: 583
Merit: 502
How is it that more complex keys are discovered but simpler one like 64 have not? i would have thought the ones after 64 would be significantly more difficult/nearly impossible. Is there any reason why this is the case?

Every five txs the public key is exposed. Maybe someone find it with other approach.

There is no "approach". The whole point of creating original transaction is to prove it, and it has been proven solid for 6 years since then.

The "approach" that was mentioned is in the different program used. People have used the "Kangaroo" program to find the keys with known public keys; versus brute force approach for the smaller ranges, i.e. 64 bit range.

The thing is that you can't use the Kangaroo "approach" to the small ranges because their public address are not known.
full member
Activity: 1232
Merit: 242
Shooters Shoot...
How is it that more complex keys are discovered but simpler one like 64 have not? i would have thought the ones after 64 would be significantly more difficult/nearly impossible. Is there any reason why this is the case?

Every five txs the public key is exposed. Maybe someone find it with other approach.

There is no "approach". The whole point of creating original transaction is to prove it, and it has been proven solid for 6 years since then.

The "approach" that was mentioned is in the different program used. People have used the "Kangaroo" program to find the keys with known public keys; versus brute force approach for the smaller ranges, i.e. 64 bit range.
legendary
Activity: 1988
Merit: 1077
Honey badger just does not care
How is it that more complex keys are discovered but simpler one like 64 have not? i would have thought the ones after 64 would be significantly more difficult/nearly impossible. Is there any reason why this is the case?

Every five txs the public key is exposed. Maybe someone find it with other approach.

There is no "approach". The whole point of creating original transaction is to prove it, and it has been proven solid for 6 years since then.
newbie
Activity: 2
Merit: 0
How is it that more complex keys are discovered but simpler one like 64 have not? i would have thought the ones after 64 would be significantly more difficult/nearly impossible. Is there any reason why this is the case?

Every five txs the public key is exposed. Maybe someone find it with other approach.
copper member
Activity: 19
Merit: 2
How is it that more complex keys are discovered but simpler one like 64 have not? i would have thought the ones after 64 would be significantly more difficult/nearly impossible. Is there any reason why this is the case?
full member
Activity: 706
Merit: 111
Created a new thread for the Baby Step Giant Step pertaining to this Bitcoin challenge transaction, specifically #120 (120 bit key).

https://bitcointalksearch.org/topic/baby-step-giant-step-combined-efforts-to-find-12-bitcoin-5304368

Any one with a CPU can help/try to solve.




About to download and check it out now.
full member
Activity: 1232
Merit: 242
Shooters Shoot...
Mr zielar You recently rejoined the distributed effort ( ttdclient ) to crack #64, can you please share what hardware are you using ? These speeds are impressive I guess there must be multiple gpus ?

I've been there for quite a long time, but the number of orders and the use of resources did not allow for active participation.
Now it has stabilized a bit, as well as of my free time.
At the moment exactly 500x Tesla V100 is generating almost 700BK/s at http://ttdsales.com/64bit

What is the current total tested range (in % from the total 64bit range width)?
Total Ranges Checked: 12,939,613 of 134,217,728
full member
Activity: 1232
Merit: 242
Shooters Shoot...
Created a new thread for the Baby Step Giant Step pertaining to this Bitcoin challenge transaction, specifically #120 (120 bit key).

https://bitcointalksearch.org/topic/baby-step-giant-step-combined-efforts-to-find-12-bitcoin-5304368

Any one with a CPU can help/try to solve.


full member
Activity: 431
Merit: 105
wow started with 250 teslas now 500, amazing farm, are they all at one location,
so it might be solved today?
did you just started with those 500 on 64th puzzle address today?
or you already found 120 > went back to help us 64.? maybe
700BK/S woow
what does one card do, any pictures. thanks a lot btw.

i'm still doing 1 card a time.  Cool
Pages:
Jump to: