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

[jamesg]

I just tried to initiate a payout from your site and it says my bitcoin address is not valid. This worked in the morning so it looks like you guys just changed something. I have probably received 100 payments to this address.

Please fix this.

Thanks,
gigavps

[1714197262]

1714197262

[MintCondition]

I just tried to initiate a payout from your site and it says my bitcoin address is not valid. This worked in the morning so it looks like you guys just changed something. I have probably received 100 payments to this address.

Please fix this.

Thanks,
gigavps

The payment daemon was being restarted. Try again now and it should succeed.

[jamesg]

I just tried to initiate a payout from your site and it says my bitcoin address is not valid. This worked in the morning so it looks like you guys just changed something. I have probably received 100 payments to this address.

Please fix this.

Thanks,
gigavps

The payment daemon was being restarted. Try again now and it should succeed.

I get the following error:

Insufficient funds.

[Fuzzy]

My miners have been going through very consistent "connection problems", simultaneously, every minute or so. Started at the beginning of the weekend. they were going steady for the month prior. Do I need to change my settings or something?

[MintCondition]

My miners have been going through very consistent "connection problems", simultaneously, every minute or so. Started at the beginning of the weekend. they were going steady for the month prior. Do I need to change my settings or something?

Thanks for your report Fuzzy. With tables only ever growing, lock contention in the database was becoming a source of delays. Luckily some query restructuring has now drastically improved performance again.

Enjoy

[greatwolf]

Can you show the submitted shares for each worker + stales/invalids next to it in parentheses? Also instead of showing connect/disconnect for a worker, it'll be more useful to just show the time of the last submitted share, eg. x seconds ago or y mins ago etc.

A graph of the pool's hash rate under 'Pool stats' would be helpful too.

[shykull]

Auto payout not working?

[Chlorine]

Auto payout not working?

Hi shykull,

No need to worry.

About one month ago, we have reviewed the payment and storage procedures for the pool. We've deployed several changes that make the pool an even less interesting target to hack than before. By making the payment schedule more dynamic, we ensured that our hot wallet is now continuously hovering near 0.

What does this mean for ABC Miners?
* Lower impact in case of a security incident, which means a higher chance of us being able to reimburse you for any losses.
* Payout timing is less predictable. If you're in a rush, request a manual payout.
* Payouts are now processed all day long, not only at 11:00 and 23:00. However, auto-payouts will never be delayed more than 48 hours.
* The payout threshold has been replaced by an autopay toggle.
* Payouts are still nicely rounded amounts. Any amount left on your account balance will be part of a future payment.

Depending on how long ago your last payout was, it should never take more than 24 hours to get your next payout.

regards,
Chlorine

[kano]

...
* Payouts are still nicely rounded amounts. Any amount left on your account balance will be part of a future payment.
...

I can describe the pool gain (from the miner)  for this and the miner loss for this.
Are there any advantages for miners with this at all?

[stiftmaster]

Is it possible to change the number of btc from the auto-payout function?

./stiftmaster

[Chlorine]

...
* Payouts are still nicely rounded amounts. Any amount left on your account balance will be part of a future payment.
...

I can describe the pool gain (from the miner)  for this and the miner loss for this.
Are there any advantages for miners with this at all?

Hi kano,

Neither the pool, nor the miners gain of loose anything using this approach.

We pay out in rounded figures, and the unrounded part remains as balance on your account. That way we keep your wallet a bit cleaner. By paying out using these rounded numbers it is easier to gauge your earnings from your transaction overview in the bitcoin client. If you want to withdraw your full balance you may initiate a manual cash out at any time. Manual cashouts are always for the full remaining balance.

regards,
Chlorine

[Chlorine]

Is it possible to change the number of btc from the auto-payout function?

./stiftmaster

Hi stiftmaster,

With Auto-Payout enabled, we will transfer every 24-48 hours your complete* balance to your payment address. This amount depends on the hashrate of your miners during this period.

*In fact, a small amount of your balance could remain. This will be paid next time (see previous post).

regards,
Chlorine

[kano]

...
* Payouts are still nicely rounded amounts. Any amount left on your account balance will be part of a future payment.
...

I can describe the pool gain (from the miner)  for this and the miner loss for this.
Are there any advantages for miners with this at all?

Hi kano,

