Large Bitcoin Collider Thread 2.0

[rico666]

Such an interesting project. Could the collider be applied to alts with smaller market caps and fewer address?  

In principle yes, but

fewer addresses = less hit probability

(I assume with "fewer addresses" you mean those in use/with funds)

Also, the size of the codomain (the number of possible addresses) of the address generation process is an important parameter. The only reason why I started this in the 1st place, are Bitcoins' 160bit (for both P2PKH and P2SH) which I believe will show being insufficient within a couple of years (contrary to what "educated" guesses may say).

An almost 1:1 Litecoin-collider could be done, obviously, because Litecoin is an almost 1:1 Bitcoin clone.  

I have not looked into the other alts too much, but from what I have seen e.g. at Monero, a collider would be really futile there.

[1713993599]

1713993599

[1713993599]

1713993599

[1713993599]

1713993599

[SopaXT]

Ethereum seems to be held together with band-aids. I am sure that there must be some bad private keys as it's an emerging technology with lots of bad implementations, and actually an Ethereum address is just hex(Keccak256(pubkey)[12:]), where pubkey is an ECDSA public key, which is represented as 32-bytes for x and 32 bytes for y (just the good old uncompressed public key with the first byte removed) - also easy to calculate and to make a bloom filter for.

[killyou007]

hi @rico666

i am trying to run LBC client on amazon ec2 p2.16xlarge (64CPUs with GPU)
but getting an error like GPU authorize: no
it's working only on cpus
i installed all compatible drivers and there is no issue from hardware.
what would be the issue?
thanks in advance...

regards,
Killer King

[rico666]

i am trying to run LBC client on amazon ec2 p2.16xlarge (64CPUs with GPU)

The p2.16xlarge is supported and would give you around 170 Mkeys/s (at the moment this would be equivalent to the total of the current pool capacity...).

In order to get GPU authorize, you have to submit 3000 Gkeys. With CPU. That's our "Proof of discipline". Also it's a little gesture of fairness for the early adopters. You have now around 680 Gkeys.

You should - by the way - refrain from doing things like

Code:

1496064624    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496064763    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496064848    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496064915    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496064934    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065010    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065068    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065115    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065262    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065384    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065443    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065645    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065690    50.19.147.36 PUT-NIL: tampered (K1LL3RK1NG-65f2)
1496065793    50.19.147.36 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
1496065848    50.19.147.36 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
...
1496066026    50.19.147.36 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
1496066101    50.19.147.36 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
1496066608     52.7.40.130 PUT-NIL: tampered (K1LLY0UALL-65f2)
...
1496067243     52.7.40.130 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
1496067535     52.7.40.130 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)
1496068278   34.202.31.106 PUT-NIL: blacklisted (K1LL3RK1NG-65f2)

  Ok?

So maybe you are cheaper off using a m4.16xlarge (64 vCPUs) and as soon as you have 3000 Gkeys, move to the p2.xxx

[killyou007]

actually i have 6 instances with p2.16xlarge and 6 with f1.8xlarge (fpga) instances.
i have these instances for another project since last year. but if you would give an opportunity i will use them for LBC.
hope you can understand the issue and let me know your opinion.
thanks in advance and waiting for your response asap.......

[killyou007]

it's the issue because i simply modified the client with GPU authorize 0 to 1
then i got blacklisted. but i am paying for amazon ec2 more than 28K per annum, so i would like to use it at least per LBC.
that's the only thing i modified in LBC client.
and i already submitted more than 3000 G keys with royal360 user id.
hope you can understand and authorize for gpu.
thanks in advance...

[rico666]

it's the issue because i simply modified the client with GPU authorize 0 to 1
then i got blacklisted. but i am paying for amazon ec2 more than 28K per annum, so i would like to use it at least per LBC.
that's the only thing i modified in LBC client.
and i already submitted more than 3000 G keys with royal360 user id.
hope you can understand and authorize for gpu.
thanks in advance...

The client is made so even adding a whitespace is considered tampering: please don't.

ROYAL247 has submitted 1410 Gkeys to date... so that's not sufficient. (You can find out with ./LBC -q command)
But the nick is rising fast https://lbc.cryptoguru.org/stats/ROYAL247, Let it work overnight and you have your GPU auth.

HOWEVER, I could enable GPU auth immediately for you (because honestly that's quite some punch hardware access you have there) if you let me play with an F1 instance for - say - 3x8 hours then.  Gentlemen agreement

6 instances p2.16xlarge could reach the 1 Gkeys/s on their own ... intriguing.

[rico666]

Hey guys,

you're the only 2 left with clients older than 1.140 (you have 1.067 in case you didn't know).
Please see https://bitcointalk.org/index.php?topic=1877935.msg18665920#msg18665920 ("News" link from my sig)

As of tomorrow, the server will require client 1.140 as minimum version. Shortly thereafter I would like to phase out the FTP updates.
The new versions accept updates of the client and the generator only via a HTTPS connection (with name validation on  )
so they address and fix some of the valid security concerns raised about a month ago.

You guys are bravely fighting your way to 3000 Gkeys, so please don't let the server pull the plug on you.

edit: If these are some "fire and forget" clients, I recommend the "eternal run" setup, see here
https://lbc.cryptoguru.org/man/user#eternal-run (scroll down the "Get Work" section)
This will keep your clients, generators and BLF file up to date with minimum overead (check once a day).
Also, it's even more robust against transient network errors or even errors of the update process itself.

[rico666]

ROYAL247 has submitted 1410 Gkeys to date... so that's not sufficient. (You can find out with ./LBC -q command)
But the nick is rising fast https://lbc.cryptoguru.org/stats/ROYAL247, Let it work overnight and you have your GPU auth.

Looks like you did it! Congrats.

For better GPU performance, Amazon recommends you do

nvidia-smi -pm 1
nvidia-smi --auto-boost-default=0
nvidia-smi -ac 2505,875


(with sudo if you are not root already), then

./LBX -gpu -x

in order to get a good/updated speed benchmark for your GPU client.

And after that, the p2.16xlarge are to be started with

LBC -c 64 -gpu -gopt dev=1-16:lws=512

be prepared that upon 1st invocation, it takes quite a while until the machine has started up all 64 processes. In my experience, the AWS IO subsystem is laggy like hell. After that all should be well.

AWS systems differ slightly in their performance even in the same machine class. The bigger the system, the bigger the performance variance. You can expect

p2.xlarge ~11 Mkeys/s
p2.8xlarge ~80 - 88 Mkeys/s
p2.16xlarge ~155 - 170 Mkeys/s

[killyou007]

hi

thanks for your support.
how can i use fpga instances? what is the command?
thanks in advance...

regards,
killer king

[rico666]

how can i use fpga instances? what is the command?
thanks in advance...

FPGA support has not been developed yet. I wish, but we're not there yet.

Oh and before I forget it:
Of course when testing AWS instances you have to use

./LBC -gpu -x -gopt lws=512

(the lws=512 is important, else you get a CL_OUT_OF_RESSOURCES or similar)

[gizmoh]

Hey Rico,

Apparently someone stumbled on an Eth collision...

https://twitter.com/RNR_0/status/869950371141177344

https://etherscan.io/address/0x2e7542eC36df6429D8C397F88C4Cf0c925948f44

Pub key: 0x2e7542eC36df6429D8C397F88C4Cf0c925948f44


Would be interesting to hash investigate ETH...

[rico666]

Apparently someone stumbled on an Eth collision...
https://twitter.com/RNR_0/status/869950371141177344

I don't feel qualified enough to comment on these ETH things. From the tweet it looks like he claims to have found eth by simply generating a privkey with NodeJS. So to me, it looks more like the RNG in NodeJS would be #rekt.

@killyou007

I see you're rising quite fast in the top30. At ~ 140 Mkeys/s no wonder, but somehow it doesn't fit the expected performance of a p2.16xlarge (let alone 6 of them). Care to let me in on your rig specs? Feel free via PM or to bots@cryptoguru.org if you don't want to discuss that officially.

@oldclients

The minimum client version accepted by the server is 1.140 as of now. Sorry.


Also, as of this writing, the pool has searched the magnificent number of 5555.55 trillion private keys (11111.1 trillion addresses). I managed to snapshot it almost at the right moment:

[vh]

Project looks interesting.

The server I was planning to allocate to contribute has no GPU @ Ubuntu 16.04.

I made it trough ./LBC -h and got stuck at ./LBC -x

Code:

# ./LBC -x
Will use 12 CPUs.
You have 1996.6953125 MB memory and running 12 threads requires 6600 MB.
I've reduced the requirement to 3 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... ./kardashev-westmere: error while loading shared libraries: libOpenCL.so.1: cannot open shared object file: No such file or directory
Generator validity check failed. Expected: 5, Got: 0
With output:
--

# uname -a
Linux ubuntu 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

no gpu = no opencl

*edit:
Googling lead me to your original thread.   Seems like OpenCL is required.   More reading to do.   

[vh]

Got past that and the odd missing blf error.   Looks like I'm good to continue.

Code:

#./LBC -x
Will use 12 CPUs.
Testing mode. Using page 0, turning off looping.
Benchmark info not found - benchmarking... done.
Your speed is roughly 401519 keys/s per CPU core.

[rico666]

Got past that and the odd missing blf error.   Looks like I'm good to continue.

Code:

Your speed is roughly 401519 keys/s per CPU core.

I see a user "___vh___" successfully asking for and delivering blocks.

May appear within a hour or two here: https://lbc.cryptoguru.org/stats/___vh___

As you probably found out already, the kardashev generators are unified binaries (CPU and GPU support) and they need a libOpenCL present - even if it is just a dummy/fake lib (for CPU only clients).

[Jude Austin]

Hi,

What does this mean:

GPU authorized: yes
Benchmark info not found - benchmarking... done.
Your speed is roughly 3245154 keys/s per CPU core.
Ask for work... got blocks [5393996735-5394007934] (11744 Mkeys)
oooooooooo0 just got out of the pool with exit code: 255 and data:
3 just got out of the pool with exit code: 255 and data:
oooooooooooooooooo


Thanks,
Jude

[rico666]

What does this mean:

GPU authorized: yes
Benchmark info not found - benchmarking... done.
Your speed is roughly 3245154 keys/s per CPU core.
Ask for work... got blocks [5393996735-5394007934] (11744 Mkeys)
oooooooooo0 just got out of the pool with exit code: 255 and data:
3 just got out of the pool with exit code: 255 and data:
oooooooooooooooooo

Any other errors on screen? Most of the time this means the OpenCL failed to start

* no GPU found (probably not your case)
* worksize too big (not your case if you are not on Amazon)
* no memory left on GPU

In your case, it looks like

OCL error: CL_MEM_OBJECT_ALLOCATION_FAILURE (clEnqueueNDRangeKernel failed.)

edit: you sure you have up-to-date client/generators? I see you were last active 24 days ago, minimum client version is now 1.140, hopefully you have also a kardashev-generator too.

[Jude Austin]

What does this mean:

GPU authorized: yes
Benchmark info not found - benchmarking... done.
Your speed is roughly 3245154 keys/s per CPU core.
Ask for work... got blocks [5393996735-5394007934] (11744 Mkeys)
oooooooooo0 just got out of the pool with exit code: 255 and data:
3 just got out of the pool with exit code: 255 and data:
oooooooooooooooooo

Any other errors on screen? Most of the time this means the OpenCL failed to start

* no GPU found (probably not your case)
* worksize too big (not your case if you are not on Amazon)
* no memory left on GPU

In your case, it looks like

OCL error: CL_MEM_OBJECT_ALLOCATION_FAILURE (clEnqueueNDRangeKernel failed.)

edit: you sure you have up-to-date client/generators? I see you were last active 24 days ago, minimum client version is now 1.140, hopefully you have also a kardashev-generator too.

I installed everything new in a new directory.

It could be my distro install, I messed some shit up trying to install Boost.

Let me do a reinstall and try again.

Thanks,
Jude

[rico666]

I made a small modification to the server source:

Code:

    my $logtxt = "Query $id";                               # text to be logged

    if (!keys %{$entry}) {                                  # if there is no information yet about the client
        $logtxt .= " - not yet in DB.";                     # state so in the LOG
    }
    else {                                                  # here, we have client data
        delete $entry->{secret};                            # remove the (encrypted) password from the answer
        $entry->{gpuauth} = 1;                              # Happy Birthday LBC (From 2017-08-01 to 2017-09-01)
    }
    log_lbc($logtxt);                                       # LOG
    return  $json->encode($entry);                          # return our answer