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

Is it me or do I have the feeling we lose money on electricity in the end because of those invalid/stale shares?

I will continue to mine anyway because I just love participating in this project of a genius.

There are other threads on this site talking about mybitcoin.com not currently working properly.

The pool is just a subset of the total mining power of the bitcoin network, so those who use a pool which throws away a lot of calculations will on average get a lower payout than they would if they mined on their own.

Having a different problem, but also related to payout. I received payout confirmation 9 hours ago. The amount has been deducted from the confirmed rewards section of mining.bitcoin.cz, but has not appeared in my wallet. Wallet information was correct. This wallet is hosted on mybitcoin.com - does anybody know of any problems with them and transactions? The last 3 payouts to this address went without problem and showed almost instantly.

Same here.

My wallet address is ok and I have accumulated 3.82 (Unconfirmed) Bitcoins with my threshold set at 1.0 and my wallet is empty. Is this normal?

What difference does unconfirmed and confirmed blocks have?

Oke, everybody get a fair share of solved blocks, and now everybody get a fair/unfair share of random increased invalid/stales so the question is do we lose money in the end or does it remains the same payout as before, due to the increase of invalid/stales. i don't know how the poolserver does this math or does this math at all, but generaly spoken if every body get a fair share of the good and the bad, the total must be the same percentage payout overall, but thats my guess. I dont know how the source code is written.

Check your wallet address.

Everybody gets their fair share of the solved blocks. However, the total performance of the pool is lower than it could have been, so the daily payout to everybody who participates in it is less.

I successfully received a payout 11 hours ago.

Edit: and just received another payout.

my threshold is set at 1.0 bitcoins, but 5.82 bitcoins have accumulated um my confirmed rewards. is anyone else having this problem. 

For the time being, I have switched my GPUs to solo mining to remove load from the pool.
My CPUs are still mining in the pool, but only for the 7 hours each day when the electricity is at cheap rate!

Yes, there are really performance peaks time to time. Before few minutes, there were >2000rq/s for no reason. I don't know if those floods are from regular users or if somebody is trying to overload server. For sure, I'll add next server tomorrow.

I thought about that too, but I tried correlating them to block durations and block solve times and found that I was getting several even while in the middle of very long blocks.

i guess that everyone is getting a lot of invalids, so in the end it doesn't affect your total score/payout, only a lot of bogus calculations for your cpu/gpu and useless network traffic

with 60+ Ghash/s, blocks are solved crazy fast.... maybe they're just stale? (ie from old blocks)

I've the same problem:

18/02/2011 13:06, b3837db9, invalid or stale
18/02/2011 13:07, 441d0323, invalid or stale
18/02/2011 13:07, 5d04acdd, accepted
18/02/2011 13:07, e2c1501e, invalid or stale
18/02/2011 13:08, bdd62415, accepted
18/02/2011 13:08, 4d6bf517, accepted
18/02/2011 13:08, d849df6e, accepted
18/02/2011 13:08, 6628a7e7, invalid or stale
18/02/2011 13:08, 82801f09, invalid or stale
18/02/2011 13:09, 274e628b, accepted
18/02/2011 13:09, 26caf674, accepted
18/02/2011 13:09, 416cbb8c, accepted
18/02/2011 13:10, a31fe188, accepted
18/02/2011 13:10, c892d32a, accepted
18/02/2011 13:10, 75749fc3, accepted
18/02/2011 13:10, a5ebeb07, invalid or stale
18/02/2011 13:11, b3357d20, invalid or stale
18/02/2011 13:11, 4dfc0d53, accepted
18/02/2011 13:11, 6e7c9400, accepted
18/02/2011 13:11, 1eb8a677, accepted
18/02/2011 13:11, b9cd3067, accepted
18/02/2011 13:11, 3b96ecf4, accepted
18/02/2011 13:11, dacc518a, accepted
18/02/2011 13:12, ccc833f6, accepted
18/02/2011 13:12, e5d28436, accepted
18/02/2011 13:13, 21e8b6cb, accepted
18/02/2011 13:13, 0b57bafc, accepted
18/02/2011 13:13, 2298cb13, accepted
18/02/2011 13:13, 1d3acb81, invalid or stale
18/02/2011 13:13, ba3101e4, accepted
18/02/2011 13:13, 7f5450e1, accepted
18/02/2011 13:13, 60dc1f1a, accepted
18/02/2011 13:13, ba03087a, accepted
18/02/2011 13:14, c5ef88d0, accepted
18/02/2011 13:14, c307c120, accepted
18/02/2011 13:14, f83d0686, accepted
18/02/2011 13:14, 0af3a69a, accepted
18/02/2011 13:14, 97a27da3, accepted
18/02/2011 13:14, 5fc07786, accepted
18/02/2011 13:15, 3c8aea3e, accepted
18/02/2011 13:15, 1f9b67c4, accepted
18/02/2011 13:15, 9388d69d, accepted
320584 khash/s


on average 15-20% of invalid or stale, dunno why.

Since yesterday I started getting unusually many invalid or stale responses, some times up to 4 in a row. It happens on two different computers. Is there any known cause for this?

Any way we can tell our RPC clients to hit your servers less often (personally, I've set the "update period" to ten seconds from the default of four, but I think that only affects what I see, not network traffic)?  Or do you get that many actual shares returned each second?

Or, you could just double the difficulty of each share and thereby halve your load, rinse-wash-repeat as necessary (while that would make it tougher for the low h/s miners like me, I would say the pool integrity comes first)...

I have a couple of questions:

1. with 8Mhash/sec GPU and round trip times about 400ms, how many miners do I need to set up not to lose shares?

2. I'm using poclbm_py2exe_20110204 and I don't see when the current block ends.
Is it possible to receive a message from the server, so I'd know where it's safe to turn it off, without the necessity of watching the web page or bitcoin client and tracking down block numbers ?

Because of huge rise of traffic every day, I decided to close pool registrations right now. For example, over this night the number of requests rise from 300 getwork/s to more than 500 getwork/s. I simply cannot add new server every day. I also need more time to finish my work on push based protocol and currently the maintenance of rising load consume too much time.

Once the pushwork stack will be ready, I open registration back again.