Author

Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 183. (Read 458487 times)

member
Activity: 75
Merit: 10
DiabloMiner users please read this post on the Eligius forum.

Run the new DiabloMiner with Eligius for 3 hours,

From DiabloMiner:
mhash: 87.9/87.2 | accept: 223 | reject: 12

From Artefact2's graph:
3 hour average15 minute average
Hashrate85.10 MH/s62.04 MH/s
Submitted valid shares21413
Submitted 'stale' shares92
Submitted 'unknown work' shares30
Total submitted invalid shares12 (5.31 %)2 (13.33 %)

Setup: Radeon HD 6570 + Ubuntu Natty 11.04 + Catalyst 11.9 + AMD APP SDK 2.5
DiabloMiner commit: ec9e6640dbc83711b10a78881c6db1bd08debaf1
DiabloMiner options: -v 2 -w 128 -f 15
legendary
Activity: 2576
Merit: 1186
DiabloMiner users please read this post on the Eligius forum.
legendary
Activity: 2576
Merit: 1186
This (or any redirection of "stolen" funds) is legally questionable.
But keeping it, or redirecting it back to the thief is ok?
I'm not redirecting it to myself, no.
A pool can make its own rules, no contract is signed between the pool and the miners (or bot net), I dont see the problem. A pool could donate my share to a charity, if I dont like that, I can only switch pools.
... or if you have a botnet, you can DDoS the pool for making rules you don't like, which we already have enough of without asking for more. Sad
hero member
Activity: 518
Merit: 500
This (or any redirection of "stolen" funds) is legally questionable.

But keeping it, or redirecting it back to the thief is ok?
A pool can make its own rules, no contract is signed between the pool and the miners (or bot net), I dont see the problem. A pool could donate my share to a charity, if I dont like that, I can only switch pools.
legendary
Activity: 2576
Merit: 1186
Im curious what you are doing about the botnet?
Nothing I can do.
Anyone think it would be a good idea to keep it mining, but send the payouts to some charity?
This (or any redirection of "stolen" funds) is legally questionable.
hero member
Activity: 518
Merit: 500
Im curious what you are doing about the botnet?
Just blacklisting wont do much, whoever is running it will direct its bots to another pool (assuming those machines are rooted too). Anyone think it would be a good idea to keep it mining, but send the payouts to some charity?
legendary
Activity: 2576
Merit: 1186
More DDoS havoc this morning. For future incident reports, please check our forum.
legendary
Activity: 2576
Merit: 1186
Ports 80 and 8332 are back.
legendary
Activity: 2576
Merit: 1186
New DDoS threat apparently. Ports 80 and 8332 are temporarily down until I have more time to get a better workaround for it.
legendary
Activity: 1428
Merit: 1000
hi,

do you have any plans for merged mining?

if you want to discuss it i opened a thread a here: https://bitcointalksearch.org/topic/thoughts-and-questions-on-btc-pools-and-merged-mining-44546
legendary
Activity: 2576
Merit: 1186
Requesting that the following wallet address be investigated for suspicious activity:
It's already a confirmed botnet. See my reply here.
sr. member
Activity: 252
Merit: 250
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.
legendary
Activity: 2576
Merit: 1186
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.
hero member
Activity: 566
Merit: 500
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!
full member
Activity: 154
Merit: 100
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?
full member
Activity: 125
Merit: 100
ha, thanks, I think I thought the old ones would move =)

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

legendary
Activity: 2576
Merit: 1186
Could you adjust the payout line displayed on the stats graphs to reflect this?  Was nice to see yourself approaching that line =)
Already did Wink
full member
Activity: 125
Merit: 100
Could you adjust the payout line displayed on the stats graphs to reflect this?  Was nice to see yourself approaching that line =)
legendary
Activity: 2576
Merit: 1186
Per poll results, the minimum payout is now 400 TBC (~0.67 BTC).
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
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?
Jump to: