Search content
Sort by

Showing 10 of 10 results by Yahkinator
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 02/08/2018, 18:36:45 UTC
Is rico666's original Large Bitcoin Collider dead? There was so much activity on it before, but after the FUD that there was a backdoor in it, I think the users got scared.
It still running bro. https://lbc.cryptoguru.org/stats


Most people abandoned the project when they figured out the created could change the code without their consent.

I disagree.  It's still running, but seems to have less and less people running the clients. There was a core group for quite a while, but the biggest member left several months ago.

Probably the biggest thing that is contributing to the demise is Rico focusing his programming efforts elsewhere.  He's not updating the client any more, not fixing any bugs, and pretty much doesn't visit the Discord channel any more.  He's essentially abandoned the project himself. 
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 30/07/2018, 06:15:21 UTC
I have it running on several machines now.  Pulled the latest bitcoin address with balance file and am looking for anything that has 10btc or more.  Pulling in 142k addresses does knock about 10% off my hashing speed, but it's still much faster than LBC was on a P5000.  It actually uses all of the video card instead of being CPU bound.  If it could use a bloom filter like LBC does, it would be even faster and look for more.

Thanks for doing this.
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 28/07/2018, 15:11:37 UTC
oclvanitygen -D 0:0 -f addresses.txt -o found.txt -k lastkey.txt 3000
What's the command you ran to have those return positive?

The command is OK.
Are you really talking about NDV fork of oclvanitygen ?
Do addresses.txt file contain 160 bounty addresses? Case of chars matters.

There is a verbose switch. Post the log.

I got it working on Ubuntu.  I was running LBC at the same time, and they were fighting for memory.  Still no go on the Windows version, but it's popping a CPU check error.  Might be because I'm using an integrated card for testing.  Some time this week I'll throw a couple ATI cards in the box and see if those will work through windows.

Thanks for the help and thanks for setting this up!
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 28/07/2018, 04:47:11 UTC
Fired up my Ubuntu and dowloaded the code.  Running an Nvidia card in that box.  Compiled it and ran the same command:

oclvanitygen -D 0:0 -f addresses.txt -o found.txt -k lastkey.txt 3000

Still doesn't find anything. 

What's the command you ran to have those return positive?
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 27/07/2018, 19:24:28 UTC
I guess these zillions of leading zeros transform your HEX to some crapy WIF.
Also HEX should be uppercase, at least in Linux.

oclvanitygen -D 0:0 -f addresses.txt -o found.txt -k lastkey.txt 3000
Start with 3000
Searching for 160 addresses
81920/131072
[1.70 Mkey/s][total 44564480]

Removed the leading zeros.  Capitalized the numbers.  Cheesy
Still doesn't find anything.
Can you share a command line that returns a find?
Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
Yahkinator
on 27/07/2018, 10:05:41 UTC
Andzhig, you should write your native language, because when you write in English I always get an impression that you have undertreated meningitis.

lol.  I'm glad I'm not the only one that was left just scratching my head.

Hey Holy_ship, can you check on the thread about your ndv vanitygen build?  I have a couple questions in there and I can't message you because I'm still a newbie on here.  Smiley
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 26/07/2018, 13:15:42 UTC
To reiterate, using
Code:
oclvanitygen -D 0:0 -f addresses.txt -o found.txt -k lastkey.txt 0000000000000000000000000000000000000000000000000000000000003000
should reveal the addresses for the first 14 puzzle transactions within seconds.  It doesn't.
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 26/07/2018, 12:35:26 UTC
why should you -v replace with -D 0:0 or -D 1:0
Quote
Intel(R) HD Graphics 4600
it seems like you're running on a CPU card I do not know if it works fine.

It's an integrated video card.  It won't be the final machine I'll be using...just testing.

@holy_ship do you have an opinion?
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 25/07/2018, 20:37:40 UTC
he goes the other way from bigger to smaller. take that 000000000000000000000000000000000000000000000000000006bd3b27c800.


Still doesn't find it.  This mean anything to you?

oclvanitygen -v -f addresses.txt -o found.txt -k lastkey.txt 000000000000000000000000000000000000000000000000000006bd3b27c800
Start with 000000000000000000000000000000000000000000000000000006bd3b27c800
Searching for 160 addresses
Device: Intel(R) HD Graphics 4600
Vendor: Intel(R) Corporation (8086)
Driver: 20.19.15.4531
Profile: FULL_PROFILE
Version: OpenCL 1.2
Max compute units: 20
Max workgroup size: 512
Global memory: 1708759450
Max allocation: 427189862
OpenCL compiler flags: -DDEEP_PREPROC_UNROLL -DLOCAL_MEM_SIZE=65520
Loading kernel binary a278d6da1e690bf2f16f62f7f94db316.oclbin
allocsize=427189862, memsize=1708759450
Grid size: 1280x2048
Modular inverse: 10240 threads, 256 ops each
Bitmap size (bytes): 427189862

Start a thread81920/131072

Copy 1280 sequential points to the device
Copy the row stride array to the device
Move the row increments forward
Copy 1280 sequential points to the device
[1.52 Mkey/s][total 2621440]
Move the row increments forward
Copy 1280 sequential points to the device
Wait for the GPU to complete its job
Found -4593 candidadtes, check on CPU
CPU check failed Sad
[1.62 Mkey/s][total 5242880]
Move the row increments forward
Copy 1280 sequential points to the device
Wait for the GPU to complete its job
Found -4593 candidadtes, check on CPU
CPU check failed Sad
[1.65 Mkey/s][total 7864320]
Move the row increments forward
Copy 1280 sequential points to the device
Wait for the GPU to complete its job
Found -4593 candidadtes, check on CPU
CPU check failed Sad
[1.66 Mkey/s][total 10485760]
Move the row increments forward
Copy 1280 sequential points to the device
Wait for the GPU to complete its job
Found -4592 candidadtes, check on CPU
CPU check failed Sad
[1.68 Mkey/s][total 13107200]
save the priv. key to a file
Copy 1280 sequential points to the device
Copy the row stride array to the device
Move the row increments forward
Copy 1280 sequential points to the device
Wait for the GPU to complete its job
Found -4597 candidadtes, check on CPU
CPU check failed Sad
Post
Topic
Board Project Development
Re: Faster and Autonomous Large Bitcoin Collider fork
by
Yahkinator
on 25/07/2018, 16:35:32 UTC
Hello,
I have it up and running, but want to test that it is working correctly.

I run

oclvanitygen -f addresses.txt -o found.txt -k lastkey.txt 000000000000000000000000000000000000000000000000000006bd3b27c500

and would expect it to find the private key to 1PiFuqGpG8yGM5v6rNHWS3TjsG6awgEGA1 almost immediately since the private key is 6bd3b27c591.

It doesn't.  It blows past that private key without logging anything.

It is likely I'm doing something wrong, but I can't see the trees from the forest right now.  Can you advise?

Thanks!