Bitcoin Forum
June 15, 2024, 12:08:07 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: January 06, 2023, 03:22:37 PM
Quote from: WanderingPhilospher on January 04, 2023, 02:08:54 PM
Quote from: minime99999 on January 04, 2023, 09:04:32 AM
hi
i was testing this and it found private key.
what does 153869ACC5B mean? doesn't look like a private key, its too short.


[2023-01-04.16:57:39] [Info] Found key for address '1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E'. Written to 'Found.txt'
[2023-01-04.16:57:39] [Info] Address     : 1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E
Private key : 153869ACC5B
Compressed  : yes
Public key  : 03B357E68437DA273DCF995A474A524439FAAD86FC9EFFC300183F714B0903468B


It leaves out the leading zeros. So if you are looking for the longer version of this private key, it is:

00000000000000000000000000000000000000000000000000000153869ACC5B
thank you
2  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: January 05, 2023, 10:27:58 AM
how to ask vanitysearch to search for classic bitcoin address and segwit too?
3  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: January 04, 2023, 09:04:32 AM
hi
i was testing this and it found private key.
what does 153869ACC5B mean? doesn't look like a private key, its too short.


[2023-01-04.16:57:39] [Info] Found key for address '1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E'. Written to 'Found.txt'
[2023-01-04.16:57:39] [Info] Address     : 1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E
Private key : 153869ACC5B
Compressed  : yes
Public key  : 03B357E68437DA273DCF995A474A524439FAAD86FC9EFFC300183F714B0903468B
4  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: January 04, 2023, 01:29:00 AM
Quote from: WhyFhy on January 03, 2023, 02:31:26 PM
Quote from: minime99999 on January 03, 2023, 01:34:34 PM
hi
im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.
I ran GPU memory test and it says no error.

any idea what is the problem?



[Building lookup32 100.0%]
Search: 6219 prefixes (Lookup size 2) [Compressed]
Start Tue Jan  3 21:29:45 2023
Base Key: BD6291C1DE2447068E663194E0DDFBE0C72CD78A8177B51CAE080716AD7496F3
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[404.78 Mkey/s][GPU 404.78 Mkey/s][Total 2^32.43][Prob 31.4%][50% in 00:00:11][Found 33]  ^C
C:\Users\abc\Desktop>


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 82 addresses (Lookup size 82,[1,1]) [Compressed]
Start Tue Jan  3 21:32:26 2023
Base Key: 5323DAB06CE0DAC8D3C8E5191F1D6DA70ABFC8F6D9188B89C186845E543C2674
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Launch: an illegal memory access was encountered


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 15 addresses (Lookup size 15,[1,1]) [Compressed]
Start Tue Jan  3 21:32:34 2023
Base Key: A6D841113DFC9539F68F8FF5345D7AECC1A62A4A3651FD86ECF6D3696C3A9644
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[1295.00 Mkey/s][GPU 1295.00 Mkey/s][Total 2^32.88][Prob 0.0%][50% in 2.48055e+31y][Found 0]

Again.
What version are of VS you running?
What version of cuda?
It's a probably a Cuda error combined with a poor VM setup.
We need more information.
And initial feedback to previous suggestions would help us troubleshoot. 



thx for the reply.
nvm i just return the card, could be faulty.
5  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: January 03, 2023, 01:34:34 PM
hi
im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.
I ran GPU memory test and it says no error.

any idea what is the problem?



[Building lookup32 100.0%]
Search: 6219 prefixes (Lookup size 2) [Compressed]
Start Tue Jan  3 21:29:45 2023
Base Key: BD6291C1DE2447068E663194E0DDFBE0C72CD78A8177B51CAE080716AD7496F3
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[404.78 Mkey/s][GPU 404.78 Mkey/s][Total 2^32.43][Prob 31.4%][50% in 00:00:11][Found 33]  ^C
C:\Users\abc\Desktop>


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 82 addresses (Lookup size 82,[1,1]) [Compressed]
Start Tue Jan  3 21:32:26 2023
Base Key: 5323DAB06CE0DAC8D3C8E5191F1D6DA70ABFC8F6D9188B89C186845E543C2674
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Launch: an illegal memory access was encountered


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 15 addresses (Lookup size 15,[1,1]) [Compressed]
Start Tue Jan  3 21:32:34 2023
Base Key: A6D841113DFC9539F68F8FF5345D7AECC1A62A4A3651FD86ECF6D3696C3A9644
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[1295.00 Mkey/s][GPU 1295.00 Mkey/s][Total 2^32.88][Prob 0.0%][50% in 2.48055e+31y][Found 0]
6  Bitcoin / Development & Technical Discussion / Re: VanitySearch (Yet another address prefix finder) on: January 01, 2023, 02:12:03 AM
why do i occasionally get this error after running the program for few hours?


Start Sun Jan  1 00:21:00 2023
Base Key: C6AB3FFC716A4DF46849D6887E7327EE78DE482B370BB5AF58DD815F5A449504
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[106.21 Mkey/s][GPU 106.21 Mkey/s][Total 2^40.40][Prob 0.0%][50% in 3.02455e+32y][Found 0]  GPUEngine: Launch: unknown error
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!