Bitcoin Forum
May 11, 2024, 05:36:30 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: July 06, 2020, 10:16:55 AM
Does anyone have a way of using this type of tool for finding corresponding addresses of multiple public keys at the same time? https://iancoleman.io/bitcoin-key-compression/
And I can use this to check the balances of the addresses. https://awebanalysis.com/en/bitcoin-multiple-address-check-balance/
2  Bitcoin / Development & Technical Discussion / Re: Pollard's kangaroo ECDLP solver on: June 30, 2020, 04:53:00 PM
Can someone please tell me what format this private key is in?

Kangaroo v2.1
Start:1000000000000000000000
Stop :1FFFFFFFFFFFFFFFFFFFFF
Keys :1
Number of CPU thread: 0
Range width: 2^84
Jump Avg distance: 2^42.03
Number of kangaroos: 2^23.32
Suggested DP: 16
Expected operations: 2^43.12
Expected RAM: 6347.6MB
DP size: 16 [0xFFFF000000000000]
GPU: GPU #1 Tesla V100-PCIE-16GB (80x64 cores) Grid(160x128) (207.0 MB used)
SolveKeyGPU Thread GPU#1: creating kangaroos...
GPU: GPU #2 Tesla V100-PCIE-16GB (80x64 cores) Grid(160x128) (207.0 MB used)
SolveKeyGPU Thread GPU#2: creating kangaroos...
GPU: GPU #0 Tesla V100-PCIE-16GB (80x64 cores) Grid(160x128) (207.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
GPU: GPU #3 Tesla V100-PCIE-16GB (80x64 cores) Grid(160x128) (207.0 MB used)
SolveKeyGPU Thread GPU#3: creating kangaroos...
SolveKeyGPU Thread GPU#1: 2^21.32 kangaroos [12.3s]
SolveKeyGPU Thread GPU#2: 2^21.32 kangaroos [12.3s]
SolveKeyGPU Thread GPU#3: 2^21.32 kangaroos [12.3s]
SolveKeyGPU Thread GPU#0: 2^21.32 kangaroos [12.4s]
[7828.45 MK/s][GPU 7828.45 MK/s][Count 2^43.22][Dead 2][24:56 (Avg 20:24)][4.8/6.9GB]
Key# 0 [1S]Pub:  0x0329C4574A4FD8C810B7E42A4B398882B381BCD85E40C6883712912D167C83E73A
       Priv: 0x11720C4F018D51B8CEBBA8
3  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 28, 2020, 08:12:29 PM
I'm getting 734.23 Mkey/s with these parameters -b 64 -t 512 -p 1024 but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue or should I just try to run it on a cloud server or something? Also if someone has a different set of parameters that they think would be better I'm all ears.
1> Press the Windows + R keys at the same time and type mmsys.cpl

2> In the Playback tab, select your sound device, in this case the Headphone.

3> Then select Properties.

4> Click the Advanced tab, then select Restore Defaults and click OK.

5> Restart the system and see if it works this way first

Tried this and no change.
4  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 25, 2020, 08:03:26 PM
Ok sounds interesting and will it save the key to a text file if it finds one? Also any plans to implement GPU support?
5  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 25, 2020, 08:01:28 PM
I just ran Unigine 2 and it got up to 99% utilization and there was no buzzing sound. When I stop BitCrack it will immediately stop making that sound so what else could it be?
6  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 25, 2020, 02:38:33 AM
So if I run this program it might find solutions to these puzzles?
7  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 24, 2020, 04:41:54 PM
Probably crap audio chipset with mass problem ...

$400 Gigabyte mobo with a really good audio chipset. What kind do you have? Mine sounds perfect when the program isn't running.
8  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 24, 2020, 02:16:02 PM
I'm getting 700 Mkey/s with these parameters -b 64 -t 512 -p 1024 but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue or should I just try to run it on a cloud server or something? Also if someone has a different set of parameters that they think would be better I'm all ears.

I doubt BitCrack have audio functionally, most likely the sound was generated from another software.

Open your Audio Manager (such as Volume Mixer on Windows) provided by your OS and find out which application generate that buzzing sound, then mute that application.

It starts when I start the program and it stops when I stop it.
9  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 24, 2020, 11:32:34 AM
Can you please explain what your python code does Andzhig?
10  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 12:59:30 PM
I'm getting 750 Mkey/s (...) but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue (...)?

Unplug headphones.



