Large Bitcoin Collider (Collision Finders Pool)

[hodlcoins]

How about people that care a bit 'bout privacy and do not use facebook, nor want google to have too much data, and hence can not sign in to pushbullet?
Is there a way to use it without either google or facebook, or is there an alternative service?
It seems to be a nice service, but why must we sign in with either of the greatest data miners out there?
Why not a simple email, confirm, done?

[1713564594]

1713564594

[1713564594]

1713564594

[1713564594]

1713564594

[rico666]

Updates:

New BLF file (your LBC should auto-update upon startup)
ftp://ftp.cryptoguru.org/LBC/blf/170331-74d3f46939986f415bc2ebf02eeb2d8f.blf.bz2 or the patch
ftp://ftp.cryptoguru.org/LBC/blf/58afd82e681f19b2faf464851aee8541_74d3f46939986f415bc2ebf02eeb2d8f.xd3.bz2

Loaded 14937974 hashes, false positive rate: ~3.523e-24 (1 in ~2.839e+23)

New LBC Appliance:

ftp://ftp.cryptoguru.org/LBC/appliance/

It has a fat 1.6GB size, but it's still the No1 solution for Win-only users.
This version comes on an updated Arch Linux, updated LBC, BLF, installed open-vm-tools and upgraded most CPAN modules.
It's not suitable for GPU clients! -> CPU only


I certainly hope we will get a OpenCL capable Live-Boot for Nvidia (and maybe even AMD) soon. User Icanscript worked on it with very promising results, but I'm not sure how far progress is now.


Rico

[icanscript]

snip

I certainly hope we will get a OpenCL capable Live-Boot for Nvidia (and maybe even AMD) soon. User Icanscript worked on it with very promising results, but I'm not sure how far progress is now.


Rico

I can most likely release it later today / tomorrow. I have just tested mine over the last 8 hours (you should see the results on icantest user). I used screen to run LBC in one and nvidia-smi in the other.

http://imgur.com/a/r2cdz

this is just one photo I took. but my GPU never went over 64c with fan @ ~35%. I am sure I can get more out of it, If you look at the GDDR5 RAM usage also.

there is also a few tweaks I need to make to the nvidia image. just hostname changing and stuff like that.

[rico666]

I can most likely release it later today / tomorrow. I have just tested mine over the last 8 hours (you should see the results on icantest user). I used screen to run LBC in one and nvidia-smi in the other.

http://imgur.com/a/r2cdz

this is just one photo I took. but my GPU never went over 64c with fan @ ~35%. I am sure I can get more out of it, If you look at the GDDR5 RAM usage also.

there is also a few tweaks I need to make to the nvidia image. just hostname changing and stuff like that.

Good to hear. Please before any "release" - send the download-links my way for review and shasum of the files - then release (I'm sure).
You certainly understand that without this I could not recommend anyone using these.
(Also I'm egoistically hoping to get a working AMD OpenCL ISO - did you get that working BTW?) 


Rico

[icanscript]

I can most likely release it later today / tomorrow. I have just tested mine over the last 8 hours (you should see the results on icantest user). I used screen to run LBC in one and nvidia-smi in the other.

http://imgur.com/a/r2cdz

this is just one photo I took. but my GPU never went over 64c with fan @ ~35%. I am sure I can get more out of it, If you look at the GDDR5 RAM usage also.

there is also a few tweaks I need to make to the nvidia image. just hostname changing and stuff like that.

Good to hear. Please before any "release" - send the download-links my way for review and shasum of the files - then release (I'm sure).
You certainly understand that without this I could not recommend anyone using these.
(Also I'm egoistically hoping to get a working AMD OpenCL ISO - did you get that working BTW?) 


Rico

I have mainly been working with the small os customisation and added nvidia, it shouldn't be difficult to install amd, I can hopefully get this to you soon. I just installed pushbullet as above for those who want to use it when released.

Any suggestions on other packages is also welcome if it helps.

[GoldTiger69]

Hi. I started LBC tonight and I got: BLF patch found. (DL-size: 139.96MB)

Everything is working fine, but when I try to stop the LBC by pressing 'e', it doesn't stop.
Is there a new command to stop LBC now?

Thanks in advance.

Edit: NVM, as soon as I posted, it started to stop. (What else is new, huh?)

[rico666]

Hi. I started LBC tonight and I got: BLF patch found. (DL-size: 139.96MB)

Everything is working fine, but when I try to stop the LBC by pressing 'e', it doesn't stop.
Is there a new command to stop LBC now?

Thanks in advance.

Edit: NVM, as soon as I posted, it started to stop. (What else is new, huh?)

Both things are not new. You will see a new BLF patch about once every 14 days. This is to keep the addresses with funds you're searching against updated.

Also, ending the client means that the end-signal sent during the current round is being catched in the next round - which is then ended.

Say you have a -t 10 (10 minutes), time to real end is between 10 and 20 minutes.


Rico

[rico666]

It is with regret that I have to inform you about ceasing pool operation.

User 599ed1ff71f0b9b3dd13e3b9c88ca6ab informed me about a find of 71 BTC and transferring
the funds to his address https://blockchain.info/de/address/14qAqvqQi4Lci3untZcjiDiiYpAuLDwCeS
he has evidently no intention of giving these funds back.

I can confirm that a block he got earlier today contained the privkey and I have the IP addresses
his client connected with. Of course the user id was blacklisted and I will offer full cooperation
with whoever can claim rightful ownership to the funds.

It seems - after all - that critical voices like becoin were right about this risk and I'm sad to
acknowledge their almost Cassandra-like prophecies.

So the pool will go down today 23:59 UTC for good as I simply cannot take the risk of this happening
ever again.


Rico

[arulbero]

April fool's prank?

[CjMapope]

~snip

Rico

April fool's prank?

O, my heart jumped reading that at first, your so mean Rico!      

[Janu$$]

It is with regret that I have to inform you about ceasing pool operation.

User 599ed1ff71f0b9b3dd13e3b9c88ca6ab informed me about a find of 71 BTC and transferring
the funds to his address https://blockchain.info/de/address/14qAqvqQi4Lci3untZcjiDiiYpAuLDwCeS
he has evidently no intention of giving these funds back.

I can confirm that a block he got earlier today contained the privkey and I have the IP addresses
his client connected with. Of course the user id was blacklisted and I will offer full cooperation
with whoever can claim rightful ownership to the funds.

It seems - after all - that critical voices like becoin were right about this risk and I'm sad to
acknowledge their almost Cassandra-like prophecies.

So the pool will go down today 23:59 UTC for good as I simply cannot take the risk of this happening
ever again.


Rico

Well done. Thought also that was a true story.

[rico666]

April fool's prank?

Killjoy! Grinch! Spoilsport! 

I had hoped to cause more stirr - maybe even becoin to show up and hold some lectures.

April, 1st confirmed.


Rico

[Real-Duke]

Hahaha nice one! And an idiot like me have even believed it for a moment and thought oh my god what an assh**le is here with us?  
 

[arulbero]

I'm using aws instances to run LBC client (version CPU only).

I chose 2 instances-type  (https://aws.amazon.com/ec2/instance-types/):

1) m4.4xlarge  (16vCPU)   about 0,13$ per hour (spot instance)
2) m4.16xlarge (64vCPU)   about 0,55$ per hour (spot instance)

generator:  gen-hrdcore-avx2-linux64

1)

Code:

$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 79
model name	: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
stepping	: 1
microcode	: 0xb000014
cpu MHz		: 2300.066
cache size	: 46080 KB
physical id	: 0
siblings	: 16
core id		: 0
cpu cores	: 8
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt
bugs		:
bogomips	: 4600.13
clflush size	: 64
cache_alignment	: 64
address sizes	: 46 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 79
model name	: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
....
processor	: 15
vendor_id	: GenuineIntel
cpu family	: 6
model		: 79
model name	: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz

2)

Code:

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 79
model name      : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
stepping        : 1
...........
processor       : 63
vendor_id       : GenuineIntel
cpu family      : 6
model           : 79
model name      : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz

The problem is the speed:

1) about 6,3Mkeys/s                2) about 12Mkeys/s

