[ARCHIVE] Bitcoin challenge discusion

[PietCoin97]

i make random from 347AE147AE147AE1:4000000000000000 with 120 Shares with 3 nvidia Cards

i search also from beginning and in the middle all low spaces between all with random and share Funktion

all with Shell script automated restart after 20 min

Looks like that

Code:

timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120

Maybe i help some newbies here

[bulleteyedk]

i have never used the share function, thanks for posting info of how to use that 

-b should be = GPU compute units x1 or x2 - so this is specific to your GPU
-t is number of threads that will run pr. block
-p is number of keys pr. process

regards your range other have posted these scanned ranges from 34xx to 40xx as below:

Code:

342D5C6012D65200:342D5C7A5ABE1200
3469B57012D65200:3469B58334E89200
346F59016D4B1200:346F59122D9F9200
347EB5016D4B1200:347EB517E4A2D200
347EB590134B1200:347EB59B86CFD200
348D7B106D4B1200:348D7B2110539200
348D7B406D4B1200:348D7BA049D21200
3490BE2011975200:3490BE3028DA9200
3495B01801975200:3495B01E88AF5200
349EB12C01975200:349EB1345FECD200
349FA68001975200:349FA6D96B9B1200
34B0F6901126D200:34B0F691E0689200
34B2E60130689200:34B2E6F130689200
34B2E60130689200:34B2E607F83F9200
34ccccbde61a2d01:34cccd086798cd01
34cccccdc0f0cd01:34cccd086798cd01
34E65901C3059000:34E65908FE959000
35B62D12BBAAE400:35B62D97FAFEE400
35B6EA0DA4B7AA00:35B6EA42BBAAE400
38BD94011E960600:38BD941FF6180600
38BD94211E960600:38BD94411E960600
38BD94411E960600:38BD9451840CCE00
38BD94611E960600:38BD94911E960600
38BD94911E960600:38BD94AF35390600
38BD94B11E960600:38BD94CC43CE0600
3961B406A89706AE:3961CBBAE38006AF
39CC4FD64D7206AF:39CC5B89073486AF
3A54B01194BCB600:3A54B11194BCB600
3A54B11194BCB600:3A54B21194BCB600
3A54B21194BCB600:3A54B31194BCB600
3A54B31194BCB600:3A54B32BD3F9B600
3A54B41194BCB600:3A54B42C6838E200
3A54B51194BCB600:3A54B5473E0AB600
3A54B61194BCB600:3A54B6422EC0F600
3B469D313E960600:3B469D5615400600
3B469E013E960600:3B469E14433D0600
3B469E201E960600:3B469EB5A2F40600
3B469E64B6668600:3B469EB5A2F40600
3B469F013E960600:3B469F123EA30600
3B469F313E960600:3B469F43B96BC600
3B469F613E960600:3B469F6B793D0600
3b5c3ea5c8e2db12:3b5c3f220b62db12
3b5c3f220b62db12:3b5c4283bb62db12
3B8EAC0100000000:3B8EAC1C3247C000
3B96D40201D19600:3B96D412686D5600
3B96D435016D5600:3B96D439BB24D600
3B96D435016D5600:3B96D43F6CC19600
3B96D462016D5600:3B96D46399C09600
3B96D464016D5600:3B96D466C60B9600
3B96D467016D5600:3B96D470B1E55600
3B96D870116D5600:3B96D872732B1600
3B96D874016D5600:3B96D87BE16B1600
3B96D87C016D5600:3B96D8818E535600
3B96D8B2016D5600:3B96D8BCF2F0D600
3B96D8BD016D5600:3B96D8C373351600
3B9D641F628CB600:3B9D64EA6D4F3600
3BD46A25016D5600:3BD46A28E0071600
3BD46A2B016D5600:3BD46A2DB93A5600
3BD46A2E016D5600:3BD46A305DACD600
3BD46A35016D5600:3BD46A3863841600
3BD46A3863841600:3BD46A3E00E4D600
3BD46A52016D5600:3BD46A562E271600
3BD46A58016D5600:3BD46A5B47709600
3BD46A5E016D5600:3BD46A6031BAD600
3BD46A91016D5600:3BD46A9360BA1600
3BD46A96016D5600:3BD46A9852141600
3BD46A9A016D5600:3BD46A9FCAC01600
3BD46C52016D5600:3BD46C57BA455600
3BD46C57016D5600:3BD46C6196C71600
3BE7860492443600:3BE78644F1C23600
3BE786A00E80F600:3BE786AA05C5F600
3BE786B011C23600:3BE786BBF1EB7600
3C13B4010D2BF600:3C13B445E33DF600
3C14B401C26C3600:3C14B421C26C3600
3C14B421C26C3600:3C14B436F04C3600
3C14B621C26C3600:3C14B64708E73600
3C14B671C26C3600:3C14B68401CF3600
3C15B405E33DF600:3C15B436255E3600
3C23B401C26C3600:3C23B42B407E3600
3C25B901C26C3600:3C25B9423F363600
3C52E605E33DF600:3C52E6303597B600
3C569520F1000000:3C5695AECBD80000
3C59B520F1000000:3C59B5383CBEC000
3C81E705E33DF600:3C81E74F628CB600
3C9B472E01000000:3C9B49565CE1C000
3CA4D520F1000000:3CA4D57FB1E4D800
3CA4D620F1000000:3CA4D6F832AA0000
3CA5291101600000:3CA529121D304000
3CA5291501600000:3CA52919EC87C000
3CA5291C01600000:3CA5292414A2C000
3CA529A201600000:3CA529A63E948000
3CA529B201600000:3CA529B5B7150000
3CA529B601600000:3CA529BE31EEC000
3CA5E43017100000:3CA5E43193EC0000
3CA5E43501600000:3CA5E43F15F10000
3CA5E46017100000:3CA5E4618BFCC000
3CA5E46201600000:3CA5E463697B8000
3CA5E46701600000:3CA5E46874780000
3CA5E49017100000:3CA5E49181004000
3CA62E1051600000:3CA62EC25B60C000
3CAA6015C05F2934:3CAA60A1957DA934
3D0E9B850119B600:3D0E9B8A486B3600
3D0F9B850119B600:3D0F9B8B97807600
3D15B6010D2BF600:3D15B8648B60A600
3D16B8310D2BF600:3D16B8CF31CA7600
3D1E9B850119B600:3D1E9B9015677600
3D1F9B850119B600:3D1F9B8C875EB600
3D29B6010D2BF600:3D29B66C56FDF600
3D29B67001FDF600:3D29B671E8713600
3D29B67401FDF600:3D29B679F1283600
3D29B67C01FDF600:3D29B6802CE2F600
3D29B68011FDF600:3D29B688D8B23600
3D29B82011FDF600:3D29B82703F23600
3D29B82901FDF600:3D29B82FEA2E3600
3D29B862012DF600:3D29B864459FB600
3D29B867012DF600:3D29B870F2587600
3D2F9B850119B600:3D2F9B8ACC413600
3D438B0168BDF600:3D438B4168BDF600
3D49B6011119B600:3D49B65454687600
3D49B67014687600:3D49B68C8FAAF600
3D49B68D01AAF600:3D49B692BE2C7600
3D4E9B801119B600:3D4E9BD201A9B600
3D5B87091119B600:3D5B87590DC8F600
3D5B8E091119B600:3D5B8E09D8809600
3D5B8E29D8809600:3D5B8E49D8809600
3D5B8E49D8809600:3D5B8E69D8809600
3D5B8E69D8809600:3D5B8E89D8809600
3D65C840090D3000:3D65C84CBE39B000
3D693B0401000000:3D693BAD952D3000
3D69B4010D2BF600:3D69B466E938B600
3D69B4501F19B600:3D69B45FB286F600
3D6AB3801119B600:3D6AB3813B8FF600
3D6AB3820119B600:3D6AB38C77EEF600
3D6AB38D0119B600:3D6AB38E13C23600
3D6AB38F0119B600:3D6AB3930F4EF600
3D6B9402628CB600:3D6B941172C03600
3D6B945022C03600:3D6B94F951E87600
3D76B5010D2BF600:3D76B560C4587600
3D76B5810D2BF600:3D76B7A372E7F600
3ddc8bab2da2c001:3ddc9bab2da2cf01
3ddc8bb176f60f01:3ddc9bab2da2cf01
3E16D4301101E934:3E16D4901101E934
3E26D4301101E934:3E26D4A1EEC9A934
3E2B36A01101E934:3E2B36AE622B2934
3E408B2011C01600:3E408B28EC989600
3E408B9011C01600:3E408BDF50015600
3E469A2501309600:3E469A270760D600
3E469A290160D600:3E469A2C0F3D1600
3E469A2E0160D600:3E469A30D4A51600
3E469A3501309600:3E469A3E1875D600
3E469A5201309600:3E469A5424ACD600
3E469A5801309600:3E469A610F4E1600
3E469A62014E1600:3E469A65A7249600
3E469A6701249600:3E469A691D4DD600
3E469A6A014DD600:3E469A73BB89D600
3E469A740189D600:3E469A7700C01600
3E469A7C0189D600:3E469A9C4CC01600
3E469AB01CC01600:3E469AB9866B1600
3E469AC011C01600:3E469AC26A561600
3E46D2501101E934:3E46D29751F96934
3E46D5201101E934:3E46D5305F33A934
3E49B850158CE934:3E49BAB87A2E6934
3E65B1700101E934:3E65B241C89EE934
3E67D490158CE934:3E67D64E56E22934
3E6AD359D8809600:3E6AD3743D181600
3E6D79401101E934:3E6D7A22758CE934
3E6DA720758CE934:3E6DB120758CE934
3E96D480105F2934:3E96D4906101E934
3E96D4910101E934:3E96D5056C796934
3e96e6dbb2c48134:3e96e74ea8c48134
3f5c29cc5635ca00:3f5c2b48ebb5ca00

[PietCoin97]

great but these already searched spaces are only a little piece of it

[paniker]

i make random from 347AE147AE147AE1:4000000000000000 with 120 Shares with 3 nvidia Cards

i search also from beginning and in the middle all low spaces between all with random and share Funktion

all with Shell script automated restart after 20 min

Looks like that

Code:

timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 1/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 2/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 3/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120
timeout 20m ./cuBitCrack.exe -d 0 -i addr.txt -c -o found1.txt -r --keyspace 347AE147AE147AE1:4000000000000000 -b 15 -t 512 -p 3200 --share 4/120

Maybe i help some newbies here

not understand, can you wrote step buy step what are happening)))
addr.txt - you already got it?
 -r what is it?

[bulleteyedk]

-i addr.txt loads the wallets adr. you want to check against

edit: i really don't know either what -r does 

from the readme file:

Code:

xxBitCrack.exe [OPTIONS] [TARGETS]

Where [TARGETS] are one or more Bitcoin address

Options:

-i, --in FILE
    Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

-o, --out FILE
    Append private keys to FILE, one per line

-d, --device N
    Use device with ID equal to N

-b, --blocks BLOCKS
    The number of CUDA blocks

-t, --threads THREADS
    Threads per block

-p, --points NUMBER
    Each thread will process NUMBER keys at a time

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

	START:END start at key START, end at key END
	START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
	:+COUNT start at key 1 and end at key 1 + COUNT

-c, --compressed
    Search for compressed keys (default). Can be used with -u to also search uncompressed keys

-u, --uncompressed
    Search for uncompressed keys, can be used with -c to search compressed keys

--compression MODE
    Specify the compression mode, where MODE is 'compressed' or 'uncompressed' or 'both'

--list-devices
    List available devices

--stride NUMBER
    Increment by NUMBER

--share M/N
    Divide the keyspace into N equal sized shares, process the Mth share

--continue FILE
    Save/load progress from FILE

Use the `-b,` `-t` and `-p` options to specify the number of blocks, threads per block, and keys per thread.

### Choosing the right parameters for your device

GPUs have many cores. Work for the cores is divided into blocks. Each block contains threads.

There are 3 parameters that affect performance: blocks, threads per block, and keys per thread.


`blocks:` Should be a multiple of the number of compute units on the device. The default is 32.

`threads:` The number of threads in a block. This must be a multiple of 32. The default is 256.

`Keys per thread:` The number of keys each thread will process. The performance (keys per second)
increases asymptotically with this value. The default is256. Increasing this value will cause the
kernel to run longer, but more keys will be processed.

[vimp666]

-i addr.txt loads the wallets adr. you want to check against

edit: i really don't know either what -r does  

from the readme file:

Code:

xxBitCrack.exe [OPTIONS] [TARGETS]