Neither the pool, nor the miners gain of loose anything using this approach.

We pay out in rounded figures, and the unrounded part remains as balance on your account. That way we keep your wallet a bit cleaner. By paying out using these rounded numbers it is easier to gauge your earnings from your transaction overview in the bitcoin client. If you want to withdraw your full balance you may initiate a manual cash out at any time. Manual cashouts are always for the full remaining balance.

regards,
Chlorine

Is being misleading the way of ABCPool?

Firstly, any manual payout of the remaining outstanding, if it is less then 0.2 (which it is after a "nicely rounded" payout) gives 0.01 BTC to the pool - i.e. a minimum 5% of the remaining amount (usually more than 5%)
Thus a miner with auto payouts cannot keep their balance at 0 (zero) without initiating a manual payout paying the pool 0.01 BTC every time the pool pays the "nicely rounded" payout but leaves the remainder in the pool wallet.

Anyone with auto payouts who stops mining will ALWAYS have a small balance that they cannot withdraw without also paying a pool fee - again at least 5% of the remaining amount.
These fees go to the pool, not to transaction fees in the block-chain.

Does disabling auto-payout and only ever manually paying out above 0.2BTC always avoid these fees?

If it does, then why are you penalising people with auto-payout who want to keep their balance at 0 BTC?

[MintCondition]

...
* Payouts are still nicely rounded amounts. Any amount left on your account balance will be part of a future payment.
...

I can describe the pool gain (from the miner)  for this and the miner loss for this.
Are there any advantages for miners with this at all?

Neither the pool, nor the miners gain of loose anything using this approach.

We pay out in rounded figures, and the unrounded part remains as balance on your account. That way we keep your wallet a bit cleaner. By paying out using these rounded numbers it is easier to gauge your earnings from your transaction overview in the bitcoin client. If you want to withdraw your full balance you may initiate a manual cash out at any time. Manual cashouts are always for the full remaining balance.

Is being misleading the way of ABCPool?

The note beside the autopayout checkbox and the explanation in the manual cash-out section explain the process fully and tersely. If you have any concrete suggestions for how we can better communicate the way autopay works at ABCPool, we'd be happy to consider them.

[...] any manual payout of the remaining outstanding, if it is less then 0.2 (which it is after a "nicely rounded" payout) gives 0.01 BTC to the pool - i.e. a minimum 5% of the remaining amount (usually more than 5%)

Thus a miner with auto payouts cannot keep their balance at 0 (zero) without initiating a manual payout paying the pool 0.01 BTC every time the pool pays the "nicely rounded" payout but leaves the remainder in the pool wallet.

It's up to you whether to withdraw the remainder, or to wait until it is included in the next round of payouts. Additional manual payouts will of course cause additional fees, as is clearly indicated on the site.

To have your balance touch zero regularly, disable autopay and start doing manual cash-outs.

If it is important for you to keep your balance at zero, turning off your miners is quite effective.

Anyone with auto payouts who stops mining will ALWAYS have a small balance that they cannot withdraw without also paying a pool fee - again at least 5% of the remaining amount.

Your blanket statement is false. It is also unnecessarily alarming: Keep in mind we're talking about a potential, one time fee of BTC 0.01 here.

What is true, is that if you're considering to stop mining at ABCPool, switching off auto-payout may avoid a final manual withdrawal of < BTC 0.2 and the associated BTC 0.01 fee. I invite everyone to take advantage of that.

Does disabling auto-payout and only ever manually paying out above 0.2BTC always avoid these fees?

The 0.01 BTC fee only applies to balances below BTC 0.2.

If it does, then why are you penalising people with auto-payout who want to keep their balance at 0 BTC?

Our autopay approach may not be a perfect fit for everyone. Our autopay approach is also an integral part of our security measures, so it is not likely to change in a major way soon.

I'm sorry to see it causes frustration for you.

[conspirosphere.tk]

Something is very wrong in the last 24 hours:
first I experienced random disconnection of just a few cards of my rigs, now I am seeing a much lower output according the statistics:

Worker Name   Status   Hashrate (Mhash/s)
animal0.5870   Active   97
animal0.5830   Active   65
animal0.58302   Active   69
animal0.5750   Active   49
animal0.57502   Active   57

