Elacoin dev continues to be incompetent, for the second time... Read on...

[Hazard]

I love that dog.

Anyway, I encourage you all to compile a coin using that insanely high value and see what happens every time you hit a difficulty retarget.

[1713880176]

1713880176

[jomay]

I love that dog.

Anyway, I encourage you all to compile a coin using that insanely high value and see what happens every time you hit a difficulty retarget.

I imagine a value bnProofOfWorkLimit == 0 is not good.

But it will be == 0. It's actually pretty amusing to read the code for >> :

Code:

00416     CBigNum& operator>>=(unsigned int shift)
00417     {
00418         // Note: BN_rshift segfaults on 64-bit if 2^shift is greater than the number
00419         //   if built on ubuntu 9.04 or 9.10, probably depends on version of OpenSSL
00420         CBigNum a = 1;
00421         a <<= shift;
00422         if (BN_cmp(&a, this) > 0)
00423         {
00424             *this = 0;
00425             return *this;
00426         }
00427 
00428         if (!BN_rshift(this, this, shift))
00429             throw bignum_error("CBigNum:operator>>= : BN_rshift failed");
00430         return *this;
00431     }

[WindMaster]

I imagine a value bnProofOfWorkLimit == 0 is not good.

But it will be == 0. It's actually pretty amusing to read the code for >> :

Code:

00416     CBigNum& operator>>=(unsigned int shift)
00417     {
00418         // Note: BN_rshift segfaults on 64-bit if 2^shift is greater than the number
00419         //   if built on ubuntu 9.04 or 9.10, probably depends on version of OpenSSL
00420         CBigNum a = 1;
00421         a <<= shift;
00422         if (BN_cmp(&a, this) > 0)
00423         {
00424             *this = 0;
00425             return *this;
00426         }
00427 
00428         if (!BN_rshift(this, this, shift))
00429             throw bignum_error("CBigNum:operator>>= : BN_rshift failed");
00430         return *this;
00431     }

Core dumped and traced from one of the many elacoind segfaults I'm seeing.  It does indeed segfault in the overloaded >> operator for CBigNum, on Debian 6.0 (so not just old versions of Ubuntu).

[Balthazar]

I wonder to see such target in action  QuantumApocalypse going on

[VelvetLeaf]

We're still waiting for Milkshake's BFL SC photo first.

Link : https://bitcointalk.org/index.php?topic=203881.msg2131011#msg2131011

Nice!, when have you received it?

Today. Nice surprise, didn't even pay for it!

You probably do realize this account is the troll account from another account here. I think it was created in honor of smoothie.

That is correct, but I do have a 30GH/s ASIC from BFL mining, and I received it as a freebie.

No kill-a-watt (they measure power consumption right?), I'll post pics later for the blog post when I've written it up and measured long term performance / stability.

I don't mind the power consumption, BFL is covering electricity bills too.

[AlternativeCypt]

We're still waiting for Milkshake's BFL SC photo first.

https://i.imgur.com/lLS8vVN.png

Nice!, when have you received it?

Today. Nice surprise, didn't even pay for it!

You probably do realize this account is the troll account from another account here. I think it was created in honor of smoothie.

That is correct, but I do have a 30GH/s ASIC from BFL mining, and I received it as a freebie.

No kill-a-watt (they measure power consumption right?), I'll post pics later for the blog post when I've written it up and measured long term performance / stability.

I don't mind the power consumption, BFL is covering electricity bills too.

LMFAO

[Impaler]

Yes, and by right-shifting by 1000000 bits, he's setting the value of bnProofOfWorkLimit to 0.

Correct.

Anybody using >> 10000 just doesn't know what he's doing.

Also you can see from getinfo that this coin started at 0 difficulty.

Have too agree with ya their, that piece of code makes me cringe and I would not run ANYTHING that came from that programmers hand.