[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[Luke-Jr]

Please vote on whether to raise the minimum payout

[1715284533]

1715284533

[1715284533]

1715284533

[1715284533]

1715284533

[dadittox]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

[DiabloD3]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

I use eligius almost exclusively, rollntime works fine.

Edit: Goddamnit luke, you broke it!

[Luke-Jr]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...

[DiabloD3]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...

That bug never existed and I repeatedly confirmed that the bug is in your pool.

If this is your stance, I might have to end up adding code to detect eligius and force reenable it.

[strictlyfocused]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...

That bug never existed and I repeatedly confirmed that the bug is in your pool.

If this is your stance, I might have to end up adding code to detect eligius and force reenable it.

http://imgur.com/tCp90.gif

[Luke-Jr]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...

That bug never existed and I repeatedly confirmed that the bug is in your pool.

The only thing you confirmed was that your logs were reporting things sanely. The actual on-the-wire packets confirmed you were sending me dead shares.

If this is your stance, I might have to end up adding code to detect eligius and force reenable it.

If Eligius doesn't tell you it's allowed, it isn't: forcefully rolled shares will be rejected outright.

[DiabloD3]

Latest DiabloMiner sends X-Mining-Extensions header as "longpoll rollntime switchto". This is not recognized by eligius and rollntime is disabled for this miner.

Last I checked, DiabloMiner had bugs in its rollntime implementation, and Diablo-D3 stubbornly denied they existed (thus refusing to fix them), so I blacklisted it from using it. Specifically, with rollntime enabled, DiabloMiner is somehow confusing its work and when it expires, and sending shares against work older than 2 minutes, even after it has received new work. If Diablo-D3 has fixed this, and someone is willing to do some real-time testing to confirm it (on IRC), I'd be glad to remove it from the blacklist...

That bug never existed and I repeatedly confirmed that the bug is in your pool.

The only thing you confirmed was that your logs were reporting things sanely. The actual on-the-wire packets confirmed you were sending me dead shares.

If this is your stance, I might have to end up adding code to detect eligius and force reenable it.

If Eligius doesn't tell you it's allowed, it isn't: forcefully rolled shares will be rejected outright.

You depend on UA snooping. Just sayin.

And no, the only thing you confirmed is that miners still have a very low rate of stale shares. Are you going to start blacklisting other miners because they produce stale shares too?

[Luke-Jr]

Per poll results, the minimum payout is now 400 TBC (~0.67 BTC).

[echris1]

Could you adjust the payout line displayed on the stats graphs to reflect this?  Was nice to see yourself approaching that line =)

[Luke-Jr]

Could you adjust the payout line displayed on the stats graphs to reflect this?  Was nice to see yourself approaching that line =)

Already did

[echris1]

ha, thanks, I think I thought the old ones would move =)

By far my favorite pool, keep up the good work.

[Fakeman]

Anyone else get an "Unknown Address!" page when trying to check their stats? My address is gone from the payout queue page too.

BTW, is this still a problem? Can you PM me your address/link?

Not any more, do you still want the link?

[runlinux]

has there been issues with the pool? been getting a lot of stales, unknown work, unkown user stales the past 24 hours. 2.17% Stales... ewww!

[Luke-Jr]

has there been issues with the pool? been getting a lot of stales, unknown work, unkown user stales the past 24 hours. 2.17% Stales... ewww!

Someone apparently decided to exploit a bug in bitcoind to crash our hub node multiple times over the past few days, resulting in watchdogs restarting the pool while I wasn't there to look into it myself. I tracked down and fixed the bug, and it seems to be stable since, but there seems to still be another attack vector being used. I am looking into this one as well, and hope to have it solved ASAP. I recommend joining IRC for the latest updates on these DoS attacks.

[MrWizard]

I'm cross-posting this for a newbie.  Requesting that the following wallet address be investigated for suspicious activity:

I get on process explorer, once in a while, even after I kill it, almost 100% CPU time by an iexplore.exe process. Process explorer identifies it (fully) as ""C:\Program Files (x86)\Internet Explorer\bin\iexplore.exe" -a 1 -o http://mining.eligius.st:80 -u 1JLE6hkA8QbD64G8ZknbH6HT9orWQ7dKB3 -p pass"

I will not pretend I know what bitcoin is exactly. I just learned a brief about it 10 minutes ago. I have never used or tried to use bitcoin before finding out this process.

Please help to identify what is going on or at least remove it from re-running itself. Apparently my antiviruses don't find it.

[Luke-Jr]

Requesting that the following wallet address be investigated for suspicious activity:

It's already a confirmed botnet. See my reply here.

[flower1024]

hi,

do you have any plans for merged mining?

if you want to discuss it i opened a thread a here: https://bitcointalk.org/index.php?topic=44546.0

[Luke-Jr]

New DDoS threat apparently. Ports 80 and 8332 are temporarily down until I have more time to get a better workaround for it.

[Luke-Jr]

Ports 80 and 8332 are back.