Note that my miner still says that my 5870 is mining at 410+ Mhs, my 5830s at 300+ Mhs and my 5750s at 170+ Mhs.
Please fix it fast or I'm gone.

edit: Now:
animal0.5870   Disconnected   0
animal0.5830   Disconnected   0
animal0.58302   Disconnected   0
animal0.5750   Disconnected   0
animal0.57502   Disconnected   0

Good bye

[bobers]

i have problem also

[11/04/2012 18:38:42] Result: 56c285a2 accepted
[11/04/2012 18:38:54] Disconnected from server
[11/04/2012 18:39:15] Failed to connect, retrying...
[11/04/2012 18:39:18] Warning: work queue empty, miner is idle
[11/04/2012 18:39:23] Failed to connect, retrying...
[11/04/2012 18:39:33] Failed to connect, retrying...
[11/04/2012 18:39:48] Failed to connect, retrying...
[11/04/2012 18:40:03] Failed to connect, retrying...
[11/04/2012 18:40:18] Failed to connect, retrying...
[[11/04/2012 18:40:33] Failed to connect, retrying...
[11/04/2012 18:40:53] Failed to connect, retrying...
[11/04/2012 18:41:08] Failed to connect, retrying...
[11/04/2012 18:41:23] Failed to connect, retrying...
[11/04/2012 18:41:38] Failed to connect, retrying...

[Chlorine]

ABCPool indeed experiences severe connectivity issues at the moment; we are investigating the cause.

Chlorine.

UPDATE: service level is back to normal.

[bobers]

Don't think so

Code:

[12/04/2012 05:43:29] Result: 836b8a6e rejected
[12/04/2012 05:43:39] Result: 3ff22a92 rejected
[12/04/2012 05:43:44] Disconnected from server
[12/04/2012 05:44:02] Warning: work queue empty, miner is idle
[12/04/2012 05:44:04] Failed to connect, retrying...
[12/04/2012 05:44:23] Failed to connect, retrying...
[12/04/2012 05:44:38] Failed to connect, retrying...
[12/04/2012 05:44:53] Failed to connect, retrying...
[12/04/2012 05:45:08] Failed to connect, retrying...
[0 Khash/sec] [464 Accepted] [15 Rejected] [RPC]Alarm clock

----------------------------------------------------------------------
Primary: pool.ABCPool.co:8332/
 Backup: not specified
----------------------------------------------------------------------
Socket listening...
[12/04/2012 05:45:24] Phoenix v1.7.5 starting...
[12/04/2012 05:45:24] Setting auto kill signal for 180 seconds.
[12/04/2012 05:45:30] Failed to connect, retrying...
[12/04/2012 05:45:50] Failed to connect, retrying...
[12/04/2012 05:46:10] Failed to connect, retrying...
[12/04/2012 05:46:30] Failed to connect, retrying...
[12/04/2012 05:46:50] Failed to connect, retrying...
[12/04/2012 05:47:10] Failed to connect, retrying...
[12/04/2012 05:47:31] Failed to connect, retrying...
[12/04/2012 05:47:51] Failed to connect, retrying...
[12/04/2012 05:48:10] Failed to connect, retrying...
[0 Khash/sec] [0 Accepted] [0 Rejected] [RPC]Alarm clock

----------------------------------------------------------------------
Primary: pool.ABCPool.co:8332/
 Backup: not specified
----------------------------------------------------------------------
Socket listening...
[12/04/2012 05:48:28] Phoenix v1.7.5 starting...
[12/04/2012 05:48:28] Setting auto kill signal for 180 seconds.
[12/04/2012 05:48:28] Failed to connect, retrying...
[12/04/2012 05:48:44] Failed to connect, retrying...
[12/04/2012 05:48:59] Failed to connect, retrying...
[12/04/2012 05:49:14] Failed to connect, retrying...
[12/04/2012 05:49:30] Failed to connect, retrying...
[12/04/2012 05:49:45] Failed to connect, retrying...

[Fuzzy]

Temporary block. You are requesting too much getworks per submitted share. This can happen if you run a CPU miner or a botnet, or in certain cases with Phoenix miner. The ratio is dynamic to keep average pool effiency at a certain level, so you may try mining again later.

Is that a problem on my side, or the pool? Never had this problem before

[joyyen]

my mhs has drop significany