Then I won't have any sound at all so how does that fix anything?
11  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 12:40:25 PM
I'm getting 734.23 Mkey/s with these parameters -b 64 -t 512 -p 1024 but I'm also hearing a buzzing sound in my headphones while it is running. Is there any way to fix this issue or should I just try to run it on a cloud server or something? Also if someone has a different set of parameters that they think would be better I'm all ears.
12  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 11:46:17 AM
Ok I figured out how to compile it in release mode by reading this https://stackoverflow.com/questions/933739/what-is-the-difference-between-release-and-debug-modes-in-visual-studio. Now I am getting approximately 720 Mkey/s Smiley It is running at 73 Celsius now when it was only 60 Celsius before. I'm using these parameters -d 0 -b 64 -t 512 -p 1024. Are these parameters optimal or no and also can someone explain what that d does and do I even need it? And one more question can I install the 446.14 graphics update in GeForce Experience or does that not support the 10.1 toolkit?
13  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 10:42:59 AM
It looks like this has been talked about before but what does he mean by building it in release mode? https://github.com/brichard19/BitCrack/issues/142. Here is someone trying to explain it but it still doesn't make much sense to me. https://stackoverflow.com/questions/46979464/unable-to-build-in-release-mode-in-visual-studio. Can you explain it in simpler terms for me?
14  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 09:29:52 AM
Now I'm only getting 8.5 with that one you just showed me Grin So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get.

So I tried this and now I get this error code when trying to build the file. I have tried reinstalling the Toolkit and Visual studio a couple of times and I just can't seem to get back the CUDA props and targets files that should be in the Visual Studio folder. So other than just completely uninstalling everything and trying over is there anything else that I can try?

Severity   Code   Description   Project   File   Line   Suppression State
Error   MSB4019   The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk.   cuKeyFinder   C:\Users\bieni\Downloads\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj   59   

Other than changing cuda to 11.0 did you change anything else? If not, just used compiled version from github.

Yeah that cuda props is ugly.  If you don't have it on your computer yet, you will have to download and place it in that folder where it says its not.
some helpful links:
https://cudaeducation.com/cudatargetsnotfound/
https://developer.nvidia.com/cuda-10.1-download-archive-update2


Thanks so much for your help man!  I installed from that link that you gave me and also found this link that explains how to do it manually https://stackoverflow.com/questions/12136808/cuda-4-2-props-and-target-file-is-missing-visual-studio-2010. So I have the program up and running again. Only problem now is that it is still running at 8 Mkey/s. I used those parameters that you had suggested above. So is there anything else I could try to get this running faster?
15  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 23, 2020, 08:29:32 AM
Now I'm only getting 8.5 with that one you just showed me Grin So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
I don't know all the code you changed...here's one way to check real quick. Go download the latest compiled version and run it instead of your compiled cuda 11 version. See what kind of Mkey/s you get.

So I tried this and now I get this error code when trying to build the file. I have tried reinstalling the Toolkit and Visual studio a couple of times and I just can't seem to get back the CUDA props and targets files that should be in the Visual Studio folder. So other than just completely uninstalling everything and trying over is there anything else that I can try?

Severity   Code   Description   Project   File   Line   Suppression State
Error   MSB4019   The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.props" was not found. Confirm that the expression in the Import declaration "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\\BuildCustomizations\CUDA 10.1.props" is correct, and that the file exists on disk.   cuKeyFinder   C:\Users\bieni\Downloads\BitCrack-master\CudaKeySearchDevice\CudaKeySearchDevice.vcxproj   59   
16  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 22, 2020, 07:49:52 AM
Now I'm only getting 8.5 with that one you just showed me Grin So do you think maybe it's because I'm using CUDA v11.0? My GPU runs at 100% load so I'm sure that it's not a problem with energy draw.
17  Bitcoin / Development & Technical Discussion / Re: BitCrack - A tool for brute-forcing private keys on: June 22, 2020, 05:45:26 AM
I tried using BitCrack with CUDA v11.0 and it works if I modify some of the files. I'm only getting around 14 Mkey/s though. Is this because I am not using CUDA v10.1? Also, what would be the optimal parameters for an RTX 2070 GPU?
18  Economy / Gambling / Re: DiceBot (Martingale, Labouchere) for Just-Dice, PRC, 999dice and safedice on: April 05, 2015, 04:20:40 AM
Your strategy did nothing but drain for me Monopoly.
19  Economy / Gambling / Re: DiceBot (Martingale, Labouchere) for Just-Dice, PRC, 999dice and safedice on: March 29, 2015, 08:14:44 PM
Well if it was more useful to me trust me I would pay you well Seuntjie.  But first I have to come up with a usage case for it.
20  Economy / Gambling / Re: DiceBot (Martingale, Labouchere) for Just-Dice, PRC, 999dice and safedice on: March 28, 2015, 10:40:01 PM
So does anyone have a profitable algorithm to use with this bot yet?  I will pay bitcoin to someone who can come up with one that works.
Pages: [1] 2 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!