Where [TARGETS] are one or more Bitcoin address

Options:

-i, --in FILE
    Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

-o, --out FILE
    Append private keys to FILE, one per line

-d, --device N
    Use device with ID equal to N

-b, --blocks BLOCKS
    The number of CUDA blocks

-t, --threads THREADS
    Threads per block

-p, --points NUMBER
    Each thread will process NUMBER keys at a time

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

	START:END start at key START, end at key END
	START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
	:+COUNT start at key 1 and end at key 1 + COUNT

-c, --compressed
    Search for compressed keys (default). Can be used with -u to also search uncompressed keys

-u, --uncompressed
    Search for uncompressed keys, can be used with -c to search compressed keys

--compression MODE
    Specify the compression mode, where MODE is 'compressed' or 'uncompressed' or 'both'

--list-devices
    List available devices

--stride NUMBER
    Increment by NUMBER

--share M/N
    Divide the keyspace into N equal sized shares, process the Mth share

--continue FILE
    Save/load progress from FILE

Use the `-b,` `-t` and `-p` options to specify the number of blocks, threads per block, and keys per thread.

### Choosing the right parameters for your device

GPUs have many cores. Work for the cores is divided into blocks. Each block contains threads.

There are 3 parameters that affect performance: blocks, threads per block, and keys per thread.


`blocks:` Should be a multiple of the number of compute units on the device. The default is 32.

`threads:` The number of threads in a block. This must be a multiple of 32. The default is 256.

`Keys per thread:` The number of keys each thread will process. The performance (keys per second)
increases asymptotically with this value. The default is256. Increasing this value will cause the
kernel to run longer, but more keys will be processed.

-r is random. this is from pikachu release

Code:

xxBitCrack.exe [OPTIONS] [TARGETS]

Where [TARGETS] are one or more Bitcoin address

Options:

-i, --in FILE
    Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

-o, --out FILE
    Append private keys to FILE, one per line

-d, --device N
    Use device with ID equal to N

-b, --blocks BLOCKS
    The number of CUDA blocks

-t, --threads THREADS
    Threads per block

-p, --points NUMBER
    Each thread will process NUMBER keys at a time

-r, --random
    Each point will start in random KEYSPACE

--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

[PietCoin97]

i use this version https://github.com/ZielarSRC/BitCrack

[vimp666]

ZielarSRC/BitCrack
forked from pikachunakapika/BitCrack.and in my opinion unchanged.

[PietCoin97]

yeah is unchanged

[zielar]

This btcpass - clean (without a virus). It is necessary to pay for this btcpass?

No ... The purpose for which this application is useful here appears in the start log regardless of whether you have purchased a license ... The license includes program functions, and in this case we are interested in a small add-on.

By the way, who is the "creator" of these bitcoin challenge transactions? Does somebody know his name or any other information?

We do not have such information
I know that in 2015 - the creator of this challenge created a thread in this topic ... I don't have a link anymore because I don't need it anymore.
Forget that anyone knows who this person is ... None of these people, for known reasons, do not introduce themselves by name and does not attach a biography with the address of residence and a photo creating such a challenge.

i use the random funktion and the --share funktion
so when i take two hex keys and make share and betweeen these shares i take the random starting point generation is it good ?
with -p 3500 i have 24576000 random starting points between the shares
and i also run pollard kangaroo for 105
i have 3 gtx 1070 each one make 250 Mkey/s

It is not possible to run the "random" function together with "--share".
The way your configuration works assumes the very high probability that you are scanning the same ranges over and over again... although I do not deny it, because every way is good!

i have never used the share function, thanks for posting info of how to use that  
-b should be = GPU compute units x1 or x2 - so this is specific to your GPU
-t is number of threads that will run pr. block
-p is number of keys pr. process

First of all, many thanks for placing the results in the 'CODE' tag according to my request :-)
In answer to your question:
-b = CU number ... i.e. x1
-t = to be max. try 512, and if it doesn't start, set 256 (because that is how much max will start)
-p = as you wrote ... but these are all theoretical concepts that in themselves will not indicate the best option. -p is the only option that needs your time to test different combinations to values that you already know :-)