obviously I have 2 different config files "lbc.json" , 1) --> "cpus":   16,   2)  --> "cpus":   64.

Why is instance #2  so slow?

[rico666]

AWS m4.4x vs m4.16x

The problem is the speed:

1) about 6,3Mkeys/s                2) about 12Mkeys/s

obviously I have 2 different config files "lbc.json" , 1) --> "cpus":   16,   2)  --> "cpus":   64.

Why is instance #2  so slow?

What about -t ? LBC gets quite a penalty on startup, because it has to load the BLF file, it connects with the FTP server to see if there are updates. AWS machines have quite a bad IO. This startup penalty is even worse with the GPU version, because additionally, it has to compile the OpenCL program.

I was able to get 18 Mkeys (https://lbc.cryptoguru.org/man/admin#system-speed) from a m4.x16 instance with the old client (secp256k1 lib). My guess would be, that the new client with your ECC should be able to give at least 32 times the speed + 20% you see from the benchmark per CPU. So at least over 20 Mkeys/s I guess.

WIth the AWS instances anything smaller than -t 10 does not make sense.

Rico

[arulbero]

I'm using t = 20

Code:

{
    "cpus":   64,
    "id":     "arulbero",
    "secret": "xxxxxxxxxxxxxx",
    "time":   20
}

[unknownhostname]

I'm using t = 20

Code:

{
    "cpus":   64,
    "id":     "arulbero",
    "secret": "xxxxxxxxxxxxxx",
    "time":   20
}

1 answer


AWS is the most shit cloud ever existed and exist

[arulbero]

1 answer

AWS is the most shit cloud ever existed and exist

What do you suggest as alternative?

[rico666]

AWS is the most shit cloud ever existed and exist

What do you suggest as alternative?

Unknownhostname is right. Alternative? Own hardware.

What I observed at AWS:

You get what they call "vCPUs". I assume that stands for "virtual CPUs". In general, it looks like you get only 50% of the CPU power announced - or in other terms - only 50% of the number of CPUs as "real" CPUs. I.e. if you get an instance with 64 vCPUs you can assume you get only the performance that 32 physical CPUs would give you.

Most of the time you can assume that, but sometimes its even worse. While I got regulary 18 Mkeys/s out of the m4.16xlarge, some instances gave me only 16 Mkeys/s - I guess Amazon speculates their customers do not see the difference (which is understandable as most of the customers do not put a 100% CPU load on the machines).

Having said all that: I actually started up a m4.x16xlarge instance after your report and I get

Code:

[root@ip-172-31-4-174 collider]# ./LBC
Ask for work... got blocks [1733262128-1733274415] (12884 Mkeys)
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
oooooooooooooooooo (23.38 Mkeys/s)

with -t 5, so this is expected. You get that performance with any modern 4-core + GPU configuration.

If you get less than these 20+ Mkeys/s, something else is wrong.


Rico

[unknownhostname]

Ask for work... got blocks [1735316448-1735339999] (24696 Mkeys)
ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooooooo (24.48 Mkeys/s)


CPU only