Topic: Large Bitcoin Collider Thread 2.0 - page 14. (Read 57143 times)

Hard to say when I do not see the little program. On my machine the LBC generator takes like 0.2 s for both compressed and uncompressed checks of 16.7M keys.
No - I do not use the code from brainflayer anymore, but I believe even the original code didn't take so long on my CPU (more like 0.4s instead of 4s)

---

On a different topic:

I updated the views. The download link to the LBC Appliance is updated. Careful, it's a 1.8GB download. It has an updated Arch Linux, newest available BLF, client and a haswell generator.
You will now see also a Crowdfunding page, which is merely there to stipulate a discussion about improving GPU performance (see what arulbero wrote above about GPU limited issues).
By using an improved ECC lib and symmetries, we may run sooner into a GPU limited situation in the future.

On the CPU generator the bloom check is only 1%?
I made a little program with:

1) my aecc
2) sha256 and ripemd160 from supervanitygen
3) bloom check from brainflayer

and I got: 1,16s for aecc, 12,4s for sha256+ripemd160, 4s for bloom check => total: 17,55s for 16,7 Mkeys

Then: 6,6% for aecc, 70,6% for sha256 and 22,8% for bloom check. Maybe I'm not using the bloom check in the best way, but 23% against 1% is too much.

No, the bloom search (more precisely: bloom check) accounts for about 1% of the total work.

tks arulbero for work 
I was thinking that the project was abandoned

This is a Python version to extract data from utxo: https://bitcoin.stackexchange.com/questions/56655/getting-a-crypto-proof-utxo-set
https://github.com/sr-gi/bitcoin_tools

Like Wuille noted, Bitcoin Core 0.15 has changed db format of the Utxo set. Maybe you could try with a old version of Core.
  

A little explanation (and update) for the LBC users:

LBC generator has 3 components:

1) ECC generator --> 2) sha256 + ripemd160 --> 3) bloom search

1) this component computes the generation from the private key of the corresponding public key. We have only a CPU version of this library.

2) each single public key produces 2 160-bit strings (addresses = hash of the public key), uncompressed and compressed addresses; Rico developed 2 optimized versions of this component, one for CPU and one for GPU. In the GPU case the output of the CPU is sent to the GPU.

3) check if the addresses generated in the step 2) are or not in the bloom filter (CPU version and GPU version).


For the systems GPU limited (GPU used at 90% or more) it is crucial to improve the component 2).

For the systems CPU limited (example: CPU used at 100% and GPU at 50%) it is important instead to improve the speed of the ECC generator, i.e. the rate at which the CPU feeds the GPU.

ECC generator is the component  I have been working on in the past months.
I'm improving the ECC library as much as I can. At this moment the library is almost 30% faster than the current one. On my CPU Kabylake, it takes only 1,16 s to generate 16,7 M public keys against the 1,64 s of the latest release.

For a system cpu limited, the new library could take a +30% speedup (exploiting completely the GPU's speed).
In that case I think that the LBC generator will be faster than oclvanitygen on all GPUs (for now the LBC generator is faster only on middle/slow gpu, but not on fast gpu).

For a system gpu limited, the only advantage is that you could use 3 cores to get (almost) the same performance as 4 cores now.

For a system without GPU there is a small speedup, because in the CPU generator only a 10% of the cpu work is about the ECC arithmetic, about 65% is for the sha256/ripemd160 task and about 25% for the bloom search.

Just to make it clear for everybody:

Yes, the project is still on, I haven't abandoned it.

I just happen to spend my energy currently on the BURST cryptocurrency, so there is not much time left for the LBC project at the moment.
I feel the need to make that clarification here, as there are 1st "stalkers" who use Burst discussions on Reddit to ask me about LBC
https://www.reddit.com/r/burstcoin/comments/75urgi/i_want_to_set_another_node_but_this_time_on_a_vps/dob21xk/

Please don't do that. There is a nice Discord Channel at https://discord.gg/AyEfZrY

Where you can get more interactive support from the great LBC community.

Also, there are at the moment some showstoppers that would need too much of my time to look into (like a broken blockparser, see https://github.com/znort987/blockparser/issues/65) if someone wants to give me a real nudge to update some things LBC (and I do have some pretty nice updates pending), fix that blockparser issue or find an alternative.

Arulbero has sent me a new version of his ECC lib which may be (I haven't tested it yet, but I believe his tests/claims) 20% faster.
I would want to include that too. So someone please look into the blockexplorer.

No downloads available on site?

A quick Google search indicates that Nvidia/Docker does not support Windows. For Linux, see this project here for Nvidia+Docker https://github.com/NVIDIA/nvidia-docker/tree/2.0

Can I participate from Windows?? Does it require GPU power or CPU power?

GPU version of LBC usually works only on Linux, not on Windows. With your Dockerfile is it possibile to exploit GPU on Win?

Just remember: Google is your friend 

I read the OP but it was too complicated.. like what are brain wallets? And what does he mean by trying to find private keys to addresses that have bitcoins in them? Is this some collective hacking attempt or something?

My guess is you are new to forums, new to reading threads, new to computers and not technically savy.

The very first post in a thread is called the "original post" or OP for sort.  This is where you will find out what the thread is all about.  So, before you ask any questions in a thread you should read the OP, the first post in the thread.  Then if you do not understand what the thread is about it then, and only then, you post a very specific question that is not answered in the OP.  In order to get to the OP you click on the 1 below where it says "Pages:" to get to the first page.  Or you can click here:

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

I don' think I understand completely what you mean by bitcoin collider. Could you please explain it is simple laymen words?

Thank you! My Dockerfile now works: https://github.com/dcw312/lbc-client-docker
You need to manually add the funds_h160 file. I'll try to post instructions for that.

I have Ubuntu 17.04.  With your command I get over 800 modules, these are related to LBC (if I remember properly)




EDIT:

Looking in to the Perl script these are modules you need for sure:

First of all, thank you for this project. Mostly because I suspected that bitcoin was vulnerable to key collision but when I shared these suspicions, I was told that the earth was more likely to explode than for that to happen. So your work will has done me the great service of seeming smarter than I am.

I tried yesterday to get the client running on my local machine yesterday. I tried using Docker to provide the safe sandbox discussed in the documentation.

I've put my Dockerfile on Github at https://github.com/dcw312/lbc-client-docker

I'm new to Arch Linux and Perl so I don't expect to make significant contributions.

As an aside, I'm a little surprised that the dependency management of Perl seems to be such a challenge. In my work yesterday, I'd keep seeing messages like "LWP::UserAgent not found - installing it." I'm most recently using Java and Maven so I expected the dependency management to be a bit more straightforward.

Would someone be willing to reply with the list of Arch Linux packages that are installed on the VM image?  I ask so I can add them to the Dockerfile.

This can be done with:

Please also supply installed cpan modules:
Or one of the other methods described here: https://stackoverflow.com/questions/115425/how-do-i-get-a-list-of-installed-cpan-modules#

Also, if something special was required to install cpan, please let me know so I can close this https://github.com/dcw312/lbc-client-docker/issues

Thanks!!  

p.s. My motivation is mostly to continue to see how Docker can be used for sandboxed work like this.

Hi guys,

I installed the LBC appliance, ran it with VMWare Player, did ./LBC -x and I get the following error:

"Testing mode. Using page 0, turning off looping.

Benchmark info not found - benchmarking.... "gen-hrdcore-sse42-linux62" not found/executable"

I also got a "wrong: minversion 1.140" error.

How do I fix this?

Thanks,

Thanks, works now! Only thing not working is the --email option. Anyone got that working?