If you had actually read every post in this thread like you said, then you would already know that that means that we (the pool) submitted a valid solution for Block 110331 AFTER somebody else had already submitted a valid solution for Block 110331. Therefor, our solution was discarded.

If you don't like Slush's pool, feel free use another or mine solo. If your concerns are valid, others will be doing the same and Slush will adjust to meet his customer's needs or go out of business. I personally don't think your concerns are valid, and will continue to use Slush's pool (for the short time remaining that mining with a single GPU is worthwhile).

Yes, I'm working on it right now. Pretty complex
task, trust me.

And please, don't feed trolls.

What you make per round is irrelevant. The only thing that is relevant is what you make over time. What you make per round is subject to many many different variables that are out of your control. What you make overtime is directly controlled by your hashrate (and difficulty).

bobR, the pool if voluntary. If you don't like it, mine on your own. That way you don't have to worry about concepts of "fairness" or "statistics". If slush sees ways that people are getting paid disproportionately from the work they put in, I'm happy that he changes the rules so that it stops that from happening. If you don't, get out of the pool.

The amount you make each second, each minute, each hour is inconsequential if you mine as slush's pool is designed to be used. If you don't use his product as designed, then you will have a worse experience.

And the cheating problem was those coming in at the beginning and then leaving. Please, read the posts before becoming irate.

Slush explained in extreme depth why the score/share changes were made and how they lead to nearly exactly the same average rewards over time. And even posted charts to prove it.

I was getting tired of typing the long lines of code evertime i wanted to start Poclbm or Rpcminer-cpu, so i made a startup menu for them



Just put Poclbm en rpcminer-cpu in the same directory and define the right directory and username.workername in the Startminers.bat

Save this code as StartMiners.bat
------------------------------------------------------------------------------------------
@echo off
REM 1. Put both programs in one directory
REM 2. Adjust the directory for right program directory at rule 25
REM 3. Adjust the account and password names for both miners at rule 27 to 30
REM 4. Save as startminers.bat
cls
:menu
echo.
echo.
echo *****************************************************************
echo.
echo     Bitcoin CPU and GPU Miners Startmenu
echo.
echo *****************************************************************
echo.
echo.
echo 1 - Start RPCMiner with 1 CPU/Thread  to khash/s, ctrl c to stop
echo.
echo 2 - Start RPCMiner with 2 CPU/Threads to khash/s, ctrl c to stop
echo.
echo 3 - Start PoclbmMiner on GPU to khash/s, ctrl c to stop
echo.
echo 4 - Exit
echo.
echo.
cd "C:\Users\yourpc\Downloads\Bitcoin\rpcminer"
SET /P M=Type 1, 2, 3, or 4 then press enter:
IF %M%== 1 start rpcminer-cpu -url=http://mining.bitcoin.cz:8332 -user=accountname.workername -password=password -statsurl=http://mining.bitcoin.cz/stats/json/ -threads=1
IF %M%== 2 start rpcminer-cpu -url=http://mining.bitcoin.cz:8332 -user=accountname.workername -password=password -statsurl=http://mining.bitcoin.cz/stats/json/ -threads=2
IF %M%== 3 start poclbm --host=mining.bitcoin.cz --port=8332 --user=accountname.workername --pass=password --device=0
IF %M%== 4 GOTO EOF
cls
GOTO MENU

You disconnect from the pool. When your computer starts again, you can reconnect. You take the risk of submitting work at the time when the pool finds a block, thereby reducing your payout via the score system.

Haha

Three servers are up and running. Looks like it helped, invalid shares should be much less often.

No, payouts/block went down significantly when the GHash/Sec being contributed nearly doubled, thus making your tiny portion less significant. But, that alone would still average to the same amount of payout per day or week since we'd be solving more blocks.

But, then the difficulty also adjusted upwards by ~40%. THAT is what has reduced your daily/weekly payout.


You obviously don't understand how this works. This is like playing the lottery. The actions beforehand have ABSOLUTELY NO BEARING on the outcome of the next play. What you contributed early did absolutely nothing to increase the odds of somebody solving a block shortly there after.

And you also obviously know nothing about statistics and variance. Over time, you will average out to exactly the same total daily/weekly payout due to sometimes submitting shares at the beginning and sometimes submitting shares at the end. Look at the graphs that Slush posted when he made this change. They conclusively show that everything works out nearly exactly the same (except for severely punishing cheaters) over time.

Yes, the new scoring somewhat favors faster contributors (who will have a lower ratio of stale shares and a better chance of generating shares closer in time to the pool hitting) - But then, the entire BTC infrastructure favors horsepower over participation, so either take your few pennies a day, or go solo and pray that you ever hit a block within the next few years.  OR, start your own purely-proportional shared pool.  Simple as that.   

Personally, even as a somewhat-penalized low-h/s contributor, I greatly appreciate what Slush has done for us by making it possible to generate any BTC at all without a high-powered GPU to throw at the task.

...said bobR after three rounds of (probably) bad luck.

(But if you mine using CPU, you are probably right. The electricity cost more than you mine. It is just the nice way how to get your first bitcoins to play with - except Bitcoin Faucet).