Has anybody managed to remove the limiter while using a x16 to x16 riser? My stupid fucking motherboard has the 2 pci3 slots too close to each other and my 2 3060s won't fit at the same time.

The annoying part is that the offending region of memory is 32-bit aligned

Doesn't work. The 30 series problem is code related, not a PTX compile issue.

All four mods are not working in 30 series GPUs waiting for your 5th mod

For me #4 and #5 finished the same search in the exact same amount of time, so no difference on #4 vs #5 on my side  

On the one hand, of course you are right. But we are discussing a bruteforce program here. For bruteforce, the only indicator of the quality of work is important - it is the number of keys/addresses per second.

cubitcrack --keyspace 4B00000000:4C00000000 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8 -p 100


Bitcrack sp-mod #4 (https://github.com/sp-hash)


[2021-03-26.08:49:07] [Info] Compression: compressed
[2021-03-26.08:49:07] [Info] Starting at: 0000000000000000000000000000000000000000000000000000004B00000000
[2021-03-26.08:49:07] [Info] Ending at:   0000000000000000000000000000000000000000000000000000004C00000000
[2021-03-26.08:49:07] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2021-03-26.08:49:07] [Info] Initializing GeForce GTX 1070 Ti
[2021-03-26.08:49:07] [Info] Generating 1,945,600 starting points (74.2MB)
[2021-03-26.08:49:08] [Info] 10.0%
[2021-03-26.08:49:08] [Info] 20.0%
[2021-03-26.08:49:08] [Info] 30.0%
[2021-03-26.08:49:08] [Info] 40.0%
[2021-03-26.08:49:08] [Info] 50.0%
[2021-03-26.08:49:08] [Info] 60.0%
[2021-03-26.08:49:08] [Info] 70.0%
[2021-03-26.08:49:08] [Info] 80.0%
[2021-03-26.08:49:08] [Info] 90.0%
[2021-03-26.08:49:09] [Info] 100.0%
[2021-03-26.08:49:09] [Info] Done
GeForce GTX 1070 416 / 8192MB | 1 target 282.24 MKey/s (1,533,132,800 total) [00:00:03][2021-03-26.08:49:14] [Info] Address:     122AJh
LEfkFBaGAd84pLp1kfE7xK3GdT8
                             Private key: 0000000000000000000000000000000000000000000000000000004B5F8303E9
                             Compressed:  yes
                             Public key:
                             022D77CD1467019A6BF28F7375D0949CE30E6B5815C2758B98A74C2700BC006543

[2021-03-26.08:49:14] [Info] No targets remaining
Execution time = 7 seconds

GeForce GTX 1070 312 / 8192MB | 1 target 200.62 MKey/s (1,456,537,600 total) [00:00:05][2021-03-26.08:59:19] [Info] Address:     122AJhK
LEfkFBaGAd84pLp1kfE7xK3GdT8
                             Private key: 0000000000000000000000000000000000000000000000000000004B5F8303E9
                             Compressed:  yes
                             Public key:
                             022D77CD1467019A6BF28F7375D0949CE30E6B5815C2758B98A74C2700BC006543

sp_ is it normal to take A LOT longer when using -r?

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.

Man get outta here. Precomputed keys in a database is not the same as vanbitcracken.

It is slow? Yet my program found the key in 44 seconds but yours took around 10 minutes?  

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?

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?

With Vanitysearch version 1.19, I get 1100 Mk / s with 3 gtx 970.
with your version I get 690 Mk / s

- causal search in a range
- set the search bits

1060 6GB card, 25 seconds total time, start to finish.

Successfully launched with -b 68