not understand, can you wrote step buy step what are happening)))
addr.txt - you already got it?
 -r what is it?

-r was turn ON random mode:

-r, --random
    Each point will start in random KEYSPACE

-i addr.txt - this is the input file containing the list of addresses to which you are looking for the key. He has these addresses in the addr.txt file

ZielarSRC/BitCrack
forked from pikachunakapika/BitCrack.and in my opinion unchanged.

The script itself is no different from the pikachupik version, while its version is for CUDA 9.2. - my fork is configured and has an .exe file running on CUDA 10.1

[PietCoin97]

--share Funktion is possible it shows no error and it works it show the right output everytime with right Keyspace.

--stride don't work and - - save file also not work with - r Funktion.

Why it should not work it never showed an error to me.

when you use random funktion -r with --share then it works

so between the shares it will create all random starting points in the given search space.

Card 1

Code:

[2019-08-25.13:59:57] [Info] Share 22 of 120 
[2019-08-25.13:59:57] [Info] Compression: compressed 
[2019-08-25.13:59:57] [Info] Starting at: 0000000000000000000000000000000000000000000000003D0624DD2F1A9F72 
[2019-08-25.13:59:57] [Info] Ending at: 0000000000000000000000000000000000000000000000003D1EB851EB851E6A 
[2019-08-25.13:59:57] [Info] Generating random starting points 
[2019-08-25.13:59:57] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001 
[2019-08-25.13:59:57] [Info] Initializing GeForce GTX 1070 
[2019-08-25.13:59:57] [Info] Generating 24,576,000 starting points (937.5MB) 
[2019-08-25.13:59:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003D067C0C08D9913A (62 bit range) 
[2019-08-25.13:59:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003D0E86349A31F8A6 (62 bit range) 
[2019-08-25.13:59:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003D14CE227B0C1BFD (62 bit range)

Card 2

Code:

 [2019-08-26.06:20:27] [Info] Share 62 of 120
[2019-08-26.06:20:27] [Info] Compression: compressed
[2019-08-26.06:20:27] [Info] Starting at: 0000000000000000000000000000000000000000000000003A5604189374BC36
[2019-08-26.06:20:27] [Info] Ending at:   0000000000000000000000000000000000000000000000003A6E978D4FDF3B2E
[2019-08-26.06:20:27] [Info] Generating random starting points
[2019-08-26.06:20:27] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-08-26.06:20:27] [Info] Initializing GeForce GTX 1070
[2019-08-26.06:20:27] [Info] Generating 24,576,000 starting points (937.5MB)
[2019-08-26.06:20:27] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003A5C134791C85DB5 (62 bit range)
[2019-08-26.06:20:27] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003A6E19170CB5F70E (62 bit range)
[2019-08-26.06:20:27] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003A5CC0F427A76254 (62 bit range)

Card 3

Code:

 [2019-08-26.06:13:56] [Info] Share 102 of 120
[2019-08-26.06:13:56] [Info] Compression: compressed
[2019-08-26.06:13:56] [Info] Starting at: 0000000000000000000000000000000000000000000000003E2D0E560418931E
[2019-08-26.06:13:56] [Info] Ending at:   0000000000000000000000000000000000000000000000003E45A1CAC0831216
[2019-08-26.06:13:56] [Info] Generating random starting points
[2019-08-26.06:13:56] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-08-26.06:13:56] [Info] Initializing GeForce GTX 1070
[2019-08-26.06:13:57] [Info] Generating 24,576,000 starting points (937.5MB)
[2019-08-26.06:13:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003E342ECDF0ED24D9 (62 bit range)
[2019-08-26.06:13:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003E36BA7C7174EEE2 (62 bit range)
[2019-08-26.06:13:57] [Info] Starting point sample: 0000000000000000000000000000000000000000000000003E418CA94D17F87E (62 bit range)

[paniker]

[/quote]
-r is random. this is from pikachu release

[/quote]


doesn't work in https://github.com/brichard19/BitCrack ?

[PietCoin97]

no this verion of bitcrack dont have random included

[paniker]

no this verion of bitcrack dont have random included

can i scan random and save the result of scan?  hex + addr?

[MrFreeDragon]

no this verion of bitcrack dont have random included

can i scan random and save the result of scan?  hex + addr?

What is your goal? I made for myself such a digital lottery - generated a random number between the range and check the corresponding wallet to it. But it was not bitcrack.
Do you want just a list of random hex+addr? It will not be useful cause it will be difficult later to compare all these random results with the already scanned ranges.

[paniker]

no this verion of bitcrack dont have random included

can i scan random and save the result of scan?  hex + addr?

What is your goal? I made for myself such a digital lottery - generated a random number between the range and check the corresponding wallet to it. But it was not bitcrack.
Do you want just a list of random hex+addr? It will not be useful cause it will be difficult later to compare all these random results with the already scanned ranges.

i am just start using bitcrack, i was using my own algo on python, but it is very slow, very slow...

can you wrote a command - "generated a random number between the range and check the corresponding wallet to it"   also it would be great to save data. hex and addr for base
 
thanks

[MrFreeDragon]

no this verion of bitcrack dont have random included

can i scan random and save the result of scan?  hex + addr?

What is your goal? I made for myself such a digital lottery - generated a random number between the range and check the corresponding wallet to it. But it was not bitcrack.
Do you want just a list of random hex+addr? It will not be useful cause it will be difficult later to compare all these random results with the already scanned ranges.

i am just start using bitcrack, i was using my own algo on python, but it is very slow, very slow...

can you wrote a command - "generated a random number between the range and check the corresponding wallet to it"   also it would be great to save data. hex and addr for base
 
thanks

The bitcrack releases do not have such options i guess. But it is open sourced, so you can chhange the code and make this thing for your own release )
PS. I also made my own code on phyton, and it was also very slow ) Like 1Mkey for several hours ) But for fun it was good  )

