Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 728. (Read 4382786 times)

You read way too much into his answer.  His answer is the correct answer.  It may be too technical, but it is what it is.  What he is trying to say is that because of the way Slush's pool works, your payouts can vary tremendously, especially with a slow miner.

I really didn't see him insulting you in his post, it looked to me like he was legitimately trying to help.

no need to insult me, not everyone is as brilliant as you are and I read that before I posted. And the score changes everything so your answer made no sense to me other than basically saying "shut up you iddiot an just accept what you get" so could someone just explain it to me in english or am I just to assume that stupid people like me should not do this. sheesh...  

It wasn't me and i don't remember such post from you, but it doesn't matter too much in this case:
All pools are using the same version 8.1 right now as there is just no other choice, so all of them get the same (similar) delay and all of them had increased chance for invalid blocks (reason for the global bad luck lately?), so it was not a problem for the Slush's pool only.

Lets just say not much higher than a cpu, not doing for coins right now doing to learn how it works and if it is worth the effort. understanding the beast before I try to feed it. it's around 50. I dont quit during the block and mine the whole time, I've had over a hundred shares one moment ( yes I know very low) and have a very small payout (.000078489)ish and then the next time I have 54 shares and a lower score and end up with .0002345.. only differences are that the first block took longer and I had a huge score and the second block only took like a half hour and a much smaller score.

You need to understand a bit more about how Slush's pool works and you (and many other) get confused with the PPS (pay-per-share) concept. Slush's pool is not a PPS one.

The detailed description of how it works is on the pool's home page - look for a text in big yellow letters that says "How does bitcoin pool work?".

In essence each share gets a "score". The score is highest at the round end, and earlier shares get lower scores. The older the share the lower the score. And that progression is not linear but exponential, so score goes down to almost zero very quickly. From observations I think the cut-off is about an hour - for shares older than an hour you get absolutely no score.

For a slow miner like you that may result in a noticeable variance - sometimes your last share could be just seconds before the end (and will get a high score), sometimes it could be a minute before the end (and will get a lower score). On some very short rounds you may not even have time to submit a single share.

Lets just say not much higher than a cpu, not doing for coins right now doing to learn how it works and if it is worth the effort. understanding the beast before I try to feed it. it's around 50. I dont quit during the block and mine the whole time, I've had over a hundred shares one moment ( yes I know very low) and have a very small payout (.000078489)ish and then the next time I have 54 shares and a lower score and end up with .0002345.. only differences are that the first block took longer and I had a huge score and the second block only took like a half hour and a much smaller score.

I would answered you if I noticed you. Can you tell me your hashrate?

Who told me that I'm an idiot when I say that this might be a problem? Will he apologise?

Round 18133 (block 237220) seems is also invalid ... hopefully that's the last one and Slush's fix will take care of that.

Also when you are sure that this is fixed can you then please look at the stratums. I think there is also something wrong with them.

Stupid question vs 2.0 I take it that the lack of response to my question is a sign of the complete stupidity of the question or I'm being ignored so could someone please let me know were to find the answer thanks

I've detected problems in bitcoind 0.8.1 where high number of transactions in memory pool caused 100% CPU load on the pool server. Because of this, submitting of new blocks were delayed for tens of seconds and caused high invalid rate.

I've detected problems in bitcoind 0.8.1 where high number of transactions in memory pool caused 100% CPU load on the pool server. Because of this, submitting of new blocks were delayed for tens of seconds and caused high invalid rate.

Sipa (the bitcoin developer) implemented fix for this problem (https://github.com/bitcoin/bitcoin/pull/2677) which I just tested and implemented to the pool server. I'm watching the pool closely, but the CPU load dropped from 100% back to 2-3%, so everything looks fine so far...

Stumbled on to where my missing shares may have gone...
Using Windows and GUIMiner to do the mining.

I'm keeping this as brief as possible and ask if you want to converse with me, send me a message from in the system ( click name, compose a message to me and not start some flame war in the thread please )

I've had weird issues with GUIMiner and connecting to Slush's pool using the ' default ' dropdown to connect ( screen blank, system freezes, java suddenly needing to be wiped/re-installed ) so decided to use Slush's mining proxy to ensure some kind of buffer between me and a known Slush's server... Think i may have stumbled on the missing share issue..

first connection to stratum.bitcoin.cz ( the following is pulled lines from the DOS window and yes, full lines )


2013-05-18 08:18:14,015 WARNING proxy mining_proxy.main # Trying to connect to S
tratum pool at stratum.bitcoin.cz:3333

2013-05-18 08:19:23,453 INFO proxy client_service.handle_event # New job f80 for
 prevhash 936c2a37, clean_jobs=True

2013-05-18 08:22:17,125 INFO proxy client_service.handle_event # New job f85 for
 prevhash 043ec4ad, clean_jobs=True

2013-05-18 08:36:07,500 INFO proxy client_service.handle_event # New job f94 for
 prevhash ea0a27c2, clean_jobs=True


all the false, etc, were removed to be easier to read.  The first ' True ' i can't tell if it loaded the work or if it accepted the share as GUIMiner only showed as 2 ' shares ' and nothing for my account page.  However when connecting with the next stratum the edited shows the following.


2013-05-18 08:57:37,296 WARNING proxy mining_proxy.main # Trying to connect to S
tratum pool at stratum2.bitcoin.cz:3333

2013-05-18 09:06:32,437 INFO proxy stratum_listener.submit # [78ms] Share from '
nybbler905.slowworker' accepted, diff 1

and GUIMiner shows 1 block, 2 shares, https://mining.bitcoin.cz/accounts/profile/ shows 1 share...

not using stratum.bitcoin.cz any more.

Sorry if this is a dumb question but I start at the beginning of every round because I leave my miner running 24/7 and my score goes up and up and up and my reward goes down not sure why there is an inverted relationship between the two. I know I have a slow hash rate but I've got new mining equipment coming so I figured start slow to learn the process. 

But where are you buying blade?  Am having 300.000,00 rubles for gear, but not finding available.