Latest posts of: Lolo54

Show Posts
Pages: « 1 [2] 3 4 5 6 »

Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it

on: April 16, 2023, 09:48:50 AM

Quote from: Gianluca95 on April 16, 2023, 09:26:50 AM I would absolutely like to understand who is the one behind this puzzle and why he should spend this huge sum only for prove that Bitcoin network is really resistant and hard to break. This absolutely make me crazy ! I will start to look with much interest to this thread and try also to find something, now find a piece of puzzle could be a life change chance ! It's superb it becomes really very motivating there will be people on it #66 at 6.6 BTC is superb the address that issued the transactions contained 872 btc the person behind is not out of BTC at all..... I've been on this puzzle since the beginning and the day I saw the one and only intervention of the creator of this puzzle I said to myself it's satoshi himself who is behind (but I could be wrong) just a feeling https://bitcointalk.org/index.php?topic=1306983.msg18765941#msg18765941 (message from creator saatoshi_rising) https://www.blockchain.com/explorer/addresses/BTC/bc1quksn4yxlxp80tn929gqnh8xpnngqj0fqr99q4z

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: April 16, 2023, 09:45:57 AM

Quote from: JDScreesh on April 16, 2023, 06:36:22 AM WOW! Somebody (maybe the owner) increased the unsolved puzzles prizes again by x10 😱 Now the puzzle #66 prize is 6.6 BTC, #67 is 6.7 BTC... and so on .... puzzle # 160 prize is now 16 BTC 👍🏼🥳 waouuhhh yes exactly I just saw that indeed OP raised the bonus of all #Puzzles by X10 it makes you want even more especially for the lowest ones it becomes very very interesting

Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it

on: April 15, 2023, 10:21:24 AM

Quote from: AlanJohnson on April 15, 2023, 09:42:27 AM The only thing that can be solved by an average person are puzzles about maybe 90 - 100 bits but only in case the creator will reveal the public keys. But then solving puzzle 66 is a matter of few minutes and only competition is who will notice first that the public key is available ( and I doubt that was the goal of creator of all this thing). OP would have no interest in revealing the PubKey from #66 to #75 today it would be almost automatically discovered. The goal of OP was to demonstrate the solidity / resistance of BTC in the face of the ingenuity and the very power of a community! for puzzle #66 if the pubkey was revealed it would take about 2s with an average #67 4s / # 68 8s / # 69 16s / #71 1m etc of course subject to identical key location and using average material for #80 with average hardware kangaroo it takes 1 hour to find the privateKey .

Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED==

on: April 08, 2023, 11:38:23 AM

13zb1hQbw fhhEryPWBrAioLY5tiFLr hs5o - 0x319AFC9E3FF391B01 take a good look at the end of the address it is in no way identical to the 66 which is h5so no hs5o 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so it is only the first 7 characters which are identical but several utilities can allow you to find some in this range with even more characters just for example 13zb1hQbWLiYzxkb5Qeiwr9ZZRHycheQBV KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZo5eQmmER3KXshr85jU 2E120C91F20C0B511 20d45a6a762458afee967c590479283af57e7c40

Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it

on: April 06, 2023, 11:45:27 AM

Quote from: WanderingPhilospher on April 05, 2023, 10:43:38 AM

Doing some testing on 76 bit...

Code:

KangaBGStrider v1.01
Range Start :0 (0 bit)
Range End   :FFFFFFFFFFFFFFFFFFF (76 bit)
Public Key(s) :1
Creating Stride Table...
CPU thread(s) : 8
Stride Table Complete: Max Stride: 2^36
Stride Avg Distance: 2^34.09
Number of Striders: 2^13.00
Suggested DP: 22
Expected operations: 2^41.39
Simulated DP size: 32 [0x00000000FFFFFFFF]
[31.88 MS/s][GPU 0.00 MS/s][Total Collision Checks 2^32.97][05:04 (Avg 1.0d)]
Key# 0 [1S]Pub:  0x02BF6E9A6F10A15DC828E968FC96CF9BC80A98F42227CCBE2AC4947B637B3E8FB1
       Priv: 0x865CE114686A1301A4C