[MrFreeDragon]

I read again most of the results posted here, and collected them to one table. Of corse results could differ from card to card depending on the settings. I also add the price of the CUDA. I tried to collect some benchmark. If you have some other device - pls, do not hesitate to add 

Code:

1. RTX 2080ti    1,200-1,300M key/sec  (price $1,200-1,500)
2. GTX 1070      250 Mkey/sec          (price $450-550)
3. GTX 1080ti    150 Mkey/sec          (price $700-1,000)
4. GTX 680       109 Mkey/sec          (price $150)
5. RX 480        107 Mkey/sec          (price $130-150)
6. RX 470        105 Mkey/sec          (price $150-300)
7. RX 580        89 Mkey/sec           (price $200-250)
8. RX 560        50 Mkey/sec           (price $100-150)
9. R9 280/290x   20 Mkey/sec           (price $50)

[paniker]

I read again most of the results posted here, and collected them to one table. Of corse results could differ from card to card depending on the settings. I also add the price of the CUDA. I tried to collect some benchmark. If you have some other device - pls, do not hesitate to add 

Code:

1. RTX 2080ti    1,200-1,300M key/sec  (price $1,200-1,500)
2. GTX 1070      250 Mkey/sec          (price $450-550)
3. GTX 1080ti    150 Mkey/sec          (price $700-1,000)
4. GTX 680       109 Mkey/sec          (price $150)
5. RX 480        107 Mkey/sec          (price $130-150)
6. RX 470        105 Mkey/sec          (price $150-300)
7. RX 580        89 Mkey/sec           (price $200-250)
8. RX 560        50 Mkey/sec           (price $100-150)
9. R9 280/290x   20 Mkey/sec           (price $50)

i got RX 580        110-120 Mkey/sec  with no boost

[PietCoin97]

i use the random funktion and the --share funktion
so when i take two hex keys and make share and betweeen these shares i take the random starting point generation is it good ?
with -p 3500 i have 24576000 random starting points between the shares
and i also run pollard kangaroo for 105
i have 3 gtx 1070 each one make 250 Mkey/s

It is not possible to run the "random" function together with "--share".
The way your configuration works assumes the very high probability that you are scanning the same ranges over and over again... although I do not deny it, because every way is good!

Zielar can you please explain to me why random  should not work with share funktion ?