[1423GH] ABCPool PPS - Proxy Pool For High & Steady Mining Rewards

[MintCondition]

2,15760376181301e-5 per share here.. 54495 shares, It should be ~ 0.0000276900796620

something is wrong.. with the amount I've been payed for the correct pay I should only have done 45448 shares..  but it's showing 57238 shares

Thanks for pointing this out; we also see this discrepancy in our detailed accounting overview. Due to the high load experienced on our servers the balances have not fully updated. We will adjust any skewed balances once the load issue has been resolved.

[bal3wolf]

NEWS:
Dear members,

As mentioned earlier, certain clients are submitting huge numbers of invalid shares while the incompatibility of certain mining clients remains. As this practically means these clients are DOSsing our servers, we are forced to start blocking their respective users in order to ensure service quality for those that are submitting normally.

1. Users that submit more invalid shares than valid (valid + stale) shares (ie. >50% of total is invalid) will be blocked on IP-basis.
2. You will only be blocked after submitting at least 1000 shares (ie. it is no problem if you start with submitting 42 invalid shares)
3. Blocked users will not be able to continue mining
4. Blocked users can still withdraw their funds.

If you are blocked, you may request an unblock by sending us a PM explaining what steps you have taken to mitigate the problem.

Some tips:
We noticed that especially the cgminer client sends a lot of invalid shares. If you are using this client, switching to another client will probably solve the invalid-shares issue.

If you have any questions, feel free to contact us.

Just a suggestion but anytime you block someone you should pay out their balance also incase they never come back.  

[MintCondition]

Seems like the pool crashed about an hour ago but since has recovered.

Can you comment on the downtimes? They seem to happen every 24-48 hours, but the system recovers in less than an hour. There seems to have been another crash in the last 30 minutes.

This is due to the extreme load non-Phoenix clients are generating.

[MintCondition]

NEWS:
Dear members,

(...)

 we are forced to start blocking their respective users in order to ensure service quality for those that are submitting normally.

(...)

4. Blocked users can still withdraw their funds.

Just a suggestion but anytime you block someone you should pay out their balance also incase they never come back.

Blocked members are only blocked from mining; they may still withdraw their balance whenever they want. They have full access to the website.

[bal3wolf]

NEWS:
Dear members,

(...)

 we are forced to start blocking their respective users in order to ensure service quality for those that are submitting normally.

(...)

4. Blocked users can still withdraw their funds.

Just a suggestion but anytime you block someone you should pay out their balance also incase they never come back.

Blocked members are only blocked from mining; they may still withdraw their balance whenever they want. They have full access to the website.

Ah i see And for me invailds are ok i guess using guiminer and opencl miner aka poclbm on a 5870 and 5970 both extreme clocks get me around 1200-1400mhash  i think my invailds might of cut way back sence i took my 8800gt off the site also and put it on another pool.  If my math is right my invailds are under 1% compared to how many shares iv submited.


Lifetime Valid: 229083 shares
Lifetime Stale: 271 shares
Lifetime Invalid: 654 shares

[chunglam]

Thanks for pointing this out; we also see this discrepancy in our detailed accounting overview. Due to the high load experienced on our servers the balances have not fully updated. We will adjust any skewed balances once the load issue has been resolved.

My personal stats show:
Lifetime Valid: 76234 shares
Lifetime Stale: 165 shares
Lifetime Invalid: 317 shares
Lifetime Earned: 1.31083799 BTC

But according to your FAQ, ignore the Stale and Invalid, I should earn 76234 * 0.00002767 =  2.1094 BTC
So I still have 0.8 BTC not shown in my balance?

[bal3wolf]

Thanks for pointing this out; we also see this discrepancy in our detailed accounting overview. Due to the high load experienced on our servers the balances have not fully updated. We will adjust any skewed balances once the load issue has been resolved.

My personal stats show:
Lifetime Valid: 76234 shares
Lifetime Stale: 165 shares
Lifetime Invalid: 317 shares
Lifetime Earned: 1.31083799 BTC

But according to your FAQ, ignore the Stale and Invalid, I should earn 76234 * 0.00002767 =  2.1094 BTC
So I still have 0.8 BTC not shown in my balance?

I think with the problems they are having the shares are showing more then they should be.  My balance does not match my shares either seems like maybe the shares are 1.5x more then they are suppose to be.  If your problem is same as above they are working on fixing it i think.

[Brian DeLoach]

Current Hashrate:1346.7 GH/s 
Current Workers:891
Registration:CLOSED
BTC.USD: $11.32

Your either expanding at an unbelievable rate or something is jacked up.

[PoulGrym]

Maybe an botnet is a new member. Running through a proxy in to one mine account. That could pretty much kill it. Would be a DDoS effect.

[MintCondition]

NEWS: As you can read above, several users have reported issues over the weekend: Sharecounts that are too high, sharecounts that are not consistent with reported balances,
and highly fluctuating hashrates. We'd like to start by thanking you for bringing them to our attention. Your comments helped us a great deal in resolving.

We have finished our investigation on the issues, and confirmed they arise from the same root cause. Due to the explosive growth of ABCPool in combination with the misbehaving client software, our systems were at full capacity. Our bookkeeping scripts run every minute, and take only a few seconds to complete under normal conditions.

Due to the high load however, execution time grew such that executions started to overlap. This caused submitted shares to be counted multiple times before they could be marked as counted. In fact, it caused a cascade of executions that crippled the system at times.

We have mitigated the issue by making sure that only one instance of the bookkeeping scripts is running at a time.

We will leave the inflated share counts as they are for now; they might be corrected downwards in the future.

In incidental cases, account balances have also increased more than they should have. As a token of gratitude to our early users we will leave these balances as they are. Cheers!

[Wolenber]

In incidental cases, account balances have also increased more than they should have. As a token of gratitude to our early users we will leave these balances as they are. Cheers!

I'm not sure where you guys get the money to run a 0% fee PPS pool and still be generous, but you guys certainly are. It's not much coming from one machine, but I just bumped my donations to 5%. Stay awesome!

[spiccioli]

We have mitigated the issue by making sure that only one instance of the bookkeeping scripts is running at a time.

We will leave the inflated share counts as they are for now; they might be corrected downwards in the future.

In incidental cases, account balances have also increased more than they should have. As a token of gratitude to our early users we will leave these balances as they are. Cheers!

MintCondition,

thanks for your generosity, right now, though, the share count does not increase anymore and my worker is listed as inctive while it is connected and sending shares...

Code:

Workers
Worker Name 	Active	Hashrate (Mhash/s)
spiccioli.m0 	N 	1303

[kripz]

cgminer works on every pool except this... why block it and not fix it?

[MintCondition]

thanks for your generosity, right now, though, the share count does not increase anymore and my worker is listed as inctive while it is connected and sending shares...

Code:

Workers
Worker Name 	Active	Hashrate (Mhash/s)
spiccioli.m0 	N 	1303

Resolved: The lock that prevents multiple executions was not properly released, causing the pipeline to stall. All shares gathered between 03:25 UTC and 10:21 UTC have now been properly accounted for.

[MintCondition]

cgminer works on every pool except this... why block it and not fix it?

Because blocking bad behavior is quite straightforward and something we'll need anyway to protect the pool from attacks. Having said that, we're also planning on making cgminer work with ABCPool, but that's less straightforward.

[spiccioli]

thanks for your generosity, right now, though, the share count does not increase anymore and my worker is listed as inctive while it is connected and sending shares...

Code:

Workers
Worker Name 	Active	Hashrate (Mhash/s)
spiccioli.m0 	N 	1303

Resolved: The lock that prevents multiple executions was not properly released, causing the pipeline to stall. All shares gathered between 03:25 UTC and 10:21 UTC have now been properly accounted for.

Thanks a lot!

spiccioli

[MintCondition]

NEWS: As of a few hours ago we have been gathering statistics on mining client performance. Based on these statistics we have expanded our range of recommended clients:

Supported clients: Phoenix 1.48+, guiminer/poclbm

Clients that are known to be incompatible with ABCPool at this moment: DiabloMiner, Bithopper, cgminer.

You may try clients not listed here, but we can not guarantee good results in that case.

We continue to investigate the reasons some clients do not work well with our pool.

[MintCondition]

NEWS: We are welcoming new miners again!

[MintCondition]

NEWS: 23:40 UTC: ABCPool RPC server is temporarily down for maintenance.

UPDATE 00:15 UTC: RPC server has been restored to service. We introduced changes to the RPC server that should make it more compatible with the original pushpoold. Since most clients play nice with pushpoold, these changes to ABCPool should benefit compatibility with mining clients.

[PoulGrym]

All of a sudden I'm only making Rejected "Stale" shares.. What's going on?