Pages:
Author

Topic: BitCrack - A tool for brute-forcing private keys - page 5. (Read 77647 times)

newbie
Activity: 11
Merit: 0
Hey people!
I'm using BitCrack/AltCrack to find 66, but it only searches consecutively through 1 or some other number. Tell me if there is a program that can search for 66 puzzles by sorting through all the range options by mask.

for example this mask (decimal): XXXXXX123456XXXXXXXX

Now I have to run Altcrack 368,935 times consecutively to check the range for this mask, but this is very long. Is there any other way?
newbie
Activity: 11
Merit: 0
tell me, is it possible to use bitcrack for Ethereum? Huh

you need AltCrack
legendary
Activity: 2646
Merit: 6681
Self-proclaimed Genius
tell me, is it possible to use bitcrack for Ethereum? Huh
No.
It's mainly developed for the puzzle transaction which is Bitcoin-exclusive.
Example:
Code:
clbitcrack 0x0123
Result:
Code:
[Error] Invalid address '0x0123'

What's your goal anyways, depending on it, I may know an alternative that'll work in Ethereum.
newbie
Activity: 7
Merit: 5
tell me, is it possible to use bitcrack for Ethereum? Huh
jr. member
Activity: 115
Merit: 1
who solved ? which tools useing to crack keyhunt or BitCrack

Very unlikely that it was bitcrack. This magic kangaroo stuff is.

I wonder of RAM requirements for 120 puzzle. Who's next p66 or p125? )
newbie
Activity: 12
Merit: 0
Needs too much effort more then guessing 256 bit key  Cry Cry
[/quote]

I read your posts on the forum.  If you take the last digits of any private key and go through the entire range, you will find the key
check this
-b 64 -t 512 -p 1600 --keyspace 7FFFFFFFFF9112D4:FFFFFFFFFFFFFFFF 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN --stride 1000000
-b 64 -t 512 -p 1600 --keyspace FFFFFFFFF5B26867:1FFFFFFFFFFFFFFFF 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe  --stride 10000000
zahid888 i think you are on the right track
you for 66 you need to find 7 digitsneed to look in the starting range 0-9  A-F = full brute force 16^7

I don't know how to speed it up



[2023-06-19.21:22:02] [Info] Compression : compressed
[2023-06-19.21:22:02] [Info] Starting at : 000000000000000000000000000000000000000000000001FFFFFFFFF0000A18 (65 bit)
[2023-06-19.21:22:02] [Info] Ending at   : 000000000000000000000000000000000000000000000003FFFFFFFFFFFFFFFF (66 bit)
[2023-06-19.21:22:02] [Info] Range       : 000000000000000000000000000000000000000000000002000000000FFFF5E7 (66 bit)
[2023-06-19.21:22:02] [Info] Initializing NVIDIA GeForce RTX 3080
[2023-06-19.21:22:02] [Info] Generating 52,428,800 starting points (2000.0MB)
[2023-06-19.21:22:05] [Info] 10.0%  20.0%  30.0%  40.0%  50.0%  60.0%  70.0%  80.0%  90.0%  100.0%
[2023-06-19.21:22:07] [Info] Done
[DEV: NVIDIA GeForce R 9156/10239MB] [0000000000000000000000000000000000000000000000036A7FFFFFF0000A18 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 1663.50 MKey/s] [TOTAL: 6,081,740,800] [00:00:01][2023-06-19.21:22:12] [Info] Reached end of keyspace


[2023-06-19.21:22:13] [Info] Compression : compressed
[2023-06-19.21:22:13] [Info] Starting at : 000000000000000000000000000000000000000000000001FFFFFFFFF0000A19 (65 bit)
[2023-06-19.21:22:13] [Info] Ending at   : 000000000000000000000000000000000000000000000003FFFFFFFFFFFFFFFF (66 bit)
[2023-06-19.21:22:13] [Info] Range       : 000000000000000000000000000000000000000000000002000000000FFFF5E6 (66 bit)
[2023-06-19.21:22:13] [Info] Initializing NVIDIA GeForce RTX 3080
[2023-06-19.21:22:13] [Info] Generating 52,428,800 starting points (2000.0MB)
[2023-06-19.21:22:16] [Info] 10.0%  20.0%  30.0%  40.0%  50.0%  60.0%  70.0%  80.0%  90.0%  100.0%
[2023-06-19.21:22:18] [Info] Done
[DEV: NVIDIA GeForce R 9156/10239MB] [00000000000000000000000000000000000000000000000370BFFFFFF0000A19 (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 1691.25 MKey/s] [TOTAL: 6,186,598,400] [00:00:01][2023-06-19.21:22:23] [Info] Reached end of keyspace


[2023-06-19.21:22:23] [Info] Compression : compressed
[2023-06-19.21:22:23] [Info] Starting at : 000000000000000000000000000000000000000000000001FFFFFFFFF0000A1A (65 bit)
[2023-06-19.21:22:23] [Info] Ending at   : 000000000000000000000000000000000000000000000003FFFFFFFFFFFFFFFF (66 bit)
[2023-06-19.21:22:23] [Info] Range       : 000000000000000000000000000000000000000000000002000000000FFFF5E5 (66 bit)
[2023-06-19.21:22:23] [Info] Initializing NVIDIA GeForce RTX 3080
[2023-06-19.21:22:24] [Info] Generating 52,428,800 starting points (2000.0MB)
[2023-06-19.21:22:27] [Info] 10.0%  20.0%  30.0%  40.0%  50.0%  60.0%  70.0%  80.0%  90.0%  100.0%
[2023-06-19.21:22:29] [Info] Done
[DEV: NVIDIA GeForce R 9156/10239MB] [0000000000000000000000000000000000000000000000036D9FFFFFF0000A1A (66 bit)] [INC: 0, 0] [TARGET: 1] [SPEED: 1663.50 MKey/s] [TOTAL: 6,134,169,600] [00:00:01][2023-06-19.21:22:34] [Info] Reached end of keyspace
hero member
Activity: 630
Merit: 731
Bitcoin g33k
My data in my sheet in github did however reveal an interesting pattern. The decimals of all the private keys of every puzzle are within 12% to 49% of the base decimal (range)
how do you come up with this false claim? please show us the decimal value of the relative position for puzzles 38 and 60 as an example. And then... Well, what do you find ?
copper member
Activity: 1330
Merit: 900
🖤😏
I never thought bitcoin/blockchain technology will see a day where people are making efforts to brute force the only technology that we need to keep the way it is or just improve on the sides of network adoption, feasibility in terms of fees, p2p and KYC free adoption. This should be the development we need to have right now and not the other way around.

I see some negative implications of this idea. Irrespective of what others think I don’t like the idea of having brute force technology. It would be obvious that soon others will copy it and start misusing the same for their own benefit. Not sure if this is only for one time use but it’s bad idea.

By just reading it I’m frightened about my wallet security. Lolz.
First off, Doing this publicly will warn everyone about possible vulnerabilities and weaknesses, demonstrating to the world how we can find the keys of low range and exposed public keys will send the signal to everyone that they need to use standard and secure wallets to generate keys with high entropy and also never use an address more than once.

On the other hand, there are hundreds of thousands of bitcoins on exposed keys for years, nobody has managed to touch them.
If you want to be 100% assured of the safety of your coins, just store them on an address and when you are spending, don't use the same address as the return address, done and safe for a few billion years.😉
newbie
Activity: 1
Merit: 0
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys.

.....

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

....

Thoughts?


Thanks!

what I am going to say is purely theoretical, as I have never tried to brute force private keys.

I don´t think you will have any success doing this.
If you have enough hash power, you would probably make more money working as an honest node, mining.

Bitcoin protocol is secure enough. If it were brute force-able, bitcoin wouldn't be worth anything.

What i think you could do is to find a collision. If someone made an insecure private key, by just hashing some passphrase... maybe you could have some luck. I tried to do this once, but never found anything. I tried those terms like "wallet" "bitcoin". I found some addresses which used to have balances, but not anymore. But I was doing manually, like 1 address/3 minutes lol

If you could somehow at the same time check if any of those 9.4 million keys/sec have any balance in btc/bch/btg etc...

But I don't think any of that will work, and will be a waste of time and resources.
full member
Activity: 1092
Merit: 227
I never thought bitcoin/blockchain technology will see a day where people are making efforts to brute force the only technology that we need to keep the way it is or just improve on the sides of network adoption, feasibility in terms of fees, p2p and KYC free adoption. This should be the development we need to have right now and not the other way around.

I see some negative implications of this idea. Irrespective of what others think I don’t like the idea of having brute force technology. It would be obvious that soon others will copy it and start misusing the same for their own benefit. Not sure if this is only for one time use but it’s bad idea.

By just reading it I’m frightened about my wallet security. Lolz.
copper member
Activity: 1330
Merit: 900
🖤😏
It is important to note that brute-forcing Bitcoin private keys is not a legal activity and is also not ethical. The tool you have created can be used for illegal activities such as stealing funds from individuals or organizations, and it can also be used for unethical purposes such as compromising the security and privacy of individuals. Therefore, it is important to use your skills and knowledge for ethical and legal purposes only.
It's time to leave the basement and join the outside world, bitcoin is an open source technology using a publicly accessible elliptic curve, whole point of using EC is due to the difficulty of finding randomly generated big private keys.

However to demonstrate how difficult it actually is, allegedly @Satoshi himself organized a series of puzzles placing bitcoins in extremely easy bit ranges and after some times some people figured it out and started  to post     topics about the subject, it was originally around 32 bitcoins, then it was increased to 100, and  2 weeks ago he added around 900 more bitcoins totalling around 1000 BTC as a prize for solvers. It has been done with consent and is totally legal.

Do also note that brute forcing any large private key will take billions of years, and brute forcing a small key in a very very small range will take decades with many high end GPUs.

Further more, all the available "cracking" tools are inefficient as they are just not enough to pose any threat.

Ps, around these woods we operate by bit and x,y, we are alien to terms such as ethics. Lol.😉
newbie
Activity: 2
Merit: 0

Were you in a cave for the last couple of years? I mean my old laptop with a low end GPU can eat 30MK/s, now you want us to chew 17 Mk in a day? Wasn't it enough that with trillions of keys per second we'd still be years from finding 66, now we have to keep searching till the sun dies off into darkness.🤣

Keep at it though, every person is an asset ( to share our desperation and despair). Sigh. Lol

Buddy this is a cpu only script at the moment and building on it, as Bitcrack is not working on any improvement. Yeah it does 16 Mil per thread, at 8 thread rig it should do 128 Mil per day, my server does about 512 Mil per process, but only run 1 at time as I need server to do allot of other stuff to.
Running 5 X processes of above that peaks by cpu at 80% gives me 128 x 5 Mil per day

If you think you can optimize the code to check faster, then try.

And will update the code to use GPU and CPU hopefully soon, just ironing some cuda bugs.
I did tests with bitcrack where I gave it 1 Bil keys to check with a correct one in these large ranges. It missed to match it, thinking due to same bug i'm having with cudo cores splitting the decimal processing when working with these large decimals.

With what 800 quad quadrillions possibilities your talking 100 of thousands of years, that is if you check from bottom to top, randomly is another ball game, as random numbers can repeat, but at least you have a fat chance in hell as who has a few millions years to check from top to bottom?

My data in my sheet in github did however reveal an interesting pattern. The decimals of all the private keys of every puzzle are within 12% to 49% of the base decimal (range)
So if the pattern repeats with next puzzles you can only check this above decimal ranges

I have a script currently doing that, just get the decimal of the private key :
current_decimal = int.from_bytes(bytes.fromhex(key.private_hex), 'big')
Check if is in range 12 - 49%, if not, no need to waste processing and checking it against public key
this however just gives me a 11 500 X 1.2 boost per thread per second

When I get the gpu part working I will also work on a reversed engineered sha256 function, we know the public key is generated by the private key, and we know the public key. So maybe we can find a formula to exclude a large list of the private keys to check that will never resolve to certain characters in the public key

Lastly I was thinking of doing a database of checked keys to, but to check database will slow it down, but if multiple rigs update it, might lead to someone finding it faster. Seems bit unfair as only someone will get the spoils even if it is a team effort and concerned that this will lead to poeple raping my server that hosts the what 80 gig database in the end

Also in my sheet I was hoping their is a pattern in the decimal multiplier from one puzzle to the next :

y = base high / decimal
x > y
z = x - y
x = z + y
x = x

So if they had a method to determine the next puzzle, a solution could be to find the x multiplier, but so far, I've not been able to find it
copper member
Activity: 1330
Merit: 900
🖤😏

Were you in a cave for the last couple of years? I mean my old laptop with a low end GPU can eat 30MK/s, now you want us to chew 17 Mk in a day? Wasn't it enough that with trillions of keys per second we'd still be years from finding 66, now we have to keep searching till the sun dies off into darkness.🤣

Keep at it though, every person is an asset ( to share our desperation and despair). Sigh. Lol
newbie
Activity: 2
Merit: 0
I wonder if keys were generated by some deterministic wallet first, and then truncated to N bits. Because in that case, it could be possible to recover the master key, and then sweep coins from all of them, while it would not mean that ECDSA is broken (because HD keys could be non-hardened).

Interesting puzzle, I checked for patterns between binary values, decimal values, floor values. Just cant find anything

I updated an excel sheet puzzle bitcoin.xlsx with allot more data of each puzzle. Like decimal, binary, floor, and allot more data per puzzle. Even multipliers of the data to the next puzzle.

Since this range is just so huge, I think a random generator would maybe work best to try and find the needle.

I attached below my python script trying the next puzzle randomly if someone might benefit to

https://github.com/negate7o4/Bitcoin-Puzzle

On my rig, I7 if I run 5 X instances, it checks about 11 500 possibilities per second per thread, but eats 80% cpu. So the code chews threw 16.5 Mil random possibilities per day

If you want to try a different puzzle, just change these values in the script :

address = '1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF'

start_key = '0000000000000000000000000000000000000000000000040000000000000000' stop_key = '000000000000000000000000000000000000000000000007ffffffffffffffff'

Also take note of the cpu threads the code uses, update according to your threads.

Their is also a text file in my repository of the correct pip's you need to install for the code to work
member
Activity: 73
Merit: 19
copper member
Activity: 1330
Merit: 900
🖤😏
Still it’s fascinating to play around and see what others use as approaches. This only shows how good Bitcoin really is and I’m shure if satoshi is still around this would be one of the threads he would read with interest to see how Bitcoin performs  Cheesy
Well, the vulnerabilities already exist, we don't know about them yet, this puzzle needs to go on for ever, and it should remain filled with hundreds of bitcoins, just imagine if someone had access to a backdoor or some sort, they could at least take the puzzle prizes because it wouldn't be theft, but if there is no puzzle prize, the exploiter could be tempted to go after people's coins.😉
hero member
Activity: 1064
Merit: 645
Magic
Still it’s fascinating to play around and see what others use as approaches. This only shows how good Bitcoin really is and I’m shure if satoshi is still around this would be one of the threads he would read with interest to see how Bitcoin performs  Cheesy
newbie
Activity: 72
Merit: 0
this is senseless
member
Activity: 282
Merit: 20
the right steps towerds the goal
what about puzzle 66?  Undecided

For 66 I have been trying something like this.

 
================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : sadness behind zone combine purse sentence bench symbol rookie bag attract govern
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000003e9542b9b08d3383b
Addrs : 13z7L2eYpaMRNEBmmT2EshBbxHUABDNccx
Range : 3e9542b9000000000:3e9542b9fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=3E9542B9000000000
Keyspace   end=3E9542B9FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:43:46 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1118.441 MK/s (GPU 1118.441 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 16:45:01 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : deliver cute current mean dutch cloud city defy system exercise glide wet
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000002b2d4e487b051ce63
Addrs : 13zb56FGSawmd1MuSsKJNrTWgNnRZwt6sz
Range : 2b2d4e48000000000:2b2d4e48fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=2B2D4E48000000000
Keyspace   end=2B2D4E48FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:47:34 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1119.082 MK/s (GPU 1119.082 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 16:48:49 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : summer very sausage trust brown post immune advice valley opera little charge
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000003598a8ee012faf870
Addrs : 13zbbSg7nRLSpyCNpJ3WZD1J9M6PUtvfC6
Range : 3598a8ee000000000:3598a8eefffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=3598A8EE000000000
Keyspace   end=3598A8EEFFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:50:04 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1108.211 MK/s (GPU 1108.211 MK/s) (2^36.24) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 16:51:19 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : fatigue suggest claw strike give test use indoor hold romance coral insane
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 00000000000000000000000000000000000000000000000217a4dd28cf107aa2
Addrs : 13zPcX7WPcLCYSaavTwg2ntBGH8pVHb76Z
Range : 217a4dd2000000000:217a4dd2fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=217A4DD2000000000
Keyspace   end=217A4DD2FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:52:35 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1097.404 MK/s (GPU 1097.404 MK/s) (2^36.24) [00:01:13 Elapsed Time][1]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 16:53:50 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : stuff kiss clog easy present fancy scrub climb link input rural globe
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 0000000000000000000000000000000000000000000000024c4a7d632c865b7b
Addrs : 13zYHtjJYESDvXXnXtymtDxFqB5tYxjJqt
Range : 24c4a7d6000000000:24c4a7d6fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=24C4A7D6000000000
Keyspace   end=24C4A7D6FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:56:35 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1108.418 MK/s (GPU 1108.418 MK/s) (2^36.25) [00:01:13 Elapsed Time][1]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 16:57:50 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : inquiry suit dentist detail gap pumpkin income dwarf express figure person enter
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000003159cfd7dde56dbc9
Addrs : 13zTojop1dzyxufJL5mkuWYCAiunW37vKN
Range : 3159cfd7000000000:3159cfd7fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=3159CFD7000000000
Keyspace   end=3159CFD7FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 16:59:37 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1109.837 MK/s (GPU 1109.837 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:00:52 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : anxiety raccoon clarify mule immense left wing any race today copy home
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 0000000000000000000000000000000000000000000000021eaaae7cea5af2f2
Addrs : 13z5MJcCTKHwVzC6C2hbXNMyAwGXMceYd7
Range : 21eaaae7000000000:21eaaae7fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=21EAAAE7000000000
Keyspace   end=21EAAAE7FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 17:02:11 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1112.090 MK/s (GPU 1112.090 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:03:26 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : scout boring super zebra swamp dance maze caution popular wait dance drive
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 00000000000000000000000000000000000000000000000232b86039f7aedbd8
Addrs : 13zwx4VKzyRUmQEjecnHxso88RVa34RJFC
Range : 232b8603000000000:232b8603fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=232B8603000000000
Keyspace   end=232B8603FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 17:05:01 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1106.019 MK/s (GPU 1106.019 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:06:16 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : reveal muffin accident harbor disagree maple enter spice divert stock when suit
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000002c5c95f84b0f9520c
Addrs : 13zsB9pM1WXH2FdnVhpoyJkiMsaDpL5WgT
Range : 2c5c95f8000000000:2c5c95f8fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=2C5C95F8000000000
Keyspace   end=2C5C95F8FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 17:07:37 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1109.461 MK/s (GPU 1109.461 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:08:51 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : sibling fence brave mirror picnic only harvest remember make torch protect daughter
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000002a641ddfe686bb93f
Addrs : 13znKyww6sn8NhxibmPvfzqueLPLoEk9hi
Range : 2a641ddf000000000:2a641ddffffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=2A641DDF000000000
Keyspace   end=2A641DDFFFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 17:13:31 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1118.169 MK/s (GPU 1118.169 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:14:46 2023

 ================================ Deterministic wallet masked with leading Zeros ==================================


Bip44 : paper ask blind spoon flat length arch bird upgrade certain abstract thank
Msk66 : 0000000000000000000000000000000000000000000000020000000000000000
Pkv66 : 000000000000000000000000000000000000000000000002264864827ec5d907
Addrs : 13zsck36JGo8jFPcHDqTZwK7AAgsJXMtgw
Range : 22648648000000000:22648648fffffffff
Prefx : 13zb1hQbW

VanBitCrackenS v1.0
Keyspace start=22648648000000000
Keyspace   end=22648648FFFFFFFFF
Search: 15 prefixes (Lookup size 15) [Compressed]
Started at Sun Mar 12 17:16:33 2023
CPU threads used: 0
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x128 cores) Grid(304x512)
1111.710 MK/s (GPU 1111.710 MK/s) (2^36.25) [00:01:13 Elapsed Time][0]
[EXIT] Reached end of keyspace.

Finish at Sun Mar 12 17:17:48 2023
Pages:
Jump to: