 Show Posts
|
|
Pages: [1] 2 3 »
|
|
1
|
Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
|
on: January 28, 2024, 04:58:34 PM
|
Agreed it is an avalanche effect, up to a point. From the private key perspective, but not the public key perspective.
Meaning, normally, if you have the same number of leading public key characters, they often will hash to the same leading characters in an address.
I was recently reading this, somewhere.
However, the private key is the wildcard. Trying to match the first x amount of characters and it hash to same public key or address is not the norm.
People like to tinker. Nothing wrong with that. Their idea may spawn something that helps solve quicker. Maybe, maybe not, but it doesn’t hurt anyone from a person tinkering out their ideas.
bx sha256 1234 - hash 1234 3a103a4e5729ad68c02a678ae39accfbc0ae208096437401b7ceab63cca0622f - Produced EC key from hash bx ec-to-public 3a103a4e5729ad68c02a678ae39accfbc0ae208096437401b7ceab63cca0622f 03b57de06f5c674af0d789530249bb658b0e317d4d179e1b1b1b0aa2ba668bb5f5 - Public key bx ec-to-public 3a103a4e5729ad68c02a678ae39accfbc0ae208096437401b7ceab63cca0622a - Only last digit of public key has been changed 02e70d3902ef877ba400f15ec109e1933956da79b14d6d33054f50cad9c30e5d5d - Public key Changing f to a on the EC key resulted in two very different pub keys. 03b57de06f5c674af0d789530249bb658b0e317d4d179e1b1b1b0aa2ba668bb5f5 02e70d3902ef877ba400f15ec109e1933956da79b14d6d33054f50cad9c30e5d5d Resulting in the following addresses bx ec-to-address 03b57de06f5c674af0d789530249bb658b0e317d4d179e1b1b1b0aa2ba668bb5f5 16sxaRqyfABv4LBsH1hEgj6tr1g5u2yNtC bx ec-to-address 02e70d3902ef877ba400f15ec109e1933956da79b14d6d33054f50cad9c30e5d5d 1CQttaNNbyei9SPeo2WSc6fsc6asWmcvkP However I have noticed public keys working towards address do somewhat share similar conversion traits. Not sure how it would be useful. Much like all the EC keys we are looking for all start the same. Just too many of possible values. |
|
|
|
|
3
|
Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports
|
on: November 17, 2023, 12:10:53 AM
|
Bsgs is now holding 18 exa keys/s stable.
Running a program to searches 18 exa keys/s is impressive! I have 16 GB and Core i7, and get only 70 Peta key/s Just uped my ram to 512 gig 51 Exa keys/s My rig will hold up to 2 terrabtes of ram. Just $$$
Bsgs is now holding 18 exa keys/s stable.
Running a program to searches 18 exa keys/s is impressive! I have 16 GB and Core i7, and get only 70 Peta key/s 18 ExKeys/s this is a drop in the ocean, the range is huge, brute force is currently not the best choice for solving the puzzle. Even if random is not a very good idea, you need to look for another approach P.s.  Still a chance, and this is what this puzzle is about. Are you suggesting I stop searching? Btw I will also be donating to Alberto if I find any. |
|
|
|
|
4
|
Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports
|
on: November 05, 2023, 01:22:44 PM
|
|
I figured it out. But not sure what was going on. I reinstalled ubuntu from usb, started fresh. Bsgs is now holding 18 exa keys/s stable. All 80 cpu threads loaded around 50-60 percent. Appears my ram can now not keep up. But the speed drop out is gone.
|
|
|
|
|
6
|
Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports
|
on: November 03, 2023, 10:43:36 PM
|
Maybe it is something related to the Operating system thread administration. Can you try some 78 or 79 threads instead?
Maybe the CPU gets heater and it reduce the frequency. Check first running it with less than 80 thread try some 70, 75... Just to discard some cases.
Ubuntu 23.04 I have tried 78, 50, 55 all the same results. Anything over 40 decreases the speed by half with twice the threads. Maybe a Kernel issue? |
|
|
|
|
7
|
Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports
|
on: November 03, 2023, 10:29:23 PM
|
|
BSGS Dual CPU support? Running 2x intel gold 6148 40 threads each 256gig ram.
At 40 threads I get 15 Exa keys/s
At 80 threads I get 6-12 Exa keys/s
All threads are fully loaded when 80 is requested. Bottle neck somewhere?
I am still fine with 40, but 80 would be nice.
Thank you for all the great work Alberto!
|
|
|
|
|
8
|
Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
|
on: October 28, 2023, 03:17:12 PM
|
|
Assuming
The creator made a wallet with random keys
When wallets are created they are always randomly generated keys. This is what makes them secure.
The creator then added zeros to the front of all those keys. Increasing in complexity each key after the previous key. Making them solvable.
I agree there's a pattern. But even distance from keys seems to shift at times.
|
|
|
|
|
10
|
Bitcoin / Bitcoin Technical Support / Re: Corrupted privkey, BTC wallet from 2010, was crossed into a Doge client.
|
on: October 14, 2023, 08:12:01 PM
|
My thoughts..
looking at this address, addr": "1N1SChDzQ1EyKm3nb5u6wGRyzhepYdNwEZ", It has not transacted. So, the program you are using is processing the wallet with your wallet passphrase, which is deriving a master key which in turn is decrypting all the Ckeys in the wallet producing the compressed addresses. (I don't believe compressed addresses were about in 2010?)
There are scripts about to convert compressed addresses to uncompressed so you could check all 200ish uncompressed addresses to see which ones have a balance. Again there are scripts to automate this.
You can then dump the wallet to get all the Ckeys. With the Ckey of the address with the balance and the passphrase master key, it would be possible to decrypt that individual private key even if the wallet was corrupt.
I do have scripts that can do this which are not public but I am sure there are others out there..
Good luck
All EC keys have been converted and checked uncompressed. No value. Unless the data is in the wallet and not dumped with the scripts. Compressed keys were not used back then you are correct. I am willing to try whatever scripts you have. Thank you! |
|
|
|
|
11
|
Bitcoin / Bitcoin Technical Support / Re: Corrupted privkey, BTC wallet from 2010, was crossed into a Doge client.
|
on: October 14, 2023, 07:43:37 PM
|
Did they use compressed public keys back in 2010? Not sure why your keys are compressed, also I'm not seeing any balance on those addresses, one has to wonder what you are going to share 20% of, when there is nothing specified, though if the amount you are missing is more than 1000 bitcoins, then 20% would be 200, and if you have a public key needing to find it's private key, show it here.
I do not have a suspect Public key. Also the suspected ec key converted to uncompressed public key has no value. My request for help relates to any possible means of recovery of the data in the wallet. 20 percent of what I have, which may be nothing. But everyone will notice if a legacy genesis Era wallet moves funds and I will keep my word. |
|
|
|
|
12
|
Bitcoin / Bitcoin Technical Support / Re: Corrupted privkey, BTC wallet from 2010, was crossed into a Doge client.
|
on: October 14, 2023, 05:01:00 PM
|
I know its been a while, I kind of took a break from this. Anyways I had tired https://github.com/HardCorePawn/pywallet and I still get a "bdict error" End of the data says "_____u_key " from bdict error. Also there is alot of data before it. So I suspect the wallet from BTC core v0.2 generated 1 key like it should. That wallet was then loaded into a LTC client in 2013, Data was corrupted, I thought it was doge, but found it appears to be a LTC client that was actually used. I tried this pywallet https://github.com/mikeborghi/pywallet and this one does not give me a error. However there are 202 keys found, same amount as every time. Here where it gets interesting. The Keypool data for the very last key is different then all the other keys in the wallet when dumped with dbdump_4.8 Also when dumped with pywallet the Ntime value is different for the last key. Ill attach a snipped of public key data from the dump. 20% for whomever could help. { "addr": "1N1SChDzQ1EyKm3nb5u6wGRyzhepYdNwEZ", "n": 97, "nTime": 1386907297, "nVersion": 80501, "public_key_hex": "03e54218920b5a65f8a719b6c3a8688ba372edacd357cd972903f1739d4423e8cc" }, { "addr": "19vH287DnfvTCGn32n57tak3PLMty3n2Uz", "n": 98, "nTime": 1386907297, "nVersion": 80501, "public_key_hex": "029d8825c8980fecce7583630164af7a4f7530c5602c4df645d9e29ba7c352e2ab" }, { "addr": "1DymDmrQi3VhQzAY7Z64pCBMzP5ZnLPxcE", "n": 99, "nTime": 1386907297, "nVersion": 80501, "public_key_hex": "039e92ce90bacbe769968c7aa103b4a90a1e49519af9a871a826544afba048acd3" }, { "addr": "16JBptL2TuLDUjRcU5GGRBbj3XTfoZq3Hw", "n": 100, "nTime": 1386907297, "nVersion": 80501, "public_key_hex": "03e9092f11b0d45ce1e843c37f03f930f0c5f133ebc3d898a076464515f49fed93" }, { "addr": "1PbyL7dJsjAaMvPWx85UW7SVtuoh6qRDna", "n": 101, "nTime": 1386914343, "nVersion": 80501, "public_key_hex": "03f8f3bbe1cb60b4c77c031d39ec94d6babfd60930912256b14346e7a0e763ac6b" } |
|
|
|
|
14
|
Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
|
on: September 03, 2023, 07:29:48 PM
|
It has been partly fun but most exhausting running a server in my garage in hope to find one of the puzzles to save me from debt, poverty and help out with illness in my family with unpayable medical bills. Sunday wife and kids are out of town and I will turn off the server and myself. Good luck rest of you!
I see you have chosen the path of cowards, there are so many things in life other than this puzzle. Find something else, believe in God, because he always provides. Also there is no such a thing as an off switch for us, we never go off, whatever happens we keep existing. A wife and kids, you are already blessed, you just don't know it. Wow, Great words here! Yes be thankful for what you have. Not what you want. Amazing reply digaran! |
|
|
|
|
15
|
Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
|
on: August 31, 2023, 03:07:08 PM
|
Take a deep breath man and relax ! There is no need to call somebody parasite even if it's clearly a scammer! Don't forget, this is a community, I don't see the point of being toxic in your comments!
Ok, lets bring a few virgins for that guy to make it up to him. Anyone here knows how to twerk? Or do I have to take another deep breath and do the twerking myself? You need to drink a glass of milk to wash the toxins away.😉 Why do you jump at people's throats so much? Do you have any frustration or do you simply think you are the owner of the absolute truth? Everyone has the right to use or recommend applications to others, without being offended by some like you. Maybe you should take your pills on time, so you don't go into fibrillation. ! Prove that PuzzleBTC contains viruses or trojans and then make claims ! Post source code |
|
|
|
|
16
|
Bitcoin / Bitcoin Technical Support / Re: Bitcoin Wallet Key Batch Extractor.
|
on: August 19, 2023, 09:22:38 PM
|
Dear Sir,
I would like to inform you that i have try to run your script (bitwalletrecover.py) for recovering my old or encrypted wallet.dat (Bitcoin); but it is not run following error massage found:
Traceback (most recent call last):
File "bitwalletrecover.py", line 23, in
from pycoin.ecdsa import generator_secp256k1, public_pair_for_secret_exponent
ImportError: cannot import name 'generator_secp256k1' from 'pycoin.ecdsa' (C:\Python37\lib\site-packages\pycoin-0.0.0-py3.7.egg\pycoin\ecdsa_init_.py)
Could you please advice how it is solve..
Thanks & Regards,
Md. Ashraful Alam
Old thread but I encountered the same issue. It seems to be caused by the latest pycoin release. It was corrected with. Set python to version 2.7 as default. https://netslovers.com/post/how-install-python-27-pip-ubuntu-22-04/sudo python -m pip uninstall pycoin sudo python -m pip install pycoin==0.80 sudo python -m pip install pycrypto |
|
|
|
|
17
|
Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
|
on: August 08, 2023, 02:24:59 AM
|
https://github.com/BTC-HUB-GROUP/PubHuntIs anyone sure this even works? When its running it reports bits, every bit the amount of computations double for the next required bit increase. Does this mean when its at 50bit its only scanning in the 50 bit range? Code seems simple and maybe dare I say fun. [10:06:53] [GPU: 1538.03 MH/s] [T: 56,831,443,468,288 (46 bit)] [F: 0] [23:34:41] [GPU: 1520.21 MH/s] [T: 131,355,736,276,992 (47 bit)] [F: 0] [25:18:46] [GPU: 1528.59 MH/s] [T: 140,840,802,451,456 (48 bit)] [F: 0] [35:49:31] [GPU: 1540.13 MH/s] [T: 199,668,382,302,208 (48 bit)] [F: 0] [57:20:31] [GPU: 1528.60 MH/s] [T: 320,320,640,647,168 (49 bit)] [F: 0] [70:41:51] [GPU: 1561.09 MH/s] [T: 394,940,412,592,128 (49 bit)] [F: 0] [82:02:23] [GPU: 1568.43 MH/s] [T: 458,789,262,196,736 (49 bit)] [F: 0] [96:37:41] [GPU: 1425.79 MH/s] [T: 539,854,018,445,312 (49 bit)] [F: 0] [105:48:12] [GPU: 1512.86 MH/s] [T: 591,400,085,225,472 (50 bit)] [F: 0] [118:24:29] [GPU: 1517.04 MH/s] [T: 661,610,855,137,280 (50 bit)] [F: 0] [144:26:15] [GPU: 1534.88 MH/s] [T: 806,676,613,562,368 (50 bit)] [F: 0] [168:04:28] [GPU: 1520.20 MH/s] [T: 939,011,786,932,224 (50 bit)] [F: 0] [168:38:10] [GPU: 1510.77 MH/s] [T: 942,101,864,906,752 (50 bit)] [F: 0] [191:30:27] [GPU: 1529.64 MH/s] [T: 1,070,122,592,632,832 (50 bit)] [F: 0] [191:33:19] [GPU: 1516.01 MH/s] [T: 1,070,385,508,384,768 (50 bit)] [F: 0]
|
|
|
|
|
