OK, thanks.
So for key #64 it will be less productive to use random I guess...
Topic: BitCrack - A tool for brute-forcing private keys - page 49. (Read 74618 times)
sp_ is it normal to take A LOT longer when using -r?
puzzle #39:
cuBitCrack.exe --keyspace 4000000000:7fffffffff 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNE
Will scan search for a private key between 2 numbers:
274 877 906 944
549 755 813 887
Without the -r parameter the scan is performed linary like a counter 274 877 906 944, 274 877 906 945...
The solution key is
323 724 968 937
Bitcrack will check 48 847 061 993 seeds
with -r Bitcrack will faster if the private key is above 274 877 906 944 + (549 755 813 887- 274 877 906 944)/2
My fork has a random mode. Run with -r --random.
sp_ is it normal to take A LOT longer when using -r?
Code:
Bitcrack sp-mod #4 (https://github.com/sp-hash)
[2021-03-25.17:48:08] [Info] Compression: compressed
[2021-03-25.17:48:08] [Info] Starting at: 0000000000000000000000000000000000000000000000000000004000000000
[2021-03-25.17:48:08] [Info] Ending at: 0000000000000000000000000000000000000000000000000000007FFFFFFFFF
[2021-03-25.17:48:08] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-03-25.17:48:08] [Info] Initializing Tesla V100-SXM2-16GB
[2021-03-25.17:48:09] [Info] Generating 114,688,000 starting points (4375.0MB)
[2021-03-25.17:48:31] [Info] 10.0%
[2021-03-25.17:48:31] [Info] 20.0%
[2021-03-25.17:48:31] [Info] 30.0%
[2021-03-25.17:48:31] [Info] 40.0%
[2021-03-25.17:48:32] [Info] 50.0%
[2021-03-25.17:48:32] [Info] 60.0%
[2021-03-25.17:48:32] [Info] 70.0%
[2021-03-25.17:48:32] [Info] 80.0%
[2021-03-25.17:48:33] [Info] 90.0%
[2021-03-25.17:48:33] [Info] 100.0%
[2021-03-25.17:48:33] [Info] Done
Tesla V100-SXM2- 10825 / 16258MB | 1 target 1568.49 MKey/s (48,857,088,000 total) [00:00:29][2021-03-25.17:49:04] [Info] Address: 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8
Private key: 0000000000000000000000000000000000000000000000000000004B5F8303E9
Compressed: yes
Public key:
022D77CD1467019A6BF28F7375D0949CE30E6B5815C2758B98A74C2700BC006543
[2021-03-25.17:49:04] [Info] No targets remaining
Execution time = 56 seconds
Same key 39 bit range with -r took 361 seconds
Code:
Bitcrack sp-mod #4 (https://github.com/sp-hash)
[2021-03-25.17:49:18] [Info] Compression: compressed
[2021-03-25.17:49:18] [Info] Starting at: 0000000000000000000000000000000000000000000000000000004000000000
[2021-03-25.17:49:18] [Info] Ending at: 0000000000000000000000000000000000000000000000000000007FFFFFFFFF
[2021-03-25.17:49:18] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-03-25.17:49:18] [Info] Generating random starting points
[2021-03-25.17:49:18] [Info] Initializing Tesla V100-SXM2-16GB
[2021-03-25.17:49:18] [Info] Generating 114,688,000 starting points (4375.0MB)
[2021-03-25.17:49:18] [Info] Starting point sample: 0000000000000000000000000000000000000000000000000000007ADA607C21 (39 bit range)
[2021-03-25.17:49:18] [Info] Starting point sample: 0000000000000000000000000000000000000000000000000000004E0381CEB0 (39 bit range)
[2021-03-25.17:49:18] [Info] Starting point sample: 0000000000000000000000000000000000000000000000000000007EBDC9D53C (39 bit range)
[2021-03-25.17:50:07] [Info] 10.0%
[2021-03-25.17:50:09] [Info] 20.0%
[2021-03-25.17:50:09] [Info] 30.0%
[2021-03-25.17:50:10] [Info] 40.0%
[2021-03-25.17:50:10] [Info] 50.0%
[2021-03-25.17:50:10] [Info] 60.0%
[2021-03-25.17:50:10] [Info] 70.0%
[2021-03-25.17:50:11] [Info] 80.0%
[2021-03-25.17:50:11] [Info] 90.0%
[2021-03-25.17:50:11] [Info] 100.0%
[2021-03-25.17:50:11] [Info] Done
Tesla V100-SXM2- 10825 / 16258MB | 1 target 1554.88 MKey/s (387,072,000,000 total) [00:04:05][2021-03-25.17:55:19] [Info] Address: 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8
Private key: 0000000000000000000000000000000000000000000000000000004B5F8303E9
Compressed: yes
Public key:
022D77CD1467019A6BF28F7375D0949CE30E6B5815C2758B98A74C2700BC006543
[2021-03-25.17:55:19] [Info] No targets remaining
Execution time = 361 seconds
And I don't care about speed at all; I care about results...in time.
But still no binary or sourcecode to look at.. Show me some code, and we can talk again.
And I don't care about speed at all; I care about results...in time.
But still no binary or sourcecode to look at.. Show me some code, and we can talk again.
(up to around 44 bits), random is faster, in my tests.
Up to around 44 bits database is faster. The point is that why do you care about the speed in low bit problems? 2^64 and up is more interesting. My mod is based on bitcrack and yes it is scanning bruteforcing all of the solutions. That might be a littlebit stupid, but stupid solutions can still solve problems with enough hashing power. My fork has a random mode. Run with -r --random.
So you have a database that has 17,592,186,044,416 keys in it? Why? And you say it is faster but how long does it take to compute and store 17,592,186,044,416 private keys?
And I don't care about speed at all; I care about results...in time.
(up to around 44 bits), random is faster, in my tests.
Up to around 44 bits database is faster. The point is that why do you care about the speed in low bit problems? 2^64 and up is more interesting. My mod is based on bitcrack and yes it is scanning bruteforcing all of the solutions. That might be a littlebit stupid, but stupid solutions can still solve problems with enough hashing power. My fork has a random mode. Run with -r --random.
Man get outta here. Precomputed keys in a database is not the same as vanbitcracken.
No binary, no sourcecode how can we tell the difference? How do we know that vanbitcracken doesn't use a sql database?
Vanbitcracken uses/generates random points through a range. I said this long ago...in smaller ranges (up to around 44 bits), random is faster, in my tests. It uses the power of the rekey function to dictate how often random points are regenerated. So it can either generate/spread out random points and sequentially start from each random point or regenerate random points every x seconds/keys. AND, it can utilize multiple GPUs!
Bottom line, vanbitcracken using one GTX 1060 card, kicked your GTX 1070Ti and sp mod's a$$...period.
Man get outta here. Precomputed keys in a database is not the same as vanbitcracken.
No binary, no sourcecode how can we tell the difference? How do we know that vanbitcracken doesn't use a sql database?
It is slow? Yet my program found the key in 44 seconds but yours took around 10 minutes?
I have a program that find the key in 1ms. It is written in sql. Local database. Here is the sourcecode. It is OpenSource:
select privatekey from compressed_bitcoinadresses where adress="122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8";
Quote
So you are telling everyone how fast your mod is but it takes your mod over 10 times longer to find the same key, with a better GPU than the one I am using?
I just showed you my 1ms opensource program (puzzle #39). You can show me yours and we can compare them.
Your bitcrack mod found #39 in 9+ minutes, my vanbitcracken found it in 44 seconds. That's what we are comparing, two key searching programs utilizing GPUs. Not some database.
You are announcing all these speeds to the community regarding your bitcrack mod, when I run similar tests, with my program or the original bitcrack, there is no gain/minimal gain in TIME finding keys, regardless of how fast you say or how many MKey/s your mod is getting.
It is slow? Yet my program found the key in 44 seconds but yours took around 10 minutes?
I have a program that find the key in 1ms. It is written in sql. Local database. Here is the sourcecode. It is OpenSource:
select privatekey from compressed_bitcoinadresses where adress="122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8";
Quote
So you are telling everyone how fast your mod is but it takes your mod over 10 times longer to find the same key, with a better GPU than the one I am using?
I just showed you my 1ms opensource program (puzzle #39). You can show me yours and we can compare them.
For the #39, it took the 1060 6GB card exactly 44 seconds to find the key. Start to finish = 44 seconds, with 1 card. Grid size of 3072x512.
sp, is 44 seconds good on an old 1060 card?
sp, is 44 seconds good on an old 1060 card?
No it is slow. should run under 100ms. You can retrieve the precalculated keys from https://privatekeys.pw/ . Since the answer to the puzzle is already known and can be precalculated.
Back to the speed of my bitcrack implementation.
puzzle 39: 2^39 = 549 755 813 888 possible combinations
with a speed of 400 000 000 (400MKeys)
puzzle #38: 274 877 906 944 / 400 000 000 = 1374 seconds (around 12minutes)
puzzle #39: 549 755 813 888 / 400 000 000 = 1374 seconds (around 23minutes)
With 400mkeys and solving puzzle 39 You would expect the program to spend 12-23 minutes. The hashes used to find the solution is printed in the miner window and the speed can easily be verified. Bitcrack sp-mod is working. I see that my fanclub is present already. I welcome you all. Go crack some keys.
The next version will come with more speed.
So you are telling everyone how fast your mod is but it takes your mod over 10 times longer to find the same key, with a better GPU than the one I am using?
My GPU only gets 113 MKey/s and still found the key to #39 in under a minute. But that is slow? But your mod takes 23 minutes and it's fast?
@fxsniper
Here is how my random "BitCrack" works. I call it Randomonium or VanBitKraken (since it is based off of VanitySearch and BitCrack). It can regenerate random points every so many keys based off of user input or user can decide to just let the program create random points throughout a range and search sequentially from each point generated.
With the flags/setup you see below, I am telling the program to search for 1Be2U address, generate new random points every 1600 Mkeys checked. I am also tell the program to search in the 36 bit range (900000000) via the boomT flag and setting the bits via the bitz flag to 32. So all random points will start with a 9 and random 32 bits, as evident by the keys below. I have it to stop once it finds the key, that's why the program stopped. Just a small sample size to show you how it works. I know there are some versions of BitCrack out there that have a random feature but I do not know which ones work. I think BitCrack generates x amount of points (based off of your -b -t -p settings) and spreads those points over the range you have identified in the --keyspace flag, but I could be wrong.
Here is how my random "BitCrack" works. I call it Randomonium or VanBitKraken (since it is based off of VanitySearch and BitCrack). It can regenerate random points every so many keys based off of user input or user can decide to just let the program create random points throughout a range and search sequentially from each point generated.
With the flags/setup you see below, I am telling the program to search for 1Be2U address, generate new random points every 1600 Mkeys checked. I am also tell the program to search in the 36 bit range (900000000) via the boomT flag and setting the bits via the bitz flag to 32. So all random points will start with a 9 and random 32 bits, as evident by the keys below. I have it to stop once it finds the key, that's why the program stopped. Just a small sample size to show you how it works. I know there are some versions of BitCrack out there that have a random feature but I do not know which ones work. I think BitCrack generates x amount of points (based off of your -b -t -p settings) and spreads those points over the range you have identified in the --keyspace flag, but I could be wrong.
Code:
C:\Users\your\Documents\BitRangeFinderWithRandomonium>RandomoniumV1 -t 0 -r 1600 -stop -gpu -gpuId 0 -bitz 32 -boomT 900000000 -o FoundKeysWithRandomonium.txt 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
Rando-monium
Searching For: 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1 [Compressed]
Started at Wed Feb 24 18:41:55 2021
CPU Threads Used: 0
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)
Key 0: 90FB029C9
Key 1: 915AB8BEF
Key 2: 94566471B
Key 3: 9B32AD4C5
Key 10236: 916FC7D4F
Key 10237: 9941AA5CC
Key 10238: 9CA0313F6
Key 10239: 9CD679F6E
Key 0: 971B253A7
Key 1: 9747E23CC
Key 2: 97155A495
Key 3: 95ADB5819
Key 10236: 94C80D1C1
Key 10237: 9718F18A5
Key 10238: 9733219BB
[424.30 Mkey/s][GPU 424.30 Mkey/s][Total 2^30.66][Prob 0.0%][50% in 7.5709e+31y][Found 0]
Key 0: 975D40E2C
Key 1: 94693B865
Key 2: 9CB0359C2
Key 3: 9A7E99691
Key 10236: 997802E90
Key 10237: 9C4F7F057
Key 10238: 9A619E828
[402.27 Mkey/s][GPU 402.27 Mkey/s][Total 2^31.91][Prob 0.0%][50% in 7.98551e+31y][Found 0]
Key 0: 94824A22E
Key 1: 98D8DF9B2
Key 2: 95FF97060
Key 3: 90D7649EB
Key 10236: 99728C9A7
Key 10237: 942FC0681
Key 10238: 9B6305716
[396.73 Mkey/s][GPU 396.73 Mkey/s][Total 2^32.57][Prob 0.0%][50% in 8.09702e+31y][Found 0]
Key 0: 9502B7D4F
Key 1: 9A50EB31E
Key 2: 9137FF051
Key 3: 98459EFC4
Key 10236: 9A4E0E1A3
Key 10237: 955C27269
Key 10238: 9344F13EE
[396.68 Mkey/s][GPU 396.68 Mkey/s][Total 2^33.03][Prob 0.0%][50% in 8.0979e+31y][Found 0]
Key 0: 90713B8A5
Key 1: 95F65F231
Key 2: 96C034F9B
Key 3: 9D5E97324
Key 10236: 9099689AA
Key 10237: 9673E3AB2
Key 10238: 9E37BEC45
[392.72 Mkey/s][GPU 392.72 Mkey/s][Total 2^33.37][Prob 0.0%][50% in 8.17973e+31y][Found 0]
Key 0: 98ECC53D8
Key 1: 98D4A705E
Key 2: 9EE3F71FB
Key 3: 9FCDC5825
Key 10236: 91581FDF1
Key 10237: 96B2A59CF
Key 10238: 9DA85DB2D
[392.74 Mkey/s][GPU 392.74 Mkey/s][Total 2^33.64][Prob 0.0%][50% in 8.1792e+31y][Found 0]
Key 0: 9524454BC
Key 1: 911B85D89
Key 2: 964F741BA
Key 3: 9AA26E965
Key 10236: 93D1494B2
Key 10237: 9680AC923
Key 10238: 9FAFE8130
[392.75 Mkey/s][GPU 392.75 Mkey/s][Total 2^33.87][Prob 0.0%][50% in 8.17905e+31y][Found 0]
Key 0: 997B54EDC
Key 1: 999C24D45
Key 2: 9A1DBE828
Key 3: 9C151CB30
Key 10236: 95EF8F151
Key 10237: 9C899397C
Key 10238: 9A032F0C9
[392.80 Mkey/s][GPU 392.80 Mkey/s][Total 2^34.07][Prob 0.0%][50% in 8.17792e+31y][Found 0]
Key 0: 9E1CD4F93
Key 1: 999311CD2
Key 2: 92FFE0C75
Key 3: 917BB7886
Key 10236: 951B19828
Key 10237: 908EAA926
Key 10238: 9C6AEA820
Key 10239: 9AE046F3E
C:\Users\your\Documents\BitRangeFinderWithRandomonium>pause
Press any key to continue . . .
Randomonium or VanBitKraken is available; please share to us...
For the #39, it took the 1060 6GB card exactly 44 seconds to find the key. Start to finish = 44 seconds, with 1 card. Grid size of 3072x512.
sp, is 44 seconds good on an old 1060 card?
sp, is 44 seconds good on an old 1060 card?
No it is slow. should run under 100ms. You can retrieve the precalculated keys from https://privatekeys.pw/ . Since the answer to the puzzle is already known and can be precalculated.
Back to the speed of my bitcrack implementation.
puzzle 39: 2^39 = 549 755 813 888 possible combinations
with a speed of 400 000 000 (400MKeys)
puzzle #38: 274 877 906 944 / 400 000 000 = 1374 seconds (around 12minutes)
puzzle #39: 549 755 813 888 / 400 000 000 = 1374 seconds (around 23minutes)
With 400mkeys and solving puzzle 39 You would expect the program to spend 12-23 minutes. The hashes used to find the solution is printed in the miner window and the speed can easily be verified. Bitcrack sp-mod is working. I see that my fanclub is present already. I welcome you all. Go crack some keys.
The next version will come with more speed.
Fan club present? Are you referring to the program and you’re able to see who’s running it?
All these questions, I rather compile from source.
For the #39, it took the 1060 6GB card exactly 44 seconds to find the key. Start to finish = 44 seconds, with 1 card. Grid size of 3072x512.
sp, is 44 seconds good on an old 1060 card?
sp, is 44 seconds good on an old 1060 card?
No it is slow. should run under 100ms. You can retrieve the precalculated keys from https://privatekeys.pw/ . Since the answer to the puzzle is already known and can be precalculated.
Back to the speed of my bitcrack implementation.
puzzle 39: 2^39 = 549 755 813 888 possible combinations
with a speed of 400 000 000 (400MKeys)
puzzle #38: 274 877 906 944 / 400 000 000 = 1374 seconds (around 12minutes)
puzzle #39: 549 755 813 888 / 400 000 000 = 1374 seconds (around 23minutes)
With 400mkeys and solving puzzle 39 You would expect the program to spend 12-23 minutes. The hashes used to find the solution is printed in the miner window and the speed can easily be verified. Bitcrack sp-mod is working. I see that my fanclub is present already. I welcome you all. Go crack some keys.
The next version will come with more speed.
THIS ...
Is why I am interested in a chat and a collaboration - we have ALL this equipment now, no need to buy anything. I will fill you in on how BIG we actually are when we chat. Let's start.
Skype - chrysophylax69
BCTThread - in my Sig As well as Discord Server Connection
#crysx
Is why I am interested in a chat and a collaboration - we have ALL this equipment now, no need to buy anything. I will fill you in on how BIG we actually are when we chat. Let's start.
Skype - chrysophylax69
BCTThread - in my Sig As well as Discord Server Connection
#crysx
I'm a bit busy with Kangaroo right now as I said earlier (I have a client waiting on me to finish tuning the 256-bit Int class so he can pay me the rest of my contract money) then I want to try to insert that into VanitySearch as well.
When I have some free time I will talk with you about this, I promise
I am here ...
Have been for 10.5 years. Not going to disappear or hide.
Speak as soon as you are able. Looking forward to it.
TimeZones may be an issue also, but we will work around that as well. I work 15Hours a day 7 Days a week in this Industry, so don;t be afraid to message any time. I'm in Australia.
#crysx
THIS ...
Is why I am interested in a chat and a collaboration - we have ALL this equipment now, no need to buy anything. I will fill you in on how BIG we actually are when we chat. Let's start.
Skype - chrysophylax69
BCTThread - in my Sig As well as Discord Server Connection
#crysx
Is why I am interested in a chat and a collaboration - we have ALL this equipment now, no need to buy anything. I will fill you in on how BIG we actually are when we chat. Let's start.
Skype - chrysophylax69
BCTThread - in my Sig As well as Discord Server Connection
#crysx
I'm a bit busy with Kangaroo right now as I said earlier (I have a client waiting on me to finish tuning the 256-bit Int class so he can pay me the rest of my contract money) then I want to try to insert that into VanitySearch as well.
When I have some free time I will talk with you about this, I promise
I think I'll end up making the speed tweaks myself after I wrap up with Kangaroo-256, without waiting for anyone.
This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.
Quote
hi, where can i find your vanbitcracken?
I haven't released it or put it out to the public due to same concerns others have about closed source. I never want to get blamed for a virus or any type of "hacking". I have put a few things out, but have stopped.This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
Pool ...
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.
THIS ...
Is why I am interested in a chat and a collaboration - we have ALL this equipment now, no need to buy anything. I will fill you in on how BIG we actually are when we chat. Let's start.
Skype - chrysophylax69
BCTThread - in my Sig As well as Discord Server Connection
#crysx
I think I'll end up making the speed tweaks myself after I wrap up with Kangaroo-256, without waiting for anyone.
This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.
Quote
hi, where can i find your vanbitcracken?
I haven't released it or put it out to the public due to same concerns others have about closed source. I never want to get blamed for a virus or any type of "hacking". I have put a few things out, but have stopped.This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
Pool ...
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.
Care to share the source code? I’m really wondering what’ve been missing all this time.
sp_? ...
Share THIS Source Code? Pfft!
Read up on what I wrote about this guy and go to his spmod thread in his history of how he deals with code AND people. When the code is useless, he releases - Maybe!
He uses GNU Open Source Public Code, makes changes and PRIVATELY distributes it breaking EVERY direction in the GNU License.
Rune is not a man that knows fairness, equality AND Legality.
As for ordering a new card or two? For ALL the cashflow he has sucked out of the communities he has sold rubbish to the last 6 years, I am amazed that a new card is being purchased NOW that he has come out the rock he lived under for so long MINING (yes - GPU Mining) while everyone else was struggling.
Be VERY Careful of this person. Very Very VERY careful.
#crysx
Jump to: