VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards) - page 7.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote from: digaran on January 15, 2023, 01:18:29 PM

Hi there dear dev, just wanted to say I'm also a *dev, so dev to dev can you help here, I'm not a win dev so don't know much about these. What's wrong with this code?
I used bold inside the quote to show that I know things, I know zero.🤣

Quote

C:\Users\Desktop\VanBit>VanBitCrackenS1.1_2 -t 0 -gpu -g 256 -gpuId 0 -r 100000 -check --keyspace 337d48f41c4bb8886:35071626a0b64d0ce --continue continue.txt -o outputfile.txt -v -b -l nosse -kp -rp privkey partialkeyfile 13zb1hQbWVsc2S7ZTZn pause
GetBase10() Results OK
Add() Results OK : 237.530 MegaAdd/sec
Mult() Results OK : 25.947 MegaMult/sec
Div() Results OK : 3.102 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 186.301 KiloInv/sec
IntGroup.ModInv() Results OK : 5.751 MegaInv/sec
ModMulK1() Results OK : 7.511 MegaMult/sec
ModSquareK1() Results OK : 6.821 MegaMult/sec
ModMulK1order() Results OK :3.525 MegaMult/sec

GPU: GPU #0 NVIDIA GeForce 920MX (2x128 cores) Grid(256x512)
GPUEngine: Launch: the launch timed out and was terminated
37.275 MegaKey/sec
(thread=3, incr=743, endo=0)
C:\Users\Desktop\VanBit>bitcrackens1.1_2.bat

C:\Users\Desktop\VanBit>VanBitCrackenS1.1_2 -t 0 -gpu -g 512 -gpuId 0 -r 100000 -check --keyspace 337d48f41c4bb8886:35071626a0b64d0ce --continue continue.txt -o outputfile.txt -v -b -l nosse -kp -rp privkey partialkeyfile 13zb1hQbWVsc2S7ZTZn pause
GetBase10() Results OK
Add() Results OK : 303.951 MegaAdd/sec
Mult() Results OK : 22.351 MegaMult/sec
Div() Results OK : 2.602 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 188.328 KiloInv/sec
IntGroup.ModInv() Results OK :5.753 MegaInv/sec
ModMulK1() Results OK :7.510 MegaMult/sec
ModSquareK1() Results OK : 7.824 MegaMult/sec
ModMulK1order() Results OK :3.829 MegaMult/sec

GPU: GPU #0 NVIDIA GeForce 920MX (2x128 cores) Grid(512x512)
Seed:
GPUEngine: Launch: the launch timed out and was terminated
83.871 MegaKey/sec
Add() Results OK : 303.030 MegaAdd/sec
Grid(1024x512)
167.744 MegaKey/sec
(thread=17, incr=876, endo=0)
Add() Results OK : 264.550 MegaAdd/sec
Adress : 18******TkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1*******KNngkdXEeobR76b53LETtpyT OK!Grid(2048x512)
206.455 MegaKey/sec
(thread=31, incr=518, endo=0)

*=fake dev. lol

Edit= on random version, is there any way to search for other addresses? And when I reset, does it have to repeat all over, and is it possible to hit duplicates? Meaning searching a range twice.

With the VBC R, Random version; what do you mean search for other addresses? You can search multiple addresses with an input file; such as addresses.txt file.
The only way it repeats, is if you are searching in a small range; 44 bit and below may get multiple duplicate hits.

digaran

copper member

Activity: 1330

Merit: 899

🖤😏

Hi there dear dev, just wanted to say I'm also a *dev, so dev to dev can you help here, I'm not a win dev so don't know much about these. What's wrong with this code?
I used bold inside the quote to show that I know things, I know zero.🤣

Quote

C:\Users\Desktop\VanBit>VanBitCrackenS1.1_2 -t 0 -gpu -g 256 -gpuId 0 -r 100000 -check --keyspace 337d48f41c4bb8886:35071626a0b64d0ce --continue continue.txt -o outputfile.txt -v -b -l nosse -kp -rp privkey partialkeyfile 13zb1hQbWVsc2S7ZTZn pause
GetBase10() Results OK
Add() Results OK : 237.530 MegaAdd/sec
Mult() Results OK : 25.947 MegaMult/sec
Div() Results OK : 3.102 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 186.301 KiloInv/sec
IntGroup.ModInv() Results OK : 5.751 MegaInv/sec
ModMulK1() Results OK : 7.511 MegaMult/sec
ModSquareK1() Results OK : 6.821 MegaMult/sec
ModMulK1order() Results OK :3.525 MegaMult/sec

GPU: GPU #0 NVIDIA GeForce 920MX (2x128 cores) Grid(256x512)
GPUEngine: Launch: the launch timed out and was terminated
37.275 MegaKey/sec
(thread=3, incr=743, endo=0)
C:\Users\Desktop\VanBit>bitcrackens1.1_2.bat

C:\Users\Desktop\VanBit>VanBitCrackenS1.1_2 -t 0 -gpu -g 512 -gpuId 0 -r 100000 -check --keyspace 337d48f41c4bb8886:35071626a0b64d0ce --continue continue.txt -o outputfile.txt -v -b -l nosse -kp -rp privkey partialkeyfile 13zb1hQbWVsc2S7ZTZn pause
GetBase10() Results OK
Add() Results OK : 303.951 MegaAdd/sec
Mult() Results OK : 22.351 MegaMult/sec
Div() Results OK : 2.602 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 188.328 KiloInv/sec
IntGroup.ModInv() Results OK :5.753 MegaInv/sec
ModMulK1() Results OK :7.510 MegaMult/sec
ModSquareK1() Results OK : 7.824 MegaMult/sec
ModMulK1order() Results OK :3.829 MegaMult/sec

GPU: GPU #0 NVIDIA GeForce 920MX (2x128 cores) Grid(512x512)
Seed:
GPUEngine: Launch: the launch timed out and was terminated
83.871 MegaKey/sec
Add() Results OK : 303.030 MegaAdd/sec
Grid(1024x512)
167.744 MegaKey/sec
(thread=17, incr=876, endo=0)
Add() Results OK : 264.550 MegaAdd/sec
Adress : 18******TkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1*******KNngkdXEeobR76b53LETtpyT OK!Grid(2048x512)
206.455 MegaKey/sec
(thread=31, incr=518, endo=0)

*=fake dev. lol

Edit= on random version, is there any way to search for other addresses? And when I reset, does it have to repeat all over, and is it possible to hit duplicates? Meaning searching a range twice.

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Quote from: WanderingPhilospher on January 10, 2023, 10:03:16 AM

Quote

Do you know any script or program that will check the list of private keys? balance?

If you mean check addresses with balance, there is a python script floating around somewhere and LoyceV has a list that he updates daily with all BTC addresses and balances.

Have you ever thought of building a Mac version of this? Those Apple Silicon processors have beefy GPUs inside and are worth a shot.

It will also give us a chance to see just how powerful the iPhone/Pad chips are as well (compared to some not-so-old desktop GPUs widely used for cracking puzzles).

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote

Do you know any script or program that will check the list of private keys? balance?

If you mean check addresses with balance, there is a python script floating around somewhere and LoyceV has a list that he updates daily with all BTC addresses and balances.

opeael2

newbie

Activity: 10

Merit: 2

Quote from: WanderingPhilospher on August 28, 2021, 12:36:43 PM

Here is VBCRandom in action.
Batch file settings:

Code:

VBCRandom -t 0 -gpu -gpuId 0 -topr 8000000000000000 -subr 48 -r 480 --keyspace 8000000000000000:FFFFFFFFFFFFFFFF -o randomtest.txt 16jY7q

Results:

Code:

Started Sat Aug 28 12:32:28 2021
Start Range  :  8000000000000000
End   Range  :  FFFFFFFFFFFFFFFF
Searching For:  16jY7q
Compression  :  Compressed
CPU threads  :  0
GPU          :  GPU #0 NVIDIA GeForce GTX 1060 6GB (10x128 cores) Grid(80x512)

Random Key   :  800007AC8B3D5525
Random Key   :  8000201C33F5235B
Random Key   :  8000E2F090E63C7D
 [00:00:04 Run Time ] [Speed 82.524 MK/s] [Total Keys: 335,544,320] [# Rekeys: 0] [Found: 2]
Random Key   :  8000208FB1B474F6
Random Key   :  8000B9FC61E9ABA1
Random Key   :  8000F0310FBE3DD2
 [00:00:08 Run Time ] [Speed 82.563 MK/s] [Total Keys: 671,088,640] [# Rekeys: 1] [Found: 4]
Random Key   :  80004698D58E9E8F
Random Key   :  800089612D96CDA0
Random Key   :  8000C2190CD91261
 [00:00:15 Run Time ] [Speed 81.609 MK/s] [Total Keys: 1,258,291,200] [# Rekeys: 2] [Found: 6]
Random Key   :  800043E67DBAB51D
Random Key   :  800098B29829B7A7
Random Key   :  800045B53E8E1753
 [00:00:20 Run Time ] [Speed 79.286 MK/s] [Total Keys: 1,593,835,520] [# Rekeys: 2] [Found: 6]

Key results:

Code:

Pub Addr: 16jY7qzxujzi1K7GaEc17ZFokFymagY3jG
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLz94bU7Lw952JxZUX
Priv (HEX): 0x000000000000000000000000000000000000000000000000800015BE8DF950C5

Pub Addr: 16jY7qdry8xB4v6JeMH2R3ViVTSTzDGv2B
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzUZ1qwKHqCmVgPRj
Priv (HEX): 0x000000000000000000000000000000000000000000000000800064574E06912E

Pub Addr: 16jY7qwSUyCss5jZYDjgJofLe7KgKxiCQo
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzGCmCHBUm9fupLgz
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000328A78D70051

Pub Addr: 16jY7q7x9EjwysPAYtappeDX6Lqtm32ekf
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzCiYnMdjWKzRsXUn
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000247B3183BFDC

Pub Addr: 16jY7qTWTgUzCEEH7E9UFxVKALnvCcykwV
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLziDMQ1SzkL55t52w
Priv (HEX): 0x00000000000000000000000000000000000000000000000080009B6E64AE0CAD

Pub Addr: 16jY7qwSwoyaH2NT2dKsY15h11Gma5bccb
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzSjUdaY9XWkAo8pE
Priv (HEX): 0x00000000000000000000000000000000000000000000000080005D00CB38A1B5

Pub Addr: 16jY7qCNptT19yStBa3tgVFy2k7CvhLi8t
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvM13ZD8mLPHJMsj9c6
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000E96EBB6FFC70

Pub Addr: 16jY7q3WZumGZ4gbrDTSte9JTbhEniZpqP
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzLQVfZGJ81tzYnbi
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000437CBF9A4063

Pub Addr: 16jY7qSaxGdCNribBnf6oxcpaw7aBUA6nN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzMkoUUXmUpiqDSm1
Priv (HEX): 0x000000000000000000000000000000000000000000000000800048EE90360155

Pub Addr: 16jY7qSV4qyaXJNmwWCu2t4DRWHuTnQuwz
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLz9toCoHuQiZuBD2p
Priv (HEX): 0x000000000000000000000000000000000000000000000000800019188671357A

Pub Addr: 16jY7qJ3MdatyubzBQ4e67n5D2iJRqFrDY
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzZLFmMZj3v26fWhh
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000779DFF73D53B

See how every new random key is within the same 48 bit range? Now you could change the -topr to whatever toprange and the -subr to whatever subrange. If in the example above you wanted to search every possible range in the toprange of 8000000000000000, you would use -topr 8000000000000000 and -subr 60.

Make sense?

use the -b for compressed and uncompressed.

Do you know any script or program that will check the list of private keys? balance?

Evillo

member

Activity: 185

Merit: 15

Two things you should never abandon: Family & BTC

Tested this today and I just wanna thank WanderingPhilosopher for such a beautiful software .. this by all means is the best way to search within a puzzle's range .. and as a tweak of both bitcrack and vanitysearch, it has beaten both of them.. faster than all I've tried before .. also very easy to use and was the best randomization option to finally land on .. great job

Trancefan

newbie

Activity: 19

Merit: 2

I just dont fucking understand. You created the damn program. Why didn't and haven't you upload the source code? It is common knowledge that when you upload a program to github, you also upload the source code as well.

stanner.austin

member

Activity: 69

Merit: 53

@madmartyk
Hello
Its very easy if you found hex or int just convert to compressed key
You can find sample posted by me, you can even display key and import to any wallet like electrum or any of your choice.

https://bitcointalksearch.org/topic/m.59753846

madmartyk

legendary

Activity: 2702

Merit: 1030

Yes I am a pirate, 300 years too late!

OK I have been playing around with this on and off. When I get the results (say from the example above) I can't IMPORTPRIVKEY into my wallet. How do I get it to display a private key that can be imported into a wallet?

zahid888

member

Activity: 275

Merit: 20

the right steps towerds the goal

Will you please add stride mode in Vanbitcracken where according to my speed I choose 7 characters random hex Ex: 7bbc039 and put stride mode -- stride 10000000 here 7 zeros are my random hex and I started counting after these 7 random hexes, suppose I am searching for the 64-bit key and the key is f9aa309c97bbc039 and I put the command --keyspace 7bbc039:fffffffff7bbc039 --stride 10000000 when I start counting through this command I have to count 9 hex to reach the end of keyspace and I will get the key in 1 minute as I say according to my speed. hope you understand what I am trying to say. if it would happen I will be very thankful to you.

Angelo1710

newbie

Activity: 26

Merit: 0

Tnx! I understand it all now after your in-depth explanation.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote from: Angelo1710 on August 29, 2021, 11:26:07 AM

Quote from: WanderingPhilospher on August 28, 2021, 09:46:55 AM

Quote from: Angelo1710 on August 28, 2021, 07:12:14 AM

Btw any idea why program is not working when you try to search for both compressed and uncompressed addresses? Getting error when I try and program stops.

Can you show what commands you are using when receiving this error? Your batch file command or cmd line?

Quote

Tnx, now I understand. Had no idea your -r feature does that, will use it from now on, that is exactly what I wanted.

The Spread version does not do this, it is the Random version that does that.

I was using -b command. Ok will try VBCRandom verson later today and let you know. Can you explain more how exactly it creates random points and how many of them does it creates. If my gpu runs lets say at 100mk/s, and I use -r 100, will it then run at 100mk/s and evey single key would be random from those 100m keys?
I want it to run at 100mk/s for example and that every key is created randomly through whole keyspace I defined with --keyspace. Lets say I want it to search through --keyspace 1000000000000:FFFFFFFFFFFFF and that it runs through that whole keyspace completely randomly, every single point in that keyspace is generated randomly.
Sorry idk how to explain this better.

REread the above or the github page. The keyspace is not really needed in the random version.

(-topr stands for toprange and -subr stands for subrange)

If you wanted to generate random keys in the 8000000000000:FFFFFFFFFFFFF range (52 bit range) you would use the flags:
-topr 8000000000000 and -subr 51

Using subr of 51 (51 bits) will add 0 to 7FFFFFFFFFFFF TO the topr of 8000000000000. So the lowest point created will be in the 8000000000000 range and the highest point that can be created is FFFFFFFFFFFFF (topr 8000000000000 + subr 7FFFFFFFFFFFF)

If you wanted to just stay in the 8000000000000 range, you would use -topr 8000000000000 and -subr 48.

The random feature is generated via built in Rand function.
How many random points created each rekey depends on the grid size you use. The program currently has x*8,512, meaning if your GPUs grid size is 40x100 then by default, the final grid size would be 320x512 (40*8 = 320 for the x grid (times) the default 512 for the y grid) = 320x512. So in this case, each rekey will generate 320x512 = 163,840 random points. After points are generated they will start from that point and move sequentially until a rekey is made. So if your GPU gets 100 MK/s and you set the -r to 200, -r 200, then you would generate new random points roughly every 2 seconds.

Angelo1710

newbie

Activity: 26

Merit: 0

Quote from: WanderingPhilospher on August 28, 2021, 09:46:55 AM

Quote from: Angelo1710 on August 28, 2021, 07:12:14 AM

Btw any idea why program is not working when you try to search for both compressed and uncompressed addresses? Getting error when I try and program stops.

Can you show what commands you are using when receiving this error? Your batch file command or cmd line?

Quote

Tnx, now I understand. Had no idea your -r feature does that, will use it from now on, that is exactly what I wanted.

The Spread version does not do this, it is the Random version that does that.

I was using -b command. Ok will try VBCRandom verson later today and let you know. Can you explain more how exactly it creates random points and how many of them does it creates. If my gpu runs lets say at 100mk/s, and I use -r 100, will it then run at 100mk/s and evey single key would be random from those 100m keys?
I want it to run at 100mk/s for example and that every key is created randomly through whole keyspace I defined with --keyspace. Lets say I want it to search through --keyspace 1000000000000:FFFFFFFFFFFFF and that it runs through that whole keyspace completely randomly, every single point in that keyspace is generated randomly.
Sorry idk how to explain this better.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Here is VBCRandom in action.
Batch file settings:

Code:

VBCRandom -t 0 -gpu -gpuId 0 -topr 8000000000000000 -subr 48 -r 480 --keyspace 8000000000000000:FFFFFFFFFFFFFFFF -o randomtest.txt 16jY7q

Results:

Code:

Started Sat Aug 28 12:32:28 2021
Start Range  :  8000000000000000
End   Range  :  FFFFFFFFFFFFFFFF
Searching For:  16jY7q
Compression  :  Compressed
CPU threads  :  0
GPU          :  GPU #0 NVIDIA GeForce GTX 1060 6GB (10x128 cores) Grid(80x512)

Random Key   :  800007AC8B3D5525
Random Key   :  8000201C33F5235B
Random Key   :  8000E2F090E63C7D
 [00:00:04 Run Time ] [Speed 82.524 MK/s] [Total Keys: 335,544,320] [# Rekeys: 0] [Found: 2]
Random Key   :  8000208FB1B474F6
Random Key   :  8000B9FC61E9ABA1
Random Key   :  8000F0310FBE3DD2
 [00:00:08 Run Time ] [Speed 82.563 MK/s] [Total Keys: 671,088,640] [# Rekeys: 1] [Found: 4]
Random Key   :  80004698D58E9E8F
Random Key   :  800089612D96CDA0
Random Key   :  8000C2190CD91261
 [00:00:15 Run Time ] [Speed 81.609 MK/s] [Total Keys: 1,258,291,200] [# Rekeys: 2] [Found: 6]
Random Key   :  800043E67DBAB51D
Random Key   :  800098B29829B7A7
Random Key   :  800045B53E8E1753
 [00:00:20 Run Time ] [Speed 79.286 MK/s] [Total Keys: 1,593,835,520] [# Rekeys: 2] [Found: 6]

Key results:

Code:

Pub Addr: 16jY7qzxujzi1K7GaEc17ZFokFymagY3jG
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLz94bU7Lw952JxZUX
Priv (HEX): 0x000000000000000000000000000000000000000000000000800015BE8DF950C5

Pub Addr: 16jY7qdry8xB4v6JeMH2R3ViVTSTzDGv2B
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzUZ1qwKHqCmVgPRj
Priv (HEX): 0x000000000000000000000000000000000000000000000000800064574E06912E

Pub Addr: 16jY7qwSUyCss5jZYDjgJofLe7KgKxiCQo
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzGCmCHBUm9fupLgz
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000328A78D70051

Pub Addr: 16jY7q7x9EjwysPAYtappeDX6Lqtm32ekf
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzCiYnMdjWKzRsXUn
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000247B3183BFDC

Pub Addr: 16jY7qTWTgUzCEEH7E9UFxVKALnvCcykwV
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLziDMQ1SzkL55t52w
Priv (HEX): 0x00000000000000000000000000000000000000000000000080009B6E64AE0CAD

Pub Addr: 16jY7qwSwoyaH2NT2dKsY15h11Gma5bccb
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzSjUdaY9XWkAo8pE
Priv (HEX): 0x00000000000000000000000000000000000000000000000080005D00CB38A1B5

Pub Addr: 16jY7qCNptT19yStBa3tgVFy2k7CvhLi8t
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvM13ZD8mLPHJMsj9c6
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000E96EBB6FFC70

Pub Addr: 16jY7q3WZumGZ4gbrDTSte9JTbhEniZpqP
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzLQVfZGJ81tzYnbi
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000437CBF9A4063

Pub Addr: 16jY7qSaxGdCNribBnf6oxcpaw7aBUA6nN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzMkoUUXmUpiqDSm1
Priv (HEX): 0x000000000000000000000000000000000000000000000000800048EE90360155

Pub Addr: 16jY7qSV4qyaXJNmwWCu2t4DRWHuTnQuwz
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLz9toCoHuQiZuBD2p
Priv (HEX): 0x000000000000000000000000000000000000000000000000800019188671357A

Pub Addr: 16jY7qJ3MdatyubzBQ4e67n5D2iJRqFrDY
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYvLzZLFmMZj3v26fWhh
Priv (HEX): 0x0000000000000000000000000000000000000000000000008000779DFF73D53B

See how every new random key is within the same 48 bit range? Now you could change the -topr to whatever toprange and the -subr to whatever subrange. If in the example above you wanted to search every possible range in the toprange of 8000000000000000, you would use -topr 8000000000000000 and -subr 60.

Make sense?

use the -b for compressed and uncompressed.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote from: gamefinder on August 28, 2021, 10:08:36 AM

Quote from: WanderingPhilospher on August 27, 2021, 04:48:27 PM

You control how often it generates random points using the -r (rekey) feature.
My program just keeps generating random points and it will never end, until you close the program down. It will never start with random points and walk them sequentially until whole keyspace is searched.

I've tried this, but I have a question about it, when it generates random points, is it confined to the current 2^? I put in C000000000000000 as a starting keyspace, will it only generate random points within the 2^35 vs all the way up to 2^64?

For example I put a --keyspace of C000000000000000:E000000000000000, it found a key at C00000037925BAAB, does this imply it's presently not searching in a higher range in the keyspace?

Also, is it completely random? As I've stopped and restarted, and always find the same key when using -r.

The Spread version does not work the random I have spoke about, Spread acts as normal, starts at start range and progresses the same way each time.
Go to Random version:
https://github.com/WanderingPhilosopher/VanBitCrackenRandom
I haven't had time to upload how to use the flags. But if you reread:

Quote

top range/keyspace/beginning range you want to start with
800000
so that is a 24 bit top range

You define if you want random keys generated in all of 24 bit range by selecting subrange of 23; now it will generate random points from 8000000 through FFFFFF
if you wanted to search subrange of 16 bit you select subrange of 16; now it will generate random points from 8000000 through 80FFFF

You control how often it generates random points using the -r (rekey) feature.

You will have an understanding.

use -topr for toprange such as -topr 800000
use -subr for subrange (in bits) such as -subr 16
use the -r to tell program how often to regen new random points within that range such as -r 1200 (every 1200,000,000 keys)

With that setup, the program will generate random points from 800000 to 80FFFF.

Try it let me know how it works for you and if you have any questions.

gamefinder

newbie

Activity: 13

Merit: 0

Quote from: WanderingPhilospher on August 27, 2021, 04:48:27 PM

You control how often it generates random points using the -r (rekey) feature.
My program just keeps generating random points and it will never end, until you close the program down. It will never start with random points and walk them sequentially until whole keyspace is searched.

I've tried this, but I have a question about it, when it generates random points, is it confined to the current 2^? I put in C000000000000000 as a starting keyspace, will it only generate random points within the 2^35 vs all the way up to 2^64?

For example I put a --keyspace of C000000000000000:E000000000000000, it found a key at C00000037925BAAB, does this imply it's presently not searching in a higher range in the keyspace?

Also, is it completely random? As I've stopped and restarted, and always find the same key when using -r.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote from: Angelo1710 on August 28, 2021, 07:12:14 AM

Btw any idea why program is not working when you try to search for both compressed and uncompressed addresses? Getting error when I try and program stops.

Can you show what commands you are using when receiving this error? Your batch file command or cmd line?

Quote

Tnx, now I understand. Had no idea your -r feature does that, will use it from now on, that is exactly what I wanted.

The Spread version does not do this, it is the Random version that does that.

Angelo1710

newbie

Activity: 26

Merit: 0

Btw any idea why program is not working when you try to search for both compressed and uncompressed addresses? Getting error when I try and program stops.

Angelo1710

newbie

Activity: 26

Merit: 0

Quote from: WanderingPhilospher on August 27, 2021, 04:48:27 PM

Quote from: Angelo1710 on August 27, 2021, 11:42:46 AM

Quote from: WanderingPhilospher on August 24, 2021, 04:51:32 PM

Quote from: gamefinder on August 24, 2021, 09:09:39 AM

I can donate a few dollars in BTC for the random implementation, but sadly I don't have much.

I may have what you already want.

I just need to make sure it is what it is.

Please reexplain what you are wanting to do. Is it just to create random points over and over inside a defined keyspace?

If it's something I have or can do, no need for donation, I do it to tinker, to actually get something to work.

Tested program, it's nice. About 2x faster then pika's random version of bitcrack. I would love to have -r random feature here also. If possible that every point that is created is random in defined keyspace, not just starting points that are random like in bitcrack. So you define your keyspace and it goes randomly through whole keyspace it on each point, not just creating starting points and going in +1 increments.

You say "...define a keyspace and it goes randomly through whole keyspace "it" (not sure what you meant by it) on each point, not just creating starting points and going in +1 increments."
I do not understand how this is random. It sounds like you want it to go check each point in the keyspace or do random jumps through the keyspace. I get confused when you say through the whole keyspace. What I have does the following:

top range/keyspace/beginning range you want to start with
800000
so that is a 24 bit top range

You define if you want random keys generated in all of 24 bit range by selecting subrange of 23; now it will generate random points from 8000000 through FFFFFF
if you wanted to search subrange of 16 bit you select subrange of 16; now it will generate random points from 8000000 through 80FFFF

You control how often it generates random points using the -r (rekey) feature.

But this program is designed to generate and regenerate random points in a given keyspace as often as you like. It will generate your GPU grid size random points and go sequentially from each random point. Once it rekeys, it generates new random points and goes sequentially. Let's say your GPU gets 100 MKey/s; you could put -r 100 and the program would generate new random points every 1 second.

The difference is; bitcrack generates random starting points and goes sequentially until keyspace has been searched; the program eventually ends.

My program just keeps generating random points and it will never end, until you close the program down. It will never start with random points and walk them sequentially until whole keyspace is searched.

Tnx, now I understand. Had no idea your -r feature does that, will use it from now on, that is exactly what I wanted.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

Quote from: Angelo1710 on August 27, 2021, 11:42:46 AM

Quote from: WanderingPhilospher on August 24, 2021, 04:51:32 PM

Quote from: gamefinder on August 24, 2021, 09:09:39 AM

I can donate a few dollars in BTC for the random implementation, but sadly I don't have much.

I may have what you already want.

I just need to make sure it is what it is.

Please reexplain what you are wanting to do. Is it just to create random points over and over inside a defined keyspace?

If it's something I have or can do, no need for donation, I do it to tinker, to actually get something to work.

Tested program, it's nice. About 2x faster then pika's random version of bitcrack. I would love to have -r random feature here also. If possible that every point that is created is random in defined keyspace, not just starting points that are random like in bitcrack. So you define your keyspace and it goes randomly through whole keyspace it on each point, not just creating starting points and going in +1 increments.

You say "...define a keyspace and it goes randomly through whole keyspace "it" (not sure what you meant by it) on each point, not just creating starting points and going in +1 increments."
I do not understand how this is random. It sounds like you want it to go check each point in the keyspace or do random jumps through the keyspace. I get confused when you say through the whole keyspace. What I have does the following:

top range/keyspace/beginning range you want to start with
800000
so that is a 24 bit top range

You define if you want random keys generated in all of 24 bit range by selecting subrange of 23; now it will generate random points from 8000000 through FFFFFF
if you wanted to search subrange of 16 bit you select subrange of 16; now it will generate random points from 8000000 through 80FFFF

You control how often it generates random points using the -r (rekey) feature.

But this program is designed to generate and regenerate random points in a given keyspace as often as you like. It will generate your GPU grid size random points and go sequentially from each random point. Once it rekeys, it generates new random points and goes sequentially. Let's say your GPU gets 100 MKey/s; you could put -r 100 and the program would generate new random points every 1 second.

The difference is; bitcrack generates random starting points and goes sequentially until keyspace has been searched; the program eventually ends.

My program just keeps generating random points and it will never end, until you close the program down. It will never start with random points and walk them sequentially until whole keyspace is searched.

Topic: VanBitCracken - a program to use for 32 BTC challenge (supports RTX 30xx cards) - page 7. (Read 5382 times)