Done: Total time 05:05

Superb result WanderingPhilospher especially only on CPU you get the result 4 times faster than with BSGSCuda and Kangaroo from JLP on my RTX 2070. I noticed that kangaroo was a little faster than BSGS on your 76 bit 18 min VS 20 min for 02BF6E9A6F10A15DC828E968FC96CF9BC80A98F42227CCBE2AC4947B637B3E8FB1
Out of curiosity I did a test with a key taken at random from the 80 bit range to compare BSGS again with kANGAROO then then if you want to test this same pubkey to display your result which should be 4 times faster so surely on the 20 MIN approximately just with CPU VS 1H20 on GPU with kangaroo and 5 Days for BSGSCuda
Kangaroo result 1h20 for this 80 bit 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc
BSGSCuda result stopped (in 47 min 4410978597433994379265 key traveled) i.e. a little over 5 days on my RTX 2070 to get the key
On the large range Kangaroo remains for the moment still the fastest and most efficient in my opinion
Adapting KangaBGstrider V 1.01 on GPU could give the same result for this 80 bit in less than 1min or around 20 min on CPU, of course then everything also depends on the hardware used as well as the number deployed.
But I think that on a single GPU type RTX 2070 or 2080 the result could be given in 45s
Could you do a test on this pubkey 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc to display your result when it is possible and if you want of course :-)

My results on the 76 bit with BSGS then Kangaroo

Code:

C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\BSGSgpu.exe -t 512 -b 72 -p 256 -pk 8000000000000000000 -pke fffffffffffffffffff -w 30 -htsz 28 -pb 02BF6E9A6F10A15DC828E968FC96CF9BC80A98F42227CCBE2AC4947B637B3E8FB1
Number of GPU threads set to #512
Number of GPU blocks set to #72
Number of pparam set to #256
Range begin: 0x8000000000000000000
Range end: 0xfffffffffffffffffff
Items number set to 2^30
HT size number set to 2^28
Pubkey set to 02bf6e9a6f10a15dc828e968fc96cf9bc80a98f42227ccbe2ac4947b637b3e8fb1
APP VERSION: 1.7.3
Found 1 Cuda device.
Cuda device:NVIDIA GeForce RTX 2070 (7173.000/8191MB)
Device have: MP:36 Cores+2304
Try -t 512 -b 72 -p 304 -w 30 -htsz 28 [7170.000 MB] Gen RAM[28672 MB]
---------------
Current config hash[d4b0aa674cd6f609feedc322743bf9fdb571f06c]
GiantSUBvalue:0000000000000000000000000000000000000000000000000000000080000000
GiantSUBpubkey: 025318f9b1a2697010c5ac235e9af475a8c7e5419f33d47b18d33feeb329eb99a4
*******************************
Total GPU Memory Need: 7008.000Mb
*******************************
Both HT files exist
Load BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_1073741824_268435456_htGPU.BIN
[0] chunk:1073741824b
[1] chunk:1073741824b
[2] chunk:1073741824b
[3] chunk:1073741824b
[4] chunk:1073741824b
[5] chunk:1073741824b
Generate Giants Buffer: 9437184 items
Load BIN file:512_72_256_1073741824_g2.BIN
[0] chunk:603979776b
Done in 00:00:01s
GPU count #1
GPU #0 launched
GPU #0 Free memory: 7171Mb
GPU #0 Total memory: 8191Mb
GPU #0 TotalBuff: 7008.000Mb
Load BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_1073741824_268435456_htCPU.BIN
[0] chunk:1073741824b
[1] chunk:1073741824b
[2] chunk:1073741824b
[3] chunk:1073741824b
[4] chunk:1073741824b
[5] chunk:1073741824b
[6] chunk:1073741824b
[7] chunk:1073741824b
[8] chunk:1073741824b
[9] chunk:1073741824b
START RANGE= 0000000000000000000000000000000000000000000008000000000000000000
  END RANGE= 000000000000000000000000000000000000000000000fffffffffffffffffff
WIDTH RANGE= 0000000000000000000000000000000000000000000007ffffffffffffffffff
SUBpoint= (107460520eec5c741683329a716622b0b81c03200807de973686f8800b188cbb, 541a2b3f65dea673cacd9464630ab5eedbd1f28b7231c259fe2849c8e0d8db0b)
Save work every 180 seconds

FINDpubkey: 02bf6e9a6f10a15dc828e968fc96cf9bc80a98f42227ccbe2ac4947b637b3e8fb1
Cnt:658ec0000000000001 [1][ 722 ] = 722 MKeys/s x2^31=2^60.50 t:00:20:01
KEY[1]: 0x000000000000000000000000000000000000000000000865ce114686a1301a4c
   Pub: 02bf6e9a6f10a15dc828e968fc96cf9bc80a98f42227ccbe2ac4947b637b3e8fb1
Working time 00:20:03s
Total time 00:21:47s
GPU#0 job finished
GPU#0 thread finished
cuda finished ok

Code:

C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\Kangaroo2.2.exe -t 6 -gpu -d 14 -o resultkang76.txt -ws Kang76.txt
Kangaroo v2.2
Start:8000000000000000000
Stop :FFFFFFFFFFFFFFFFFFF
Keys :1
Number of CPU thread: 6
Range width: 2^75
Jump Avg distance: 2^37.02
Number of kangaroos: 2^20.18
Suggested DP: 14
Expected operations: 2^38.60
Expected RAM: 982.1MB
DP size: 14 [0xFFFC000000000000]
SolveKeyCPU Thread 1: 1024 kangaroos
SolveKeyCPU Thread 2: 1024 kangaroos
SolveKeyCPU Thread 5: 1024 kangaroos
SolveKeyCPU Thread 4: 1024 kangaroos
SolveKeyCPU Thread 3: 1024 kangaroos
SolveKeyCPU Thread 0: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 2070 (36x64 cores) Grid(72x128) (97.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.17 kangaroos [4.6s]
[660.58 MK/s][GPU 619.62 MK/s][Count 2^39.09][Dead 1][17:50 (Avg 10:30)][1.1/1.3GB]  MB]
Done: Total time 18:07

80 bit pubkey 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc

Code:

C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\Kangaroo2.2.exe -t 6 -gpu -d 16 -o resultkang80.txt -ws Kang80.txt
Kangaroo v2.2
Start:80000000000000000000
Stop :FFFFFFFFFFFFFFFFFFFF
Keys :1
Number of CPU thread: 6
Range width: 2^79
Jump Avg distance: 2^38.96
Number of kangaroos: 2^20.18
Suggested DP: 16
Expected operations: 2^40.60
Expected RAM: 982.1MB
DP size: 16 [0xFFFF000000000000]
SolveKeyCPU Thread 4: 1024 kangaroos
SolveKeyCPU Thread 5: 1024 kangaroos
SolveKeyCPU Thread 1: 1024 kangaroos
SolveKeyCPU Thread 3: 1024 kangaroos
SolveKeyCPU Thread 2: 1024 kangaroos
SolveKeyCPU Thread 0: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 2070 (36x64 cores) Grid(72x128) (97.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.17 kangaroos [5.0s]
[648.05 MK/s][GPU 603.01 MK/s][Count 2^41.31][Dead 2][01:19:35 (Avg 42:51)][1.2/1.6GB]
Done: Total time 01:19:58

Code:

C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\BSGSgpu.exe -t 512 -b 72 -p 256 -pk 80000000000000000000 -pke ffffffffffffffffffff -w 30 -htsz 28 -pb 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc
Number of GPU threads set to #512
Number of GPU blocks set to #72
Number of pparam set to #256
Range begin: 0x80000000000000000000
Range end: 0xffffffffffffffffffff
Items number set to 2^30
HT size number set to 2^28
Pubkey set to 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc
APP VERSION: 1.7.3
Found 1 Cuda device.
Cuda device:NVIDIA GeForce RTX 2070 (7173.000/8191MB)
Device have: MP:36 Cores+2304
Try -t 512 -b 72 -p 304 -w 30 -htsz 28 [7170.000 MB] Gen RAM[28672 MB]
---------------
Current config hash[1e744f24cca3231323c65c9831191e62c175fcc5]
GiantSUBvalue:0000000000000000000000000000000000000000000000000000000080000000
GiantSUBpubkey: 025318f9b1a2697010c5ac235e9af475a8c7e5419f33d47b18d33feeb329eb99a4
*******************************
Total GPU Memory Need: 7008.000Mb
*******************************
Both HT files exist
Load BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_1073741824_268435456_htGPU.BIN
[0] chunk:1073741824b
[1] chunk:1073741824b
[2] chunk:1073741824b
[3] chunk:1073741824b
[4] chunk:1073741824b
[5] chunk:1073741824b
Generate Giants Buffer: 9437184 items
Load BIN file:512_72_256_1073741824_g2.BIN
[0] chunk:603979776b
Done in 00:00:01s
GPU count #1
GPU #0 launched
GPU #0 Free memory: 7171Mb
GPU #0 Total memory: 8191Mb
GPU #0 TotalBuff: 7008.000Mb
Load BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_1073741824_268435456_htCPU.BIN
[0] chunk:1073741824b
[1] chunk:1073741824b
[2] chunk:1073741824b
[3] chunk:1073741824b
[4] chunk:1073741824b
[5] chunk:1073741824b
[6] chunk:1073741824b
[7] chunk:1073741824b
[8] chunk:1073741824b
[9] chunk:1073741824b
START RANGE= 0000000000000000000000000000000000000000000080000000000000000000
  END RANGE= 00000000000000000000000000000000000000000000ffffffffffffffffffff
WIDTH RANGE= 000000000000000000000000000000000000000000007fffffffffffffffffff
SUBpoint= (769bc75842bff58edc8366ecd78f8950ee4ab2e81359d90f9921fa3d2c4561be, b407e8c9d0187c4537231b3108c0a2b8be5e888984878c522a6df3ff4f2693d0)
Save work every 180 seconds

FINDpubkey: 02b7e1f6b67c5c09ab3de91dcbe456716b98e7eb807f9c80160a5dea6e242e41bc
Cnt:ef1ea0000000000001 [1][ 699 ] = 699 MKeys/s x2^31=2^60.45 t:00:46:58

Bitcoin / Bitcoin Discussion / Re: == Bitcoin challenge transaction: ~100 BTC total bounty to solvers! ==UPDATED==

on: March 02, 2023, 07:28:23 PM

Quote from: zielar on March 02, 2023, 06:04:28 PM Congratulations to the person who found key #120. I am impressed and I will be grateful if this person publicly discloses the private key and provides information on how he found the key, or provided this information in a private message if he wants to remain anonymous, and that I complete this information in the table in the main post on his behalf. the same I am impressed because only those who ignore the difficulty do not express themselves while it remains a feat / an event !! I just say congratulations to the one who succeeded but it would be nice if he at least gave the key! you zielar you said how you succeeded congratulations to you

Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it

on: February 28, 2023, 01:19:27 PM

If the method used was indeed Kangaroo in this case the #125 will not be touched before 10 or 15 years according to current programs and technology The smallest keys from 66 are already starting to be unreachable without pubkey

Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it

on: February 27, 2023, 04:56:02 PM

I doubt it was brute force that solved 120 any other way. But either way, it's a great performance. congratulations

Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver

on: February 27, 2023, 04:47:16 PM

Wonderful performance congratulations It will have taken more than 2 years to find it. I'm curious to know the privateKey and whether it's bruteforcing (kangaroo solver/bsgs/bitcrack etc...) or some other way to find it? Congratulations

Bitcoin / Project Development / Re: VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards)

on: January 31, 2023, 08:20:45 PM

Quote

Try this and let me know results:

Code:

WindowsKeySubtracter.exe -f 1 -o 120testx.txt -p 02FDD766926BC7EB713CB57FC71CB066DE3D97379F283BBE6E657016A812DC7735 -n 1000 -r 1:700000000000000000000000000000 -x
pause

I just ran the command line but it doesn't work.

Code:

C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\WindowsKeySubtracter.exe -f 1 -o 120testx.txt -p 02FDD766926BC7EB713CB57FC71CB066DE3D97379F283BBE6E657016A812DC7735 -n 1000 -r 1:700000000000000000000000000000 -x pause
[+] Min range: 1
[+] Max range: 700000000000000000000000000000
0.000000
C:\Users\Laurent>

Nothing is happening

Bitcoin / Project Development / Re: VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards)

on: January 31, 2023, 07:14:11 PM

Quote from: WanderingPhilospher on January 31, 2023, 06:20:43 PM Quote from: Lolo54 on January 31, 2023, 05:53:57 PM hi WanderingPhilospher I wanted to test https://github.com/WanderingPhilosopher/Windows-KeySubtractor/releases but impossible error message at launch 0xc000007b I saw that many encountered this problem how to solve it? Do me a favor, see if you can download the newest .exe and if it works... I just uploaded a new one. I think the issue was if your PC didn't have some of the dependencies, it wouldn't work, but I added those (I think) to the exe file. Try and see. Thanks now it launches without an error message but it doesn't seem to work or am I inserting a wrong command line? Quote C:\Users\Laurent>C:\Users\Laurent\Documents\Bitcoin\WindowsKeySubtracter.exe -p 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630 -n 10 -r 0:32 Min range: 0 Max range: 32 Version: 0.1 [E] there are some missing parameter Usage: -h show this help -b bits For some puzzles you only need a bit range -n number Number of publikeys to be geneted, this numbe will be even -f number Format: 1 for text, 2 for binary -o file Output file -p key Publickey to be substracted compress or uncompress -r A:B range A to B -R Set the publickey substraction Random instead of secuential -x X point only without extra byte of odd/even of Y point it seems that several parameters are missing for the program to run [E] I inserted other commands same message -p 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630 -n 200 -b 120 -p 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630 -n 10 -b 60 -o keysubtracter

Bitcoin / Project Development / Re: VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards)

on: January 31, 2023, 05:53:57 PM

hi WanderingPhilospher I wanted to test https://github.com/WanderingPhilosopher/Windows-KeySubtractor/releases but impossible error message at launch 0xc000007b I saw that many encountered this problem how to solve it?

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 30, 2023, 12:29:08 AM

Quote from: WanderingPhilospher on January 29, 2023, 07:05:02 PM Quote from: Lolo54 on January 29, 2023, 06:25:50 PM Quote from: WanderingPhilospher on January 26, 2023, 08:43:26 PM Quote from: Lolo54 on January 26, 2023, 08:33:47 PM Exactly that's right! Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have." That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol... Thank you for the testing of 14 missing characters, I appreciate it. Quote wif (the last 17 are missing) KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL Compressed address 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol. Can you insert for example the command line you used to perform this search and can you use it randomly? Sure, no problem: Code: VBCr.exe -stop -t 0 -drk 1 -dis 1 -gpu -g 480,512 -r 2900 -begr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac940fcecb3e9857bf1 -endr 6013a6d9493032a55781798cbba36961d73fb72d4a86ac94cfe723cac3c4838 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE pause Note: This is searching with a GPU. You can change it to CPU by adding -t 4 (or whatever number of cores you want to use) and deleting the -gpu, -g flags. You can also redo the -r flag to however often you want the CPU/GPU to generate new random keys. The -r is in millions so if you use -r 10, it will generate new random keys after 10,000,000 keys have been checked. Thanks. can you put an example of using the -rp command?

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 29, 2023, 06:25:50 PM

Quote from: WanderingPhilospher on January 26, 2023, 08:43:26 PM Quote from: Lolo54 on January 26, 2023, 08:33:47 PM Exactly that's right! Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result Well I did say in my original post, "As always, it depends on the program you are running and how much hardware you have." That was a 48 bit range; which could take up to 4-5 hours to check every key, so I leaned on the side of caution and ran with 6 GPUs lol... Thank you for the testing of 14 missing characters, I appreciate it. Quote wif (the last 17 are missing) KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL Compressed address 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE That's a 60 bit range C018588C2B6CC47... I'm gonna have to pass on that one lol. Can you insert for example the command line you used to perform this search and can you use it randomly?

Bitcoin / Project Development / Re: VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards)

on: January 29, 2023, 06:21:57 PM

is it possible to have an example of using the -rp command?

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 26, 2023, 08:56:24 PM

I understand lol ....but how long do you think it would take you to find with your material?

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 26, 2023, 08:33:47 PM

Exactly that's right! Yes nice result but you have 6 nice GPUs . With one GPU let's say you would have taken about 15 min it's a good result If you want to test 17 missing (as you have 6 beautiful GPU ) wif (the last 17 are missing) KwRPC6Be7ukp2fh4rVYU4GrmfSdCweo2RxL Compressed address 1MpqX7tzAWAo1bZv6msHM3mkQ6fHFh2mjE good luck What would be nice is if you post command lines to run

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 26, 2023, 04:55:56 PM

Sorry, I made a mistake in my previous post. here is WIF (the last 14 are missing) KxQxHMsPZatAoe4g2xrZW2RFCXHm38LE5JuB6i?? Compressed address 1PA7i6w5pAvc72zhXJs7n1TpdtQ4isELKc

Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys

on: January 26, 2023, 02:51:04 PM

Quote from: WanderingPhilospher on January 25, 2023, 03:10:06 PM 8 or 9 characters in a month? Depending on location of missing characters, and if they are sequentially missing, which seems to be what you are referring to (a fourth of a piece of paper); 8 or 9 missing from the end can be brute forced solved in seconds. Missing 13 or 14 from the end can be brute force solved in under an hour. I am very curious to see if with the last 14 characters missing you put less than 1 hour to find this WIF WIF (the last 14 are missing) KwLp2q49zihR4tgPrJaWSqcqui Compressed address 1KECKoV4CvqBeJaA1t7EgF2dYd4VQdHRfA Good luck

Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports

on: January 20, 2023, 06:02:14 PM

Quote from: WanderingPhilospher on January 20, 2023, 12:27:52 PM Quote from: Lolo54 on January 20, 2023, 06:48:44 AM hello albert did you manage to adapt keyhunt for a GPU version ? which should be faster No. However, depending on what you want to use, BSGS, Search for private keys, Kangaroo, etc. there are existing programs that incorporate GPUs. Example, BSGS = BSGS Cuda; Kangaroo = Kangaroo by JLP. For searching for private keys, there are many GPU options. I am looking for a bsgs GPU version with random which reads an incoming file not in sequence. I used before this one https://github.com/Etayson/BSGS-cuda but it doesn't offer random and read incoming file in sequential not random. On the other hand, on a single PubKey search, its speed can reach 2 ExaKey/s VS 82 PetaKey/s (KeyHunt) for me for the same search.

Pages: « 1 [2] 3 4 5 6 »