Author

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 299. (Read 229120 times)

full member
Activity: 282
Merit: 114
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

.........................

.....................



Thanks.

One more thing, about -b -t -p  (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack   -d 1  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack   -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]



racminer - I know that multiplying the value of -b x2 does not affect the result, however I found (in my case) on other cards - a setting that is definitely better. And without hiding the fact that the -p indicator I have exactly the same as you (2560), check what result will be at the setting: -b 36 -t 512 -p 2560 ... if it does not move, reduce the -p value... and share the result... :-)


./clBitCrack -r -c -u -d 1 -b 36 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-28.13:53:24] [Info] Compression: both
Ellesmere        1216/6512MB | 2749473 targets 35.61 MKey/s (603,979,776 total) [00:00:15]


./clBitCrack -r -c -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-27.13:58:26] [Info] Compression: both
Ellesmere        2368/6471MB | 2749473 targets 46.55 MKey/s (1,659,358,937,088 total) [10:01:53]




racminer.... try -t 512 with -b 36... no 256
member
Activity: 245
Merit: 17
Hello does anyone have a complete list of the taken addresses and it's corresponding private keys? from 1-60? Thank you

It's a bit boring to get last 10, they are spread on 20 pages.

1757756a93
2237d05330
4b5f8303e9
e9ae4933d6
153869acc5b
2a21e3a7271
6bd3b27c591
e02b35a358f
122fca143c05
2ec18388d544
6cd610b53cba
ade6d7ce3b9b
174176b015f4d
22bd43c2e9354
75070a1a009d4
efae164cb9e3c
180788e47e326c
236fb6d5ad1f43
57dfa374c1d98f
9d18b63ac4ffdf
1eb25c90795d61c
2c675b852189a21
7496CBB87CAB44F

First 55 are in one message

0000000000000000000000000000000000000000000000000000000000000001 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
0000000000000000000000000000000000000000000000000000000000000003 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
0000000000000000000000000000000000000000000000000000000000000007 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
0000000000000000000000000000000000000000000000000000000000000008 1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
0000000000000000000000000000000000000000000000000000000000000015 1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
0000000000000000000000000000000000000000000000000000000000000031 1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
000000000000000000000000000000000000000000000000000000000000004c 1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
00000000000000000000000000000000000000000000000000000000000000e0 1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
00000000000000000000000000000000000000000000000000000000000001d3 1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
0000000000000000000000000000000000000000000000000000000000000202 1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
0000000000000000000000000000000000000000000000000000000000000483 1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
0000000000000000000000000000000000000000000000000000000000000a7b 1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
0000000000000000000000000000000000000000000000000000000000001460 1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
0000000000000000000000000000000000000000000000000000000000002930 1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
00000000000000000000000000000000000000000000000000000000000068f3 1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW
000000000000000000000000000000000000000000000000000000000000c936 1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY
000000000000000000000000000000000000000000000000000000000001764f 1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm
000000000000000000000000000000000000000000000000000000000003080d 1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE
000000000000000000000000000000000000000000000000000000000005749f 1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w
00000000000000000000000000000000000000000000000000000000000d2c55 1HsMJxNiV7TLxmoF6uJNkydxPFDog4NQum
00000000000000000000000000000000000000000000000000000000001ba534 14oFNXucftsHiUMY8uctg6N487riuyXs4h
00000000000000000000000000000000000000000000000000000000002de40f 1CfZWK1QTQE3eS9qn61dQjV89KDjZzfNcv
0000000000000000000000000000000000000000000000000000000000556e52 1L2GM8eE7mJWLdo3HZS6su1832NX2txaac
0000000000000000000000000000000000000000000000000000000000dc2a04 1rSnXMr63jdCuegJFuidJqWxUPV7AtUf7
0000000000000000000000000000000000000000000000000000000001fa5ee5 15JhYXn6Mx3oF4Y7PcTAv2wVVAuCFFQNiP
000000000000000000000000000000000000000000000000000000000340326e 1JVnST957hGztonaWK6FougdtjxzHzRMMg
0000000000000000000000000000000000000000000000000000000006ac3875 128z5d7nN7PkCuX5qoA4Ys6pmxUYnEy86k
000000000000000000000000000000000000000000000000000000000d916ce8 12jbtzBb54r97TCwW3G1gCFoumpckRAPdY
0000000000000000000000000000000000000000000000000000000017e2551e 19EEC52krRUK1RkUAEZmQdjTyHT7Gp1TYT
000000000000000000000000000000000000000000000000000000003d94cd64 1LHtnpd8nU5VHEMkG2TMYYNUjjLc992bps
000000000000000000000000000000000000000000000000000000007d4fe747 1LhE6sCTuGae42Axu1L1ZB7L96yi9irEBE
00000000000000000000000000000000000000000000000000000000b862a62e 1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR
00000000000000000000000000000000000000000000000000000001a96ca8d8 187swFMjz1G54ycVU56B7jZFHFTNVQFDiu
000000000000000000000000000000000000000000000000000000034a65911d 1PWABE7oUahG2AFFQhhvViQovnCr4rEv7Q
00000000000000000000000000000000000000000000000000000004aed21170 1PWCx5fovoEaoBowAvF5k91m2Xat9bMgwb
00000000000000000000000000000000000000000000000000000009de820a7c 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
0000000000000000000000000000000000000000000000000000001757756a93 14iXhn8bGajVWegZHJ18vJLHhntcpL4dex
00000000000000000000000000000000000000000000000000000022382facd0 1HBtApAFA9B2YZw3G2YKSMCtb3dVnjuNe2
0000000000000000000000000000000000000000000000000000004b5f8303e9 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8
000000000000000000000000000000000000000000000000000000e9ae4933d6 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
00000000000000000000000000000000000000000000000000000153869acc5b 1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E
000000000000000000000000000000000000000000000000000002a221c58d8f 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
000000000000000000000000000000000000000000000000000006bd3b27c591 1PiFuqGpG8yGM5v6rNHWS3TjsG6awgEGA1
00000000000000000000000000000000000000000000000000000e02b35a358f 1CkR2uS7LmFwc3T2jV8C1BhWb5mQaoxedF
0000000000000000000000000000000000000000000000000000122fca143c05 1NtiLNGegHWE3Mp9g2JPkgx6wUg4TW7bbk
00000000000000000000000000000000000000000000000000002ec18388d544 1F3JRMWudBaj48EhwcHDdpeuy2jwACNxjP
00000000000000000000000000000000000000000000000000006cd610b53cba 1Pd8VvT49sHKsmqrQiP61RsVwmXCZ6ay7Z
0000000000000000000000000000000000000000000000000000ade6d7ce3b9b 1DFYhaB2J9q1LLZJWKTnscPWos9VBqDHzv
000000000000000000000000000000000000000000000000000174176b015f4d 12CiUhYVTTH33w3SPUBqcpMoqnApAV4WCF
00000000000000000000000000000000000000000000000000022bd43c2e9354 1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk
00000000000000000000000000000000000000000000000000075070a1a009d4 1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS
000000000000000000000000000000000000000000000000000efae164cb9e3c 15z9c9sVpu6fwNiK7dMAFgMYSK4GqsGZim
00000000000000000000000000000000000000000000000000180788e47e326c 15K1YKJMiJ4fpesTVUcByoz334rHmknxmT
00000000000000000000000000000000000000000000000000236fb6d5ad1f46 19LeLQDmSR8nxFa4v7UdX9SC41mdxP6Rx9
000000000000000000000000000000000000000000000000006abe1f9b67e114 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa
000000000000000000000000000000000000000000000000009d18b63ac4ffdf 17aPYR1m6pVAacXg1PTDDU7XafvK1dxvhi
00000000000000000000000000000000000000000000000001eb25c90795d61c 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz
00000000000000000000000000000000000000000000000002c675b852189a21 1Dn8NF8qDyyfHMktmuoQLGyjWmZXgvosXf
00000000000000000000000000000000000000000000000007496cbb87cab44f 1HAX2n9Uruu9YDt4cqRgYcvtGvZj1rbUyt
0000000000000000000000000000000000000000000000000fc07a1825367bbe 1Kn5h2qpgw9mWE5jKpk8PP4qvvJ1QVy8su
jr. member
Activity: 115
Merit: 1
Hello does anyone have a complete list of the taken addresses and it's corresponding private keys? from 1-60? Thank you

It's a bit boring to get last 10, they are spread on 20 pages.

1757756a93
2237d05330
4b5f8303e9
e9ae4933d6
153869acc5b
2a21e3a7271
6bd3b27c591
e02b35a358f
122fca143c05
2ec18388d544
6cd610b53cba
ade6d7ce3b9b
174176b015f4d
22bd43c2e9354
75070a1a009d4
efae164cb9e3c
180788e47e326c
236fb6d5ad1f43
57dfa374c1d98f
9d18b63ac4ffdf
1eb25c90795d61c
2c675b852189a21
7496CBB87CAB44F

First 55 are in one message
member
Activity: 166
Merit: 16
Hello does anyone have a complete list of the taken addresses and it's corresponding private keys? from 1-60? Thank you

scroll back a bit and you can get most of them.. I think page 24? then move forward from there and you should have them all soon enough.. once you get used to skimming for the way they are posting the private keys you can do it in short order.
newbie
Activity: 2
Merit: 0
Hello does anyone have a complete list of the taken addresses and it's corresponding private keys? from 1-60? Thank you
member
Activity: 245
Merit: 17
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

.........................

.....................



Thanks.

One more thing, about -b -t -p  (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack   -d 1  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack   -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]



racminer - I know that multiplying the value of -b x2 does not affect the result, however I found (in my case) on other cards - a setting that is definitely better. And without hiding the fact that the -p indicator I have exactly the same as you (2560), check what result will be at the setting: -b 36 -t 512 -p 2560 ... if it does not move, reduce the -p value... and share the result... :-)


./clBitCrack -r -c -u -d 1 -b 36 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-28.13:53:24] [Info] Compression: both
Ellesmere        1216/6512MB | 2749473 targets 35.61 MKey/s (603,979,776 total) [00:00:15]


./clBitCrack -r -c -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-27.13:58:26] [Info] Compression: both
Ellesmere        2368/6471MB | 2749473 targets 46.55 MKey/s (1,659,358,937,088 total) [10:01:53]


member
Activity: 245
Merit: 17
1         target compressed      107 Mkey/s
2.7M   targets both                     46 Mkey/s

OK, not stubborn, but alternatively gifted.
Do you really think that 46 vs 107 is "won't change much"?

I think we agree, we just need to ask the same question Smiley

I said "won't change much" when: 
1) you compare  "1 compressed target" with  "2.7M compressed targets"                   107 and  83    23% decrease
2) you compare  "1 uncompressed target" with  "2.7M many uncompressed targets"  85  and  64    25% decrease
3) you compare  "1 both c & u   target" with  "2.7M  c & u  targets"                               65  and  46    30% decrease
 
more numbers

 you compare  "1 compressed target" with  "1M compressed targets"            107 and    90    16% decrease
 you compare  "1 compressed target" with  "100000 compressed targets"     107 and  100    7% decrease

Thanks Wink
jr. member
Activity: 115
Merit: 1
1       target compressed      107 Mkey/s
2.7M targets both                     46 Mkey/s

OK, not stubborn, but alternatively gifted.
Do you really think that 46 vs 107 is "won't change much"?
full member
Activity: 282
Merit: 114
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

Ok

We "stubborn boyz" have shown you numbers not expectations.

./clBitCrack  -c -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:58] [Info] Compression: compressed
Ellesmere        2304/6473MB | 1 target 107.29 MKey/s (1,321,205,760 total) [00:00:10]

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:00] [Info] Compression: uncompressed
Ellesmere        2304/6473MB | 1 target 85.06 MKey/s (1,283,457,024 total) [00:00:12]

 ./clBitCrack  -c -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:20:27] [Info] Compression: both
Ellesmere        2304/6485MB | 1 target 64.78 MKey/s (868,220,928 total) [00:00:11]


 ./clBitCrack -c -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.03:06:54] [Info] Compression: compressed
[2019-02-26.03:08:58] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6450MB | 2749473 targets 83.47 MKey/s (4,420,641,226,752 total) [14:41:53]^C

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-27.13:34:01] [Info] Compression: uncompressed
[2019-02-27.13:34:40] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6473MB | 2749473 targets 64.28 MKey/s (2,793,406,464 total) [00:00:39]

./clBitCrack -c -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.23:52:15] [Info] Compression: both
[2019-02-26.23:54:19] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6481MB | 2749473 targets 46.05 MKey/s (2,213,925,617,664 total) [13:21:11]



In Short: Ubuntu 16.04, Rx480 8Gb
1       target compressed      107 Mkey/s
1       target uncompressed   85  Mkey/s
1       target both                    65 Mkey/s

2.7M targets compressed        83 Mkey/s
2.7M targets uncompressed    64 MKey/s
2.7M targets both                     46 Mkey/s
 

Show us your  setting (OS, gpu type) and your numbers (Mkeys/s with 1 or many targets, with -c or -c -u)
otherwise, no need to comment.

Thanks.

One more thing, about -b -t -p  (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack   -d 1  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack   -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]



racminer - I know that multiplying the value of -b x2 does not affect the result, however I found (in my case) on other cards - a setting that is definitely better. And without hiding the fact that the -p indicator I have exactly the same as you (2560), check what result will be at the setting: -b 36 -t 512 -p 2560 ... if it does not move, reduce the -p value... and share the result... :-)
newbie
Activity: 37
Merit: 0
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

Ok

We "stubborn boyz" have shown you numbers not expectations.

./clBitCrack  -c -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:58] [Info] Compression: compressed
Ellesmere        2304/6473MB | 1 target 107.29 MKey/s (1,321,205,760 total) [00:00:10]

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:00] [Info] Compression: uncompressed
Ellesmere        2304/6473MB | 1 target 85.06 MKey/s (1,283,457,024 total) [00:00:12]

 ./clBitCrack  -c -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:20:27] [Info] Compression: both
Ellesmere        2304/6485MB | 1 target 64.78 MKey/s (868,220,928 total) [00:00:11]


 ./clBitCrack -c -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.03:06:54] [Info] Compression: compressed
[2019-02-26.03:08:58] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6450MB | 2749473 targets 83.47 MKey/s (4,420,641,226,752 total) [14:41:53]^C

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-27.13:34:01] [Info] Compression: uncompressed
[2019-02-27.13:34:40] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6473MB | 2749473 targets 64.28 MKey/s (2,793,406,464 total) [00:00:39]

./clBitCrack -c -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.23:52:15] [Info] Compression: both
[2019-02-26.23:54:19] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6481MB | 2749473 targets 46.05 MKey/s (2,213,925,617,664 total) [13:21:11]



In Short: Ubuntu 16.04, Rx480 8Gb
1       target compressed      107 Mkey/s
1       target uncompressed   85  Mkey/s
1       target both                    65 Mkey/s

2.7M targets compressed        83 Mkey/s
2.7M targets uncompressed    64 MKey/s
2.7M targets both                     46 Mkey/s
 

Show us your  setting (OS, gpu type) and your numbers (Mkeys/s with 1 or many targets, with -c or -c -u)
otherwise, no need to comment.

Thanks.

One more thing, about -b -t -p  (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack   -d 1  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack   -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]



Nice!!!  Grin
member
Activity: 245
Merit: 17
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".

Ok

We "stubborn boyz" have shown you numbers not expectations.

./clBitCrack  -c -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:58] [Info] Compression: compressed
Ellesmere        2304/6473MB | 1 target 107.29 MKey/s (1,321,205,760 total) [00:00:10]

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:22:00] [Info] Compression: uncompressed
Ellesmere        2304/6473MB | 1 target 85.06 MKey/s (1,283,457,024 total) [00:00:12]

 ./clBitCrack  -c -u -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
[2019-02-27.13:20:27] [Info] Compression: both
Ellesmere        2304/6485MB | 1 target 64.78 MKey/s (868,220,928 total) [00:00:11]


 ./clBitCrack -c -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.03:06:54] [Info] Compression: compressed
[2019-02-26.03:08:58] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6450MB | 2749473 targets 83.47 MKey/s (4,420,641,226,752 total) [14:41:53]^C

./clBitCrack  -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-27.13:34:01] [Info] Compression: uncompressed
[2019-02-27.13:34:40] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6473MB | 2749473 targets 64.28 MKey/s (2,793,406,464 total) [00:00:39]

./clBitCrack -c -u -d 1 -b 72 -t 256 -p 2048  -o res.txt -i btc.txt
[2019-02-26.23:52:15] [Info] Compression: both
[2019-02-26.23:54:19] [Info] 2,749,473 addresses loaded (52.4MB)
Ellesmere        2368/6481MB | 2749473 targets 46.05 MKey/s (2,213,925,617,664 total) [13:21:11]



In Short: Ubuntu 16.04, Rx480 8Gb
1       target compressed      107 Mkey/s
1       target uncompressed   85  Mkey/s
1       target both                    65 Mkey/s

2.7M targets compressed        83 Mkey/s
2.7M targets uncompressed    64 MKey/s
2.7M targets both                     46 Mkey/s
 

Show us your  setting (OS, gpu type) and your numbers (Mkeys/s with 1 or many targets, with -c or -c -u)
otherwise, no need to comment.

Thanks.

One more thing, about -b -t -p  (to Zielar)

Default setting:
~/BitCrack/bin$ ./clBitCrack   -d 1  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        16/6471MB | 1 target 48.35 MKey/s (1,997,537,280 total) [00:00:39]

My setting:
:~/BitCrack/bin$ ./clBitCrack   -d 1 -b 72 -t 256 -p 2048  15VF3MsCzjHmFQ3wK3SMrTEBTmFY8zhJnU
Ellesmere        2304/6491MB | 1 target 107.70 MKey/s (868,220,928 total) [00:00:06]

jr. member
Activity: 115
Merit: 1
You, stubborn boyz, don't get simple thing: bounty is 100% compressed, so you need only -c switch.
For abandoned wallets you 100% need both -u and -c switches.
That's 2x drop.

bloom filter with thousands of addressed also cannot be free. Here you get another ~50% drop.

So, 1 address vs thousands is really around "3X difference".
full member
Activity: 282
Merit: 114
Thank you for you very competent comments.

Welcome.

I claim that an Rx480 does 105MHkey/s on 01 target and 85 MHkey/s on 2,749,473 targets (compressed only)... draw you own conclusions. This is no BS.

1. Most abandoned wallets are uncompressed.
2. If speed with one address is almost the same as with 2.7M, then you haven't found right values for -b A -t B -p C
No other options.

I am not fully accept that... B is block's number. in many apps you can read CU value (compute units) which is -b the best value.
member
Activity: 245
Merit: 17
Thank you for you very competent comments.

Welcome.

I claim that an Rx480 does 105MHkey/s on 01 target and 85 MHkey/s on 2,749,473 targets (compressed only)... draw you own conclusions. This is no BS.

1. Most abandoned wallets are uncompressed.
2. If speed with one address is almost the same as with 2.7M, then you haven't found right values for -b A -t B -p C
No other options.
8Gb Rx480

-b 72 -t 256 -p 2048

Most abandoned wallets are uncompressed .. you are certainly right.



my rx480 4gb config:

-c  -b 72  -t 256 -p 2048   

5,000,000 addresses = 85Mkey/s

-c -u  -b 72  -t 256 -p 2048   

5,000,000 addresses = 42Mkey/s



Indeed, that's what I have.
holy_ship does not seem to agree. Smiley
newbie
Activity: 37
Merit: 0
Thank you for you very competent comments.

Welcome.

I claim that an Rx480 does 105MHkey/s on 01 target and 85 MHkey/s on 2,749,473 targets (compressed only)... draw you own conclusions. This is no BS.

1. Most abandoned wallets are uncompressed.
2. If speed with one address is almost the same as with 2.7M, then you haven't found right values for -b A -t B -p C
No other options.
8Gb Rx480

-b 72 -t 256 -p 2048

Most abandoned wallets are uncompressed .. you are certainly right.



my rx480 4gb config:

-c  -b 72  -t 256 -p 2048   

5,000,000 addresses = 85Mkey/s

-c -u  -b 72  -t 256 -p 2048   

5,000,000 addresses = 42Mkey/s

member
Activity: 245
Merit: 17
Thank you for you very competent comments.

Welcome.

I claim that an Rx480 does 105MHkey/s on 01 target and 85 MHkey/s on 2,749,473 targets (compressed only)... draw you own conclusions. This is no BS.

1. Most abandoned wallets are uncompressed.
2. If speed with one address is almost the same as with 2.7M, then you haven't found right values for -b A -t B -p C
No other options.
8Gb Rx480

-b 72 -t 256 -p 2048

Most abandoned wallets are uncompressed .. you are certainly right.

jr. member
Activity: 115
Merit: 1
Thank you for you very competent comments.

Welcome.

I claim that an Rx480 does 105MHkey/s on 01 target and 85 MHkey/s on 2,749,473 targets (compressed only)... draw you own conclusions. This is no BS.

1. Most abandoned wallets are uncompressed.
2. If speed with one address is almost the same as with 2.7M, then you haven't found right values for -b A -t B -p C
No other options.
jr. member
Activity: 34
Merit: 5
i have tested it with higher values too, need to of optimization
i created issues inside your pull of bitcrack and modified for random, check that too

Thank your for testing!
member
Activity: 330
Merit: 34
There are many posts lately.
It is a pity that none of them makes sense [luckily, at this time, regardless of it - I effectively scan 288000000000Mkey/s which may allow me and this time to win with all the conjectures and ideas that appear here]. Conclusions and questions are born in the same way ...
I'll start with the conclusions:
- torments of smallies donors are unnecessary with the idea that they will discover the public key and use 2step to get the private key ... This sum goes to the wallet and will not come back alone ... this will not result in the 33bit RAW PUBKEY that is necessary for the operation this method.
- I will not agree with the fact that the version of BitCracka presented with the "-r" option in any way contributes to speeding up or facilitating (reading, increasing the chance) to obtain a key. The same functionality is obtained using the --share x / x command in the original version, which only differs from the aforementioned version in the way of searching various ranges (which are still dependent on luck and strength used to search and in the same large scope). It scans at the same speed, so the chances do not increase at all with the use of this option as someone has previously written.
Now questions:
- Birthdayparadox: what are you striving for? what message does this mass of data show you ... a lot of general data that is based on ... nothing. Show these scripts you used to generate these reports / what they are based on?
- 2Step Giant: as part of curiosity in discovering the potential of this interesting feature I have recently delved into - I've found for training purposes three addresses from the TOP1000 largest BTC wallets, which have no more than five outgoing transactions and at the latest 5 years ago. I introduced RAWPUBKEYS to the Step 2 Giant script and using the possibility of using 1TB RAM I compiled the script to run on HASHTABLE (1ULL >> 33). To my surprise after two days when I looked to see what's going on in effect - I saw three private keys. My heart softened and I shivered. The amazement dropped when I converted the results to WIF and it turned out that the addresses for them were never used and have no transactions. My puzzle is that where did these keys come from if they do not belong to these 33bit RAWPUBKEYS? I started the script a second time and the result was identical.

And as for the next versions you plan to implement: instead of focusing on something that an application already has - implement something that actually makes it better than the original. For example, an example of what I would like to IMPROVE would be to show the time remaining until the end of scanning of a given interval (based on the scanning speed and knowledge which scope is scanned) - simple and better, because the original does not exist Smiley

2step gaint
i run under original script 1<<25
5 million used pubkeys
found 2 keys
when checked those 2 keys never used and never in my 5m pubkeys list
repeat run same identical keys
repeat with 1 <<26 , no result
i think something wrong inside script, i mention compelete script only filtered 2 pubkeys which output privkey but never used in my above posts


You are getting false positives which is normal with this version of the code and your big hashtable.
Read recent posts of arulbero in this thread to understand why.
Simplified said there are collisions in the hashtable.

Code:
typedef struct hashtable_entry {
    uint32_t x;
    uint32_t exponent;
} hashtable_entry;

Here uint32_t x; is to small too prevent collisions.
If you make it bigger you will also require more system memory. So you have to find a smart way or just verify each found match if it is a true positive.

i have tested it with higher values too, need to of optimization
i created issues inside your pull of bitcrack and modified for random, check that too
jr. member
Activity: 34
Merit: 5
There are many posts lately.
It is a pity that none of them makes sense [luckily, at this time, regardless of it - I effectively scan 288000000000Mkey/s which may allow me and this time to win with all the conjectures and ideas that appear here]. Conclusions and questions are born in the same way ...
I'll start with the conclusions:
- torments of smallies donors are unnecessary with the idea that they will discover the public key and use 2step to get the private key ... This sum goes to the wallet and will not come back alone ... this will not result in the 33bit RAW PUBKEY that is necessary for the operation this method.
- I will not agree with the fact that the version of BitCracka presented with the "-r" option in any way contributes to speeding up or facilitating (reading, increasing the chance) to obtain a key. The same functionality is obtained using the --share x / x command in the original version, which only differs from the aforementioned version in the way of searching various ranges (which are still dependent on luck and strength used to search and in the same large scope). It scans at the same speed, so the chances do not increase at all with the use of this option as someone has previously written.
Now questions:
- Birthdayparadox: what are you striving for? what message does this mass of data show you ... a lot of general data that is based on ... nothing. Show these scripts you used to generate these reports / what they are based on?
- 2Step Giant: as part of curiosity in discovering the potential of this interesting feature I have recently delved into - I've found for training purposes three addresses from the TOP1000 largest BTC wallets, which have no more than five outgoing transactions and at the latest 5 years ago. I introduced RAWPUBKEYS to the Step 2 Giant script and using the possibility of using 1TB RAM I compiled the script to run on HASHTABLE (1ULL >> 33). To my surprise after two days when I looked to see what's going on in effect - I saw three private keys. My heart softened and I shivered. The amazement dropped when I converted the results to WIF and it turned out that the addresses for them were never used and have no transactions. My puzzle is that where did these keys come from if they do not belong to these 33bit RAWPUBKEYS? I started the script a second time and the result was identical.

And as for the next versions you plan to implement: instead of focusing on something that an application already has - implement something that actually makes it better than the original. For example, an example of what I would like to IMPROVE would be to show the time remaining until the end of scanning of a given interval (based on the scanning speed and knowledge which scope is scanned) - simple and better, because the original does not exist Smiley

2step gaint
i run under original script 1<<25
5 million used pubkeys
found 2 keys
when checked those 2 keys never used and never in my 5m pubkeys list
repeat run same identical keys
repeat with 1 <<26 , no result
i think something wrong inside script, i mention compelete script only filtered 2 pubkeys which output privkey but never used in my above posts


You are getting false positives which is normal with this version of the code and your big hashtable.
Read recent posts of arulbero in this thread to understand why.
Simplified said there are collisions in the hashtable.

Code:
typedef struct hashtable_entry {
    uint32_t x;
    uint32_t exponent;
} hashtable_entry;

Here uint32_t x; is to small too prevent collisions.
If you make it bigger you will also require more system memory. So you have to find a smart way or just verify each found match if it is a true positive.
Jump to: