Pages:
Author

Topic: Faster and Autonomous Large Bitcoin Collider fork - page 3. (Read 6759 times)

newbie
Activity: 19
Merit: 1
Vanitygen Plus has been reported not fully using all Vga when run multiple card (6 cards). Do you test vg from ndv with 6 cards, is the hash rate is sum of 6 cards.
jr. member
Activity: 115
Merit: 1
Quote
There is another project BitCrack that does the same thing and some people are getting 440 million  keys per second on a GTX 1080. Why is it so much faster than VanityGen??

Theoretically CUDA doesn't have noticeable advantage over OPENCL. So being 4-7 times faster means either this guy is a genius  Grin either this proggie is a scam.

I see that latest commit was in August, so it is easy to check for scam, try to search near 44218742292676575 (puzzle 56, which was found in September), if it finds - maybe it is not scam.

Also it is good idea to order some 3rd part review.
legendary
Activity: 1120
Merit: 1037
฿ → ∞
holy_shit likes to pour shit over the LBC, but let's stick to the facts:

  • this is merely a vanitygen mod/fork, not a fork of any LBC code
  • because there is no pool-coordination between the clients, everyone searches the same space. ergo, work is done twice,triple, quadruple,... times
  • it's not a collider, because you just search for the 32BTC bounty, not for all BTC addresses with funds (~ 18 million)

Don't get me wrong, I'm all for this project, because it keeps the "bounty-only" guys away from LBC, I just think that holy_shit makes promises (and claims) that show no correlation with the real world.

That being said, do not consider this any marketing for LBC. I have way too few time for maintaining LBC, so everyone participating there is basically "on his own".
newbie
Activity: 22
Merit: 3
There is another project BitCrack that does the same thing and some people are getting 440 million  keys per second on a GTX 1080. Why is it so much faster than VanityGen??
jr. member
Activity: 115
Merit: 1
Bounty56 found by someone...  Embarrassed moving to 57  Cry  Cry  Cry
jr. member
Activity: 184
Merit: 3
It seems to speed it affects PCI-E x16, x8, x4, x1. x16 more mkeys than x4. And with these collisions still the question whether they exist at all, if generate addresses in the first "bitcoin core 0.1" we will see
 
1FnVuHYKV7pW4TWR286GNi4KNT6UeaYTTf  5JrJw8iqnx7JHQ8NSSxM4XUGhgLU3mMqunMNLbawxWe1u9P4xZ4 884A50B3C55D5A085861904B98B930DEB8A519FB5F1998D914BDA6115A550A44
17AshpjqPgWsjLKYEbyBQ8XESYBrAsXy1v     5KXCn9sbHSdwdxWvfBnDAagWBV9eTxyZ6rmRBCESfxvmTyihNyU E09A864939B15C21309D297D63A88F51B3D0A95B2B11AA33D5189E50F1054B53
1Js1mFr9sEne154baEDsnvHb9j4TFFaj2v       5JFJ6QKpwPAWBhiUeQf4bTtus1GcBf6ymJrsoZ6UQrJBxEcAp8d     38C91E6407A8C639D2ACEC7C0DDFBC71CAE31D31686B41F5929552E48FDB7332
1J6zwmN987G2CthDEwc4rm2TPrskSYktU1    5K49E5MB8WRv8hy78Wz8JUV6PraazUiD8uG3CauzqxMVKpfw5KL  A3285FB9B1BE935FB2B6480F89C720FCCD8D30C1E8E11FCE6C10818C09A23A73

and their dec

61645851076440950040700147302009857952423202268196304805711354366578612570692
101591099338789881068330322780764063693808694983735576401369783241827565259603
25684865529875059200910699259210504468103551193592807433616257170740122186546
73798328873875309116869894990344634409190150273260165561706242786928783145587

what are the "first bitcoin" 2^160 it is unclear from whomever he came up with. these are the addresses 2^253 - 2^256. If there are collisions what is the use of doing such a safety run 2^256 if there is a collision somewhere 2^96 (as witnesses of a collision say). Then there would be no security...
jr. member
Activity: 115
Merit: 1
Hey, fixed a list. 38MK is the speed of 1070.
So, 1080 should get 60-70MK, nobody has reported yet.
jr. member
Activity: 115
Merit: 1
This VG version can search only decrementally - from starting number, in infinite loop it does minus 1

So for puzzle56 the range is 2^55 - 2^56

1. get your crystal ball, see there the right percentage, let's say it is 42%
2. count a bit. 42% of range is around 51160891766928834 decimal or B5C28F5C28F5C2 hex

echo 'obase=16; 2^55/100*42+2^55' | bc -l
B5C28F5C28F5C2

p.s. I already searched around 42 and 17 percent for a couple of months at speed 40MK. It's not there... Grin
newbie
Activity: 23
Merit: 0


I personally run with this 92k list.
Hi! Are you scan different space range or you calculate some range for step by step scaning ?
jr. member
Activity: 115
Merit: 1
Quote from: pinkflower
rico666 is doing an excellent job on Burst thats not reflected in its market value. If you are a fan of rico, support us in the Burst community.

This topic is not about splendid rico and his beautiful shitcoins Smiley

Quote from: giftseller8x
I have one MSI GTX 1060 3G Gaming X. Try this oclvanitygen it run at speed 27M key. Is it normal or slow.

1050 gets 15MK
1060 gets 25MK
1070 gets 38MK

address list can be up to 150-200 thousand keys without big speed penalty

I personally run with this 97k list.
It contains 4BTC++ addresses without any spends
or 15BTC++ with spends. Obviously "15BTC++ with spends" sometime
become empty and should be deleted.

http://80.211.89.91/92k
newbie
Activity: 3
Merit: 0
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?

I do not find the address program, I know that it is in the reverse order, but everything is similar to the one described above.
sr. member
Activity: 868
Merit: 259
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. 

Yeah he has been very busy developing on Burst and also trying to revive the project and take it to the top 50 in market value. Its a very ambitious goal but him and his team will be rewarded well if they can do it.

rico666 is doing an excellent job on Burst thats not reflected in its market value. If you are a fan of rico, support us in the Burst community.
newbie
Activity: 10
Merit: 0
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. 
member
Activity: 378
Merit: 53
Telegram @keychainX
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.
newbie
Activity: 19
Merit: 1
If it could use a bloom filter like LBC does, it would be even faster and look for more

There is of course a bloom filter in VG, but it's implementation is tuned for around 10k addresses. Sad
Mostly it's my fault - I thought that there are 10-20 thousand of fat addresses. Was wrong.

So, this part of VG can also be upgraded. Actually, this guy spent only couple of weeks on it. Smiley He looks like a pro, but a freelancer, not charity fund Smiley There were many things to do, but I wasn't ready to spend more, than $500

Your share is great.
I have one MSI GTX 1060 3G Gaming X. Try this oclvanitygen it run at speed 27M key. Is it normal or slow.
newbie
Activity: 19
Merit: 1
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
sr. member
Activity: 868
Merit: 259
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.
jr. member
Activity: 49
Merit: 1
The chance to actually generate the private keys for a particular bitcoin address is infinitesimal.

There are exactly 2^160 possible addresses. 2^160 is 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976.

To put that in perspective, there are only 2^63 grains of sand on all of the beaches of the Earth.

You'd have a better chance to mine solo on a cpu  Grin

member
Activity: 378
Merit: 53
Telegram @keychainX
If it could use a bloom filter like LBC does, it would be even faster and look for more

There is of course a bloom filter in VG, but it's implementation is tuned for around 10k addresses. Sad
Mostly it's my fault - I thought that there are 10-20 thousand of fat addresses. Was wrong.

So, this part of VG can also be upgraded. Actually, this guy spent only couple of weeks on it. Smiley He looks like a pro, but a freelancer, not charity fund Smiley There were many things to do, but I wasn't ready to spend more, than $500


I've come across 40.000+ Brainwallets, what is your target list size?
jr. member
Activity: 115
Merit: 1
If it could use a bloom filter like LBC does, it would be even faster and look for more

There is of course a bloom filter in VG, but it's implementation is tuned for around 10k addresses. Sad
Mostly it's my fault - I thought that there are 10-20 thousand of fat addresses. Was wrong.

So, this part of VG can also be upgraded. Actually, this guy spent only couple of weeks on it. Smiley He looks like a pro, but a freelancer, not charity fund Smiley There were many things to do, but I wasn't ready to spend more, than $500
Pages:
Jump to: