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

[jamesg]

Is there a way to view the block history?

Hi Stoppots,
Every member of ABCPool is paid per share. The share price is determined by a formula based on the theoretical expected number of blocks to be found. That reward is independent of when or how much blocks are actually found. As such we do not list the block history, sorry!

It is a little weird that you do not list the blocks found by your pool.

I guess you could be pool hopping with the hashes and no one would know. I would hope this is not the case.

Why exactly do you do this. btcguild.com is also a straight PPS pool but they should the blocks they have found.

Do you not want your miners to be able to figure out your actual income?

[MintCondition]

Is there a way to view the block history?

Hi Stoppots,
Every member of ABCPool is paid per share. The share price is determined by a formula based on the theoretical expected number of blocks to be found. That reward is independent of when or how much blocks are actually found. As such we do not list the block history, sorry!

Why exactly do you do this. btcguild.com is also a straight PPS pool but they should the blocks they have found.

Do you not want your miners to be able to figure out your actual income?

Kudos to BTCGuild for providing their block history to the mining community. And your interest is noted!

Chlorine and I are trying to do the best we can with our limited resources. The next feature to be introduced will most likely be automated password recovery and account reset, since the current manual process is slow and takes quite some effort to support as we keep gaining more and more users.

Of course, as always, you're welcome to suggest any other features you'd like to have on ABCPool! You can reply here or PM me or Chlorine directly. Just don't expect it to be implemented the next day!

[Hotdog453]

Assuming they're not doing anything underhanded (which I don't think they are, since, well, I get paid what I expect), the "allure" of "seeing the blocks you've found" is simply that: something to look at and "brag" about.

Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.

[jamesg]

Assuming they're not doing anything underhanded (which I don't think they are, since, well, I get paid what I expect), the "allure" of "seeing the blocks you've found" is simply that: something to look at and "brag" about.

Kinda cool? Sure. What *MOST* people in a pure PPS pool are looking for? I sort of doubt it.

I think my key point is more about transparency then fun charts and graphs to look at. While abcpool.co is fairly stable, their lack of details regarding the pool doesn't inspire confidence. Nor does their new marketing strategy around their fees.

[stoppots]

With a 4% fee it would be in ABC's interest to atleast offer the same features that can be found at a 0% fee pool.

Features such as email and sms notifications of miner failure, payout, account changes, block being solved. Block stats can be found on nearly all mining pools.

[stoppots]

Transparency needed?/avoided?
https://bitcointalk.org/index.php?topic=51839.msg658974#msg658974

[dirtycat]

Transparency needed?/avoided?
https://bitcointalk.org/index.php?topic=51839.msg658974#msg658974

Interesting theory!

[stoppots]

n

Transparency needed?/avoided?
https://bitcointalk.org/index.php?topic=51839.msg658974#msg658974

Interesting theory!

Came across it today and felt it possibly related to wat was being mention above.

[99Percent]

I am getting sporadic (about 1 out of 15 blocks) errors:

ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok

I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?

[MintCondition]

I am getting sporadic (about 1 out of 15 blocks) errors:

ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok

I am directly connected to high bandwidth internet using DiabloMiner. What could be wrong?

Hi 99Percent,
That error message indicates that the long poll connection was terminated. ABCPool releases those connections on purpose for performance reasons.

The message should occur ca. every 10 minutes, and only when a new block was not found within that time. In those cases it is innocent and you may ignore it. Diablominer will immediately reconnect after the connection has been released.

hope this helps,
MC

[99Percent]

Well, I am getting that error like every minute. I have no idea if its hurting the production if at all. Is there a parameter to pass on to DiabloMiner to adjust this?

[MintCondition]

Well, I am getting that error like every minute. I have no idea if its hurting the production if at all. Is there a parameter to pass on to DiabloMiner to adjust this?

As far as i'm aware there's no parameter to hide the message in Diablominer. Why don't you PM me the log output and I'll take a look at it. Please also include your GPU/worker configuration.

[99Percent]

DiabloMiner output goes like this:

Code:

     
[1/13/12 3:29:20 PM] pool.ABCPool.co accepted block 616 from Cayman (#1)     
[1/13/12 3:29:25 PM] pool.ABCPool.co accepted block 617 from Cayman (#1)     
[1/13/12 3:29:29 PM] pool.ABCPool.co accepted block 618 from Cayman (#1)     
[1/13/12 3:29:31 PM] pool.ABCPool.co accepted block 619 from Cayman (#1)     
[1/13/12 3:29:48 PM] pool.ABCPool.co accepted block 620 from Cayman (#1)     
[1/13/12 3:29:49 PM] pool.ABCPool.co accepted block 621 from Cayman (#1)     
[1/13/12 3:29:52 PM] pool.ABCPool.co accepted block 622 from Cayman (#2)     
[1/13/12 3:29:53 PM] pool.ABCPool.co accepted block 623 from Cayman (#1)     
[1/13/12 3:29:53 PM] pool.ABCPool.co accepted block 624 from Cayman (#1)     
[1/13/12 3:29:55 PM] pool.ABCPool.co accepted block 625 from Cayman (#2)     
[1/13/12 3:29:59 PM] pool.ABCPool.co accepted block 626 from Cayman (#1)     
[1/13/12 3:30:02 PM] pool.ABCPool.co accepted block 627 from Cayman (#1)     
[1/13/12 3:30:05 PM] pool.ABCPool.co accepted block 628 from Cayman (#1)     
[1/13/12 3:30:10 PM] pool.ABCPool.co accepted block 629 from Cayman (#2)     
[1/13/12 3:30:10 PM] pool.ABCPool.co accepted block 630 from Cayman (#2)     
[1/13/12 3:30:19 PM] pool.ABCPool.co accepted block 631 from Cayman (#1)     
[1/13/12 3:30:23 PM] pool.ABCPool.co accepted block 632 from Cayman (#1)     
[1/13/12 3:30:24 PM] pool.ABCPool.co accepted block 633 from Cayman (#2)     
[1/13/12 3:30:25 PM] pool.ABCPool.co accepted block 634 from Cayman (#2)     
[1/13/12 3:30:29 PM] pool.ABCPool.co accepted block 635 from Cayman (#1)     
[1/13/12 3:30:40 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:30:52 PM] pool.ABCPool.co accepted block 636 from Cayman (#2)     
[1/13/12 3:30:52 PM] pool.ABCPool.co accepted block 637 from Cayman (#2)     
[1/13/12 3:30:55 PM] pool.ABCPool.co accepted block 638 from Cayman (#1)     
[1/13/12 3:31:16 PM] pool.ABCPool.co accepted block 639 from Cayman (#1)     
[1/13/12 3:31:29 PM] pool.ABCPool.co accepted block 640 from Cayman (#1)     
[1/13/12 3:31:30 PM] pool.ABCPool.co accepted block 641 from Cayman (#2)     
[1/13/12 3:31:41 PM] pool.ABCPool.co accepted block 642 from Cayman (#2)     
[1/13/12 3:31:44 PM] pool.ABCPool.co accepted block 643 from Cayman (#2)     
[1/13/12 3:31:51 PM] pool.ABCPool.co accepted block 644 from Cayman (#1)     
[1/13/12 3:32:01 PM] pool.ABCPool.co accepted block 645 from Cayman (#2)     
[1/13/12 3:32:05 PM] pool.ABCPool.co accepted block 646 from Cayman (#1)     
[1/13/12 3:32:08 PM] pool.ABCPool.co accepted block 647 from Cayman (#2)     
[1/13/12 3:32:15 PM] pool.ABCPool.co accepted block 648 from Cayman (#2)     
[1/13/12 3:32:16 PM] pool.ABCPool.co accepted block 649 from Cayman (#1)     
[1/13/12 3:32:21 PM] pool.ABCPool.co accepted block 650 from Cayman (#2)     
[1/13/12 3:32:21 PM] pool.ABCPool.co accepted block 651 from Cayman (#1)     
[1/13/12 3:32:22 PM] pool.ABCPool.co accepted block 652 from Cayman (#1)     
[1/13/12 3:32:26 PM] pool.ABCPool.co accepted block 653 from Cayman (#2)     
[1/13/12 3:32:39 PM] pool.ABCPool.co accepted block 654 from Cayman (#2)     
[1/13/12 3:32:40 PM] pool.ABCPool.co accepted block 655 from Cayman (#2)     
[1/13/12 3:32:41 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:32:41 PM] pool.ABCPool.co accepted block 656 from Cayman (#2)     
[1/13/12 3:32:51 PM] pool.ABCPool.co accepted block 657 from Cayman (#2)     
[1/13/12 3:32:52 PM] pool.ABCPool.co accepted block 658 from Cayman (#1)     
[1/13/12 3:33:05 PM] pool.ABCPool.co accepted block 659 from Cayman (#2)     
[1/13/12 3:33:10 PM] pool.ABCPool.co accepted block 660 from Cayman (#1)     
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 661 from Cayman (#1)     
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 662 from Cayman (#1)     
[1/13/12 3:33:18 PM] pool.ABCPool.co accepted block 663 from Cayman (#1)     
[1/13/12 3:33:36 PM] pool.ABCPool.co accepted block 664 from Cayman (#2)     
[1/13/12 3:33:47 PM] pool.ABCPool.co accepted block 665 from Cayman (#2)     
[1/13/12 3:34:03 PM] pool.ABCPool.co accepted block 666 from Cayman (#1)     
[1/13/12 3:34:12 PM] pool.ABCPool.co accepted block 667 from Cayman (#2)     
[1/13/12 3:34:13 PM] pool.ABCPool.co accepted block 668 from Cayman (#1)     
[1/13/12 3:34:13 PM] pool.ABCPool.co accepted block 669 from Cayman (#2)     
[1/13/12 3:34:22 PM] pool.ABCPool.co accepted block 670 from Cayman (#1)     
[1/13/12 3:34:31 PM] pool.ABCPool.co accepted block 671 from Cayman (#1)     

2 x RAdeon HD6950 Linux Mint x64 Debian Edition

[MintCondition]

DiabloMiner output goes like this:

Code:

     
[1/13/12 3:30:40 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok
[1/13/12 3:32:41 PM] ERROR: Cannot connect to pool.ABCPool.co: Bitcoin disconnected during response: 200 ok

I've looked through our source code, and at some point we switched to shorter timeouts for the longpolls. They're now every 120 seconds, which means that that timeout is indeed what diablominer is reporting. Therefore what you see is expected behavior.

While the negative part of this effect will be between 0.00% and 0.02% in wasted GPU cycles (depending on your latency), the positive effect more than compensates that because of the faster longpoll-handling whenever a new block is reported.

[DeepBit]

I've looked through our source code, and at some point we switched to shorter timeouts for the longpolls. They're now every 120 seconds, which means that that timeout is indeed what diablominer is reporting. Therefore what you see is expected behavior

Why would you want to make such short LP timeouts ?
It should be more than 600 seconds (or longer) for best efficiency.

[Inaba]

I believe it's to get their stale count down at the cost of extremely poor efficiency.  Dunno if that debate was ever really resolved to anyones satisfaction circa Bitcoin Pool.

[MintCondition]

Hi miners,
16:00 UTC: Problems at our hosting provider caused ABCPool to be offline for now. Cause is yet unknown, but i'm inclined to guess that the pool will be back online in half an hour.

Sorry for the inconvenience!

UPDATE 17:00 UTC: pool is back online. The bare metal on which the server was hosted gave up. Data is unaffected, all shares have been counted. Please check your miners to make sure they have reconnected.

Thanks for your patience while we resolved this. Happy hashing again everyone!

[despoiler]

Looks like it's offline again.

[jamesg]

Looks like it's offline again.

Confirmed.

[MintCondition]

Looks like it's offline again.

Confirmed.

Looking into it.

UPDATE: It's official, ABCPool is playing with the big boys now: We are being DDOS'ed! We're now going to do some emergency whitelisting on the network perimeter and then figure out a more permanent solution. The pool will most likely be unavailable for a few hours; keep an eye on the forum for updates.