Large Bitcoin Collider (Collision Finders Pool) - page 30.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: Jude Austin on March 19, 2017, 02:20:53 AM

Quote from: GoldTiger69 on March 19, 2017, 01:43:25 AM

-snip-
How can I get such authorization? (besides the 0.1 btc)

Pray Rico is feeling generous when he sees this post. Tongue

or get in the top30 with your CPU(s)

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 19, 2017, 01:43:25 AM

Quote from: Jude Austin on March 19, 2017, 01:01:24 AM

Quote from: GoldTiger69 on March 19, 2017, 12:55:45 AM

Quote from: Jude Austin on March 18, 2017, 10:39:04 PM

Quote from: GoldTiger69 on March 18, 2017, 09:57:58 PM

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

Set your secret first by doing --secret x:yoursecret then you can just do --secret yoursecret

I have AMD cards working but only on 14.04 after 14.04 Ubuntu no longer supports fglrx so it won't work.

Let me know if you need any help.

Thanks,
Jude

Thanks for the answer, I'll try that latter on. First, I'll try just with CPU, because AFAIK, to be able to use GPU we need to be authorized first, don't we?

No problem.

Yeah, you will need to be authorized.

The LBC client will tell you when you use the --gpu argument if you are authorized or not.

Thanks,
Jude

How can I get such authorization? (besides the 0.1 btc)

Pray Rico is feeling generous when he sees this post. Tongue

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: Jude Austin on March 19, 2017, 01:01:24 AM

Quote from: GoldTiger69 on March 19, 2017, 12:55:45 AM

Quote from: Jude Austin on March 18, 2017, 10:39:04 PM

Quote from: GoldTiger69 on March 18, 2017, 09:57:58 PM

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

Set your secret first by doing --secret x:yoursecret then you can just do --secret yoursecret

I have AMD cards working but only on 14.04 after 14.04 Ubuntu no longer supports fglrx so it won't work.

Let me know if you need any help.

Thanks,
Jude

Thanks for the answer, I'll try that latter on. First, I'll try just with CPU, because AFAIK, to be able to use GPU we need to be authorized first, don't we?

No problem.

Yeah, you will need to be authorized.

The LBC client will tell you when you use the --gpu argument if you are authorized or not.

Thanks,
Jude

How can I get such authorization? (besides the 0.1 btc)

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 19, 2017, 12:55:45 AM

Quote from: Jude Austin on March 18, 2017, 10:39:04 PM

Quote from: GoldTiger69 on March 18, 2017, 09:57:58 PM

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

Set your secret first by doing --secret x:yoursecret then you can just do --secret yoursecret

I have AMD cards working but only on 14.04 after 14.04 Ubuntu no longer supports fglrx so it won't work.

Let me know if you need any help.

Thanks,
Jude

Thanks for the answer, I'll try that latter on. First, I'll try just with CPU, because AFAIK, to be able to use GPU we need to be authorized first, don't we?

No problem.

Yeah, you will need to be authorized.

The LBC client will tell you when you use the --gpu argument if you are authorized or not.

Thanks,
Jude

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: Jude Austin on March 18, 2017, 10:39:04 PM

Quote from: GoldTiger69 on March 18, 2017, 09:57:58 PM

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

Set your secret first by doing --secret x:yoursecret then you can just do --secret yoursecret

I have AMD cards working but only on 14.04 after 14.04 Ubuntu no longer supports fglrx so it won't work.

Let me know if you need any help.

Thanks,
Jude

Thanks for the answer, I'll try that latter on. First, I'll try just with CPU, because AFAIK, to be able to use GPU we need to be authorized first, don't we?

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: rico666 on March 18, 2017, 06:16:56 AM

It's official: 7 million pages on directory.io per second

My understanding is, most of this is done by one man and with CPUs.

Pool operation is seamless so far, I've seen a 13seconds network hiccup yesterday (which all clients handled well within 2 retries), and today I experienced a 500 error when calling the stats page. This too seems to have been only transient, although there may be some race condition at the bottom of this. => Pool operation purring like a cat

At the moment I'm completely dissecting the GPU client, as the segmentation faults I've been observing (read: have been driving me mad) for the past couple of days are 100% not my programming fault, but some internal error of the Nvidia OpenCL implementation. I'm trying to find a workaround and/or thorough internal analysis report to submit to Nvidia.

Rico

May I have a go at fixing this?

Thanks,
Jude

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: digaran on March 18, 2017, 11:05:25 PM

When you find a correct private key how do you know that it's the right one? in iphone if you enter wrong password more than 5 times you get locked out for some minutes to be able to enter and try again, now is there any way to implement such mechanism into bitcoin?

No, it doesn't work like that.

Imagine a normal key and lock, LBC isn't generating just the keys and trying them on a specific lock, LBC is generating the key AND the lock at the same time.

The key and lock combination creates a public hash which is what LBC is actually looking for by comparing to a list of existing public hashes with balances.

The ability to implement that system into Bitcoin is not feasible and would actually cause it to be less secure.

Rico,

Feel free to chime in with your genius, lol.

Thanks,
Jude

digaran

copper member

Activity: 1330

Merit: 899

🖤😏

When you find a correct private key how do you know that it's the right one? in iphone if you enter wrong password more than 5 times you get locked out for some minutes to be able to enter and try again, now is there any way to implement such mechanism into bitcoin?

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: GoldTiger69 on March 18, 2017, 09:57:58 PM

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

Set your secret first by doing --secret x:yoursecret then you can just do --secret yoursecret

I have AMD cards working but only on 14.04 after 14.04 Ubuntu no longer supports fglrx so it won't work.

Let me know if you need any help.

Thanks,
Jude

GoldTiger69

hero member

Activity: 583

Merit: 502

Hi, I'm trying to use LBC with the following parameters:
./LBC --address 1M4QXX...XXXX --cpus 2

But I get in return: Server don't like us, wrong secret.
What do I need to do to participate in the project?
Thanks in advance.

Edit: LBC - Large Bitcoin Collider v. 1.031
client fingerprint: db030a.........XXXX
AMD FX-4300 on Ubuntu 15.04

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: GoldTiger69 on March 18, 2017, 01:50:45 PM

And what about AMD? are you gonna do implementations for those too?

AFAIK some users operate their GPU client on AMD cards. Myself, I wasn't successful so far - but Jude Austin says he was (Ubuntu 14.04 with fglrx).

Rico

GoldTiger69

hero member

Activity: 583

Merit: 502

Quote from: rico666 on March 18, 2017, 06:16:56 AM

It's official: 7 million pages on directory.io per second

My understanding is, most of this is done by one man and with CPUs.

Pool operation is seamless so far, I've seen a 13seconds network hiccup yesterday (which all clients handled well within 2 retries), and today I experienced a 500 error when calling the stats page. This too seems to have been only transient, although there may be some race condition at the bottom of this. => Pool operation purring like a cat

At the moment I'm completely dissecting the GPU client, as the segmentation faults I've been observing (read: have been driving me mad) for the past couple of days are 100% not my programming fault, but some internal error of the Nvidia OpenCL implementation. I'm trying to find a workaround and/or thorough internal analysis report to submit to Nvidia.

Rico

And what about AMD? are you gonna do implementations for those too?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

It's official: 7 million pages on directory.io per second

My understanding is, most of this is done by one man and with CPUs.

Pool operation is seamless so far, I've seen a 13seconds network hiccup yesterday (which all clients handled well within 2 retries), and today I experienced a 500 error when calling the stats page. This too seems to have been only transient, although there may be some race condition at the bottom of this. => Pool operation purring like a cat

At the moment I'm completely dissecting the GPU client, as the segmentation faults I've been observing (read: have been driving me mad) for the past couple of days are 100% not my programming fault, but some internal error of the Nvidia OpenCL implementation. I'm trying to find a workaround and/or thorough internal analysis report to submit to Nvidia.

Rico

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Rico,

You mentioned that someone wanted a way to get notifications of found addresses...

Why not use Pushbullet?

I use it for some other stuff I do and I like it a lot.

Check it out: https://www.pushbullet.com/

Thanks,
Jude

Real-Duke

legendary

Activity: 3486

Merit: 2287

Top Crypto Casino

Quote from: unknownhostname on March 16, 2017, 07:31:10 AM

Ask for work... got blocks [1080203856-1080210383]

Thats me:

Code:

Ask for work... got blocks [1147238848-1147247615] (9193 Mkeys)

So cute compared to yours Wink

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

The current .blf file contains now also P2SH addresses.

As of now, even if we find a privkey to a hash160 belonging to a P2SH address, we will not be able to do anything with it, but as there seem to be very efficient and GPU-friendly implementations how to get access - in time we will have them.

This means the blf file now contains over 14 million addresses we check against, the false positive rate is currently around 10^-23.x - that's nearly 10000 times higher than with our previous BLF files, so I consider this experimental. If it turns out there is too much noise, I will deactivate P2SH search again.

On the positive side, this means our mean search space until a collision is found is only 136.2bits (checking currently against 14582689 addresses). If it turns out all is working, I will adjust the stats and theory section accordingly.

Rico

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: unknownhostname on March 16, 2017, 01:16:43 PM

Quote from: rico666 on March 16, 2017, 11:56:35 AM

edit: 384 MKeys/s = 3 million pages on directory.io per second

Rico

The real speed right now is more than 500Mkeys/s I guess.

Ask for work... got blocks [1091773040-1091779951]

Define "real"

Depends on the averaging time. The stats show a 24h average, The average in the past 1 hour will be higher.
One can estimate this from the gradient af speed growth - we're going straight up with no sign of a slowdown.
So yeah - give it a couple hours and it may show a slowdown at 480+ Mkeys.

512Mkeys = 4 million pages on directory.io per second. Insane (by todays standards).

The log files definitely belong to you, I'd say somewhere between 70 to 80% of the pool capacity is your clients.

For me it's interesting to see how the server scales. No problem there. WIthout changes, I believe the pool could handle 50 GKeys/s as is.

Rico

unknownhostname

member

Activity: 62

Merit: 10

Quote from: rico666 on March 16, 2017, 11:56:35 AM

edit: 384 MKeys/s = 3 million pages on directory.io per second

Rico

The real speed right now is more than 500Mkeys/s I guess.

Ask for work... got blocks [1091773040-1091779951]

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: unknownhostname on March 16, 2017, 07:31:10 AM

Ask for work... got blocks [1080203856-1080210383]

We have officially searched about 11 tn keys in #51 search space.

Code:

[1087617328, 1087624239] <<<                  Unknownhostname

out of 1125 tn keys Wink

so about 1% done

edit: 384 MKeys/s = 3 million pages on directory.io per second

Rico

unknownhostname

member

Activity: 62

Merit: 10

Quote from: rico666 on March 16, 2017, 02:07:37 AM

Exceptionally, I set the pool computational front to 2^50. We will cover the ~370 tn keys after we have found #51.

You will see this on block numbers > 1073770688

Ask for work... got blocks [1080203856-1080210383]

Topic: Large Bitcoin Collider (Collision Finders Pool) - page 30. (Read 193404 times)