Looks that way... it also seems like I didn't lose any income while the stats were down, although the stats are completely foobar now.

It appears no shares are being counted.  Almost certainly, if you are mining right now, you're not earning anything.

I moved my miners elsewhere for the time being... lost over 2 hours of shares already.

Edit: looks like stats are back up, and shifts have been counting shares.

Something is messed up tho, because the shifts are variable and super short right now

rhaikh: I don't see where I suggested xi 1100 in that post...

Relm9: rejects are hugely dependant on the pool too. Where are you mining?  BIOS is unlikely to affect your reject rate.

I get ~1% rejects at xi 1100, btw.

If it wasn't a multi-pool, someone else would be mining those coins and selling them, so this logic is pretty flawed.

Threw a small bit of BTC at mintpal voting.  Let's get RON on Mintpal!

For reference-design motherboards only.  The Tri-X have a reference mobo.
See my post here: https://bitcointalk.org/index.php?topic=442852.msg5352740#msg5352740

I have been seeing an increase in Duplicate Share rejects over the past while, yes.  But this has been several days, not just today. Duplicate Shares account for the majority of my rejects now it seems.

What is your hashrate?

I never restart my miners unless doing updates or major changes, and do not have any issues.

What kind of retarded troll are you?  This dev team does actually look legit.  I wish they would release source code and actually support the community, but this is a rather unique product, so I can understand the desire to keep it private.

I get a huge kick out of people who complain about multi-pools "damaging" or "destroying" altcoins.  If an altcoin market isn't strong enough to survive a big sell off, or the protocol isn't built well enough to handle difficulty spikes, then that altcoin deserves to get hammered.

That said, AUR didn't bomb because of WafflePool.  It bombed because it's price rise was ridiculous - driven mostly by the largely bullshit coinmarketcap.com valuation that includes the pre-mined (and inactive/non-circulated) coins.

@dloganbill:
- try running everything at the same thread concurrency.
- switch to xintensity instead of intensity to gain a few more KH/s (try xintensity 300 or 400 - adjust higher for a few more kh but potentially higher rejects depending on what pool you are mining with)
- with wafflepool, you can tune (x)intensity pretty high, because they count what would normally be 'stale' shares as valid. e.g. a share that is 1 block outdated is still valid on WP - 1100 seems like a good balance on WP.
- try worksize 256.  I stopped using 512 entirely.
- try gpu-memclock at 1499 instead of 1500 for a few KH benefit on stock
- flash to STILT's BIOS and drop gpu-memclock to 1375 or 1400 and gain a few KH/s in the process
- I always say not to use auto-fan.  Try to find a stable fan % that will keep your cards cool and noise reasonable, and fix it.
- expiry should probably be at least 2 - you will find a lot of shares being considered stale when they aren't if you use 1.  I use 4/8 for scan-time and expiry on wafflepool.
- BAMT/SMOS kinda suck.  Try rolling your own linux install if you want stable linux.  But if you have the cards running stable on Windows, keep with it.  I have never had much luck getting cards/driver stable under windows over a long period.

Stop using intensity... switch to shader multiple threads - xintensity.  Intensity is completely antiquated now.

Only relevant parts quoted - nuff said... fix your cooling situation - VRM and GPU needs to stay cool.

---

That said...

stop using gpu-threads 2... 1 is optimal for 290(X)

Where the heck is that thread-concurrency from?  Try some normal numbers as posted everywhere.

If you are tuning intensity/xintensity, get rid of the shaders line.

Crank your FAN!  Why are you using variable?  Stick it to 90 or 100% if you need to to keep it cooler. temp-* is too low.  cutoff should be 95, overheat something like 97, and target 92.

If you are mining on a pool that has a good reject policy, crank the xintensity up - 1100 is a good value.  Only pool like CM, or solo-mining low-diff coins, will reward a low intensity.

We have a ton of Aurora coin stashed that represents a good portion of our mining effort.  AUR has fallen a been fairly volatile as well, which explains some of the dips.

Once AUR confirms (can take over a day, because blocks are coming in very slowly since AUR has not yet implemented KGW or fast diff variation), we'll likely see a larger then normal payout.

Speculating this strongly on AUR was probably a mistake, however...

@PoolWaffle: you should probably take confirmation time vs market stability into account in the future, before spending so much of our mining time on something like Aurora when it was bubbling.

You are miss-reading that.  N is equivalent to 10 shifts (or at least it was when I talked to PoolWaffle about this a long while ago - should still be).

Furthermore, when a share is found, it pays based on the LAST N shares... future shares are not relevant, so even if N was equal to the number of shares in a shift, a shift with 0 blocks would still earn you something when a block is found during the next shift (because the last N shares would include some shares from the previous shift).

The personal stats earnings log tracks when coins are converted to BTC - there is no equivalent data on the stats page, only the chart and coin totals.

WafflePool uses PPLNS where N represents many shifts.  There is no significance if 0 blocks are found during a shift.

Not sure what you mean about the lack of correlation - my recent blocks found always show up in the pool stats.  As far as 'recent shifts', you have to judge over the entire set of displayed shifts - the portion of hashing power you contribute is the portion you will get paid of any discovered blocks.

You should NEVER install ADL_SDK unless you are compiling your own mining software.  It is for development only, and serves no purpose otherwise.

Ik88: you try downclocking the memory?  kessak doesn't use much memory, whereas scrypt is highly dependent on memory bandwidth.

Do you not see how complicated it would be to implement?  WP has no login system, so how do would you confirm what coins you want to not trade?

WP has better stuff to work on, IMO.  If you want altcoins, go mine them or buy them with BTC.  If you want the best profits, paid in BTC, mine here.

Sounds like a power issue.  How many cards, what motherboard, and what PSU?