Topic: [1423GH] ABCPool PPS - Proxy Pool For High & Steady Mining Rewards - page 6. (Read 151781 times)
February 04, 2013, 08:10:29 AM
I confirm, auto-payout is not working and I can't manually request the payout because "your balance has exceeded the amount for manual payout".
January 23, 2013, 05:54:58 AM
Erm auto payout not working I think. 
Plz look into it
Thanks
Plz look into it
Thanks
January 22, 2013, 12:18:13 PM
Are autopayouts not working?
January 08, 2013, 08:18:50 AM
Hi,
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Hi HC,
please note the E-5 part. Your account is empty (to be precise: the remaining amount is 0.00009586 BTC)
kind regards,
Chlorine
Then it's not 'empty' is it?
I'm well aware of what scientific notation is........
January 08, 2013, 07:53:18 AM
Hi,
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Hi HC,
please note the E-5 part. Your account is empty (to be precise: the remaining amount is 0.00009586 BTC)
kind regards,
Chlorine
Then it's not 'empty' is it?
I'm well aware of what scientific notation is........
December 31, 2012, 05:28:54 AM
Hi,
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Hi HC,
please note the E-5 part. Your account is empty (to be precise: the remaining amount is 0.00009586 BTC)
kind regards,
Chlorine
December 30, 2012, 07:08:00 PM
Hi,
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
Just spotted this:
In the account details on the stats tab....
Balance at risk: 9.586E-5 BTC
I requested a payout of all the bit-coins in the account.
HC
December 14, 2012, 08:13:24 PM
Hi,
Not criticizing, just trying to find a GOOD pool before my ASICs are delivered.
Trying to do it in the most logical way, by running a reasonably slow miner and taking a look at the results.
It's always good to do some research, and to ask some critical questions.Not criticizing, just trying to find a GOOD pool before my ASICs are delivered.
Trying to do it in the most logical way, by running a reasonably slow miner and taking a look at the results.
Cheers
December 14, 2012, 08:00:51 PM
Hi,
Not criticizing, just trying to find a GOOD pool before my ASICs are delivered.
Trying to do it in the most logical way, by running a reasonably slow miner and taking a look at the results.
Not criticizing, just trying to find a GOOD pool before my ASICs are delivered.
Trying to do it in the most logical way, by running a reasonably slow miner and taking a look at the results.
December 14, 2012, 08:17:00 AM
Quote from: hardcore-fs
from https://www.btcguild.com/variable_difficulty.php
Quote
When mining at a higher difficulty, when your shares are accepted, they will show up on your 'My Account'/'Earnings History' stats as multiple shares. This is because PPS rates are set at Difficulty of 1+ shares. When submitting a Difficulty 8+ share, each submission will show up as 8 shares on your statistics.
Rest assured btcguild is not paying out 8 times what they earn themselves, they would go bankrupt before you can blink. Their way of explaining it is somewhat ambiguous, but what they seem to mean is:
* When they give a diff 8 work packet to you, they will add 8 shares to your stats if you reply with a share that indeed has a difficulty of 8 or more.
* When they give a diff 1 work packet to you, they will add 1 shares to your stats if you reply with a share that indeed has a difficulty of 1 or more.
* And therefore: When they give an 1+ work packet to you, they will add 1 shares to your stats, even if you reply with a share of difficulty 8 or more.
In any case, a pool (PPS, DGM, Proportional, any pool actually) asks for a share that has at least a certain quality (ie diff 1, diff 8, diff n, ...). If it meets the specs, it gets counted according to the specs, and if it doesn't, it won't. If it does more than meet the spec, it will still only get counted at the level of the specs. There's one rarely seen exception (usually promotional): certain pools reward block-finding-shares extra, taking that reward from the non-block-finding shares, but that just makes their rewards a little bit more like solo mining: normal shares get less AND variability increases.
December 13, 2012, 11:05:44 PM
Code:
[quote author=hardcore-fs link=topic=33586.msg1396989#msg1396989 date=1355386393]
[...] why do they only kick up during a block change, is the loading different?
[/quote]
After a block change a lot of work is suddenly needed, as all long polls trigger at once. Immediately after that, every mining client will request another work item to fill its cache. This means that a load equivalent of 20 seconds is now concentrated in one moment. We are working on a big overhaul of the pool software to make this more efficient.
[quote]
Also just one more question:
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
[...] why do they only kick up during a block change, is the loading different?
[/quote]
After a block change a lot of work is suddenly needed, as all long polls trigger at once. Immediately after that, every mining client will request another work item to fill its cache. This means that a load equivalent of 20 seconds is now concentrated in one moment. We are working on a big overhaul of the pool software to make this more efficient.
[quote]
Also just one more question:
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
how are the previous two "paid" are they counted as
2 shares, or as 18 ?
Since the "difficulty 17" takes way longer to solve.
Usually you will generate a share with a difficulty higher than the diff requested. Pools could pay you more for such shares, but that goes against the very idea of pooled mining. With pooled mining the goal is to reward everyone for their efforts, not for their individual results. By paying a fixed amount per share (PPS), regardless of achieved difficulty, miners can be sure to receive the most stable payouts possible. That's because calculating a share of difficulty >1 takes a certain amount of effort, regardless of the actual difficulty that's achieved.
To put it more intuitively with an extreme example: You wouldn't expect 25BTC reward for a block solving share, because it would mean there is no (or significantly less) coin left to divide among the less powerful shares, and the reward scheme will start to look a lot like solo mining.
Regards,
MC
[/quote]
from https://www.btcguild.com/variable_difficulty.php
Quote
When mining at a higher difficulty, when your shares are accepted, they will show up on your 'My Account'/'Earnings History' stats as multiple shares. This is because PPS rates are set at Difficulty of 1+ shares. When submitting a Difficulty 8+ share, each submission will show up as 8 shares on your statistics.
December 13, 2012, 05:25:35 AM
Code:
[quote author=hardcore-fs link=topic=33586.msg1396989#msg1396989 date=1355386393]
[...] why do they only kick up during a block change, is the loading different?
[/quote]
After a block change a lot of work is suddenly needed, as all long polls trigger at once. Immediately after that, every mining client will request another work item to fill its cache. This means that a load equivalent of 20 seconds is now concentrated in one moment. We are working on a big overhaul of the pool software to make this more efficient.
[quote]
Also just one more question:
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
[...] why do they only kick up during a block change, is the loading different?
[/quote]
After a block change a lot of work is suddenly needed, as all long polls trigger at once. Immediately after that, every mining client will request another work item to fill its cache. This means that a load equivalent of 20 seconds is now concentrated in one moment. We are working on a big overhaul of the pool software to make this more efficient.
[quote]
Also just one more question:
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
how are the previous two "paid" are they counted as
2 shares, or as 18 ?
Since the "difficulty 17" takes way longer to solve.
[/quote]
The payout for a share depends on the difficulty requested by the pool, and currently ABCPool always requests difficulty 1 (though this is about to change).
Usually you will generate a share with a difficulty higher than the diff requested. Pools could pay you more for such shares, but that goes against the very idea of pooled mining. With pooled mining the goal is to reward everyone for their efforts, not for their individual results. By paying a fixed amount per share (PPS), regardless of achieved difficulty, miners can be sure to receive the most stable payouts possible. That's because calculating a share of difficulty >1 takes a certain amount of effort, regardless of the actual difficulty that's achieved.
To put it more intuitively with an extreme example: You wouldn't expect 25BTC reward for a block solving share, because it would mean there is no (or significantly less) coin left to divide among the less powerful shares, and the reward scheme will start to look a lot like solo mining.
Regards,
MC
December 13, 2012, 03:13:13 AM
Hi Hardcore-fs,
At the moment you took these logs, the system ran in degraded mode as one of the servers had crashed yesterday; that explains an elevated error level. All servers are up again currently.
More to the point of your post, we return a 'submission failure' for stale shares. Even though that makes it seem they are not paid, they do get counted on your stats page. We return a failure code to allow people to tweak their mining configuration based on these shares, in the same way they would at other pools.
So in short: your miner reports stale shares as failures, but we still pay them, as long as they arrive within a certain time of us finishing triggering all longpollers.
Hope this helps,
MC
At the moment you took these logs, the system ran in degraded mode as one of the servers had crashed yesterday; that explains an elevated error level. All servers are up again currently.
More to the point of your post, we return a 'submission failure' for stale shares. Even though that makes it seem they are not paid, they do get counted on your stats page. We return a failure code to allow people to tweak their mining configuration based on these shares, in the same way they would at other pools.
So in short: your miner reports stale shares as failures, but we still pay them, as long as they arrive within a certain time of us finishing triggering all longpollers.
Hope this helps,
MC
I see your servers run in a "degraded" state quite frequently, but why do they only kick up during a block change, is the loading different?
Also just one more question:
Code:
2012-12-13 12:21:53.775 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001b469e1a1996711610cd0c499f8c73bb0a17aa68545cf90b3000003ae0000000057c368a727cac5e12bef17d7a7e71b16331fa99565f67289644032dce18f797250c957a51a04fa62
2012-12-13 12:22:05.550 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001b469e1a1996711610cd0c499f8c73bb0a17aa68545cf90b3000003ae0000000057c368a727cac5e12bef17d7a7e71b16331fa99565f67289644032dce18f797250c957a51a04fa62:80773f8c
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:06.525 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001b469e1a1996711610cd0c499f8c73bb0a17aa68545cf90b3000003ae0000000057c368a727cac5e12bef17d7a7e71b16331fa99565f67289644032dce18f797250c957a51a04fa62:d31bdb97
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
2012-12-13 12:22:05.550 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001b469e1a1996711610cd0c499f8c73bb0a17aa68545cf90b3000003ae0000000057c368a727cac5e12bef17d7a7e71b16331fa99565f67289644032dce18f797250c957a51a04fa62:80773f8c
2012-12-13 12:22:06.047 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 80773f8c (difficulty 17.05233)
2012-12-13 12:22:06.525 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001b469e1a1996711610cd0c499f8c73bb0a17aa68545cf90b3000003ae0000000057c368a727cac5e12bef17d7a7e71b16331fa99565f67289644032dce18f797250c957a51a04fa62:d31bdb97
2012-12-13 12:22:07.021 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share d31bdb97 (difficulty 1.29580)
how are the previous two "paid" are they counted as
2 shares, or as 18 ?
Since the "difficulty 17" takes way longer to solve.
December 12, 2012, 06:56:16 PM
Hi Hardcore-fs,
At the moment you took these logs, the system ran in degraded mode as one of the servers had crashed yesterday; that explains an elevated error level. All servers are up again currently.
More to the point of your post, we return a 'submission failure' for stale shares. Even though that makes it seem they are not paid, they do get counted on your stats page. We return a failure code to allow people to tweak their mining configuration based on these shares, in the same way they would at other pools.
So in short: your miner reports stale shares as failures, but we still pay them, as long as they arrive within a certain time of us finishing triggering all longpollers.
Hope this helps,
MC
At the moment you took these logs, the system ran in degraded mode as one of the servers had crashed yesterday; that explains an elevated error level. All servers are up again currently.
More to the point of your post, we return a 'submission failure' for stale shares. Even though that makes it seem they are not paid, they do get counted on your stats page. We return a failure code to allow people to tweak their mining configuration based on these shares, in the same way they would at other pools.
So in short: your miner reports stale shares as failures, but we still pay them, as long as they arrive within a certain time of us finishing triggering all longpollers.
Hope this helps,
MC
December 12, 2012, 05:19:16 PM
What your forum states
"Should it be your problem if the pool does not notify your miner of a new block? We don't think so. That's why we pay you for every share, even stale shares*!"
what happens in reality......
Code:
2012-12-13 06:12:24.209 [300] Dummy blockchain: New block detected
2012-12-13 06:12:24.230 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b400000000a6f8331ef15871e6d206e12266664bb94987a11636d0326ea8054141a7ab7d3350c901331a04fa62
2012-12-13 06:12:29.747 [200] abcpool_XUPV5-LX110T: Error while fetching job: Traceback (most recent call last):
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 257, in fetcher
jobs = self._build_jobs(response, data, epoch, now, "getwork")
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 375, in _build_jobs
decoded = json.loads(decoded)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2012-12-13 06:12:39.491 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b400000000a6f8331ef15871e6d206e12266664bb94987a11636d0326ea8054141a7ab7d3350c901331a04fa62:9b5adbb5
2012-12-13 06:12:40.551 [300] Dummy blockchain: New block detected
2012-12-13 06:12:40.700 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b4000000004f66d8ac64c3b99851da99ce13cfe465042018ca2e205e6a507f1a253de43d3a50c9014a1a04fa62
2012-12-13 06:12:46.698 [200] XUPV5-LX110T_2: abcpool_XUPV5-LX110T rejected share 9b5adbb5 (difficulty 1.95456): Unknown reason
2012-12-13 06:12:24.230 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b400000000a6f8331ef15871e6d206e12266664bb94987a11636d0326ea8054141a7ab7d3350c901331a04fa62
2012-12-13 06:12:29.747 [200] abcpool_XUPV5-LX110T: Error while fetching job: Traceback (most recent call last):
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 257, in fetcher
jobs = self._build_jobs(response, data, epoch, now, "getwork")
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 375, in _build_jobs
decoded = json.loads(decoded)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2012-12-13 06:12:39.491 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b400000000a6f8331ef15871e6d206e12266664bb94987a11636d0326ea8054141a7ab7d3350c901331a04fa62:9b5adbb5
2012-12-13 06:12:40.551 [300] Dummy blockchain: New block detected
2012-12-13 06:12:40.700 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001254d2863c39bd8c1ef392a9dbd0effa38cf14fae68ed016a000001b4000000004f66d8ac64c3b99851da99ce13cfe465042018ca2e205e6a507f1a253de43d3a50c9014a1a04fa62
2012-12-13 06:12:46.698 [200] XUPV5-LX110T_2: abcpool_XUPV5-LX110T rejected share 9b5adbb5 (difficulty 1.95456): Unknown reason
funny how this only happens on a newblock, to bounce stale shares:
Code:
2012-12-13 06:15:38.906 [300] Dummy blockchain: New block detected
2012-12-13 06:15:38.929 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001ac04af54217785c2e1edce0fa71c870be170d56f0d583f3d0000034200000000e4a293a8aa19c203646c55d2029627808df7f7d2720ab170ec516c9f9e0cbfa950c902101a04fa62
2012-12-13 06:15:44.541 [200] abcpool_XUPV5-LX110T: Error while fetching job: Traceback (most recent call last):
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 257, in fetcher
jobs = self._build_jobs(response, data, epoch, now, "getwork")
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 375, in _build_jobs
decoded = json.loads(decoded)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2012-12-13 06:15:55.398 [400] XUPV5-LX110T_2: Mining BTCGuild_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000000036f50f37c17c17e1bd2ffb3ed5d18424fab23a54a4f96d0a067213b1cd50ee50c9020a1a04fa62
2012-12-13 06:15:38.929 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:00000001ac04af54217785c2e1edce0fa71c870be170d56f0d583f3d0000034200000000e4a293a8aa19c203646c55d2029627808df7f7d2720ab170ec516c9f9e0cbfa950c902101a04fa62
2012-12-13 06:15:44.541 [200] abcpool_XUPV5-LX110T: Error while fetching job: Traceback (most recent call last):
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 257, in fetcher
jobs = self._build_jobs(response, data, epoch, now, "getwork")
File "/Users/stevebirtles/Desktop/Modular-Python-Bitcoin-Miner/modules/theseven/bcjsonrpc/bcjsonrpcworksource.py", line 375, in _build_jobs
decoded = json.loads(decoded)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
2012-12-13 06:15:55.398 [400] XUPV5-LX110T_2: Mining BTCGuild_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000000036f50f37c17c17e1bd2ffb3ed5d18424fab23a54a4f96d0a067213b1cd50ee50c9020a1a04fa62
and when there is not a "new block"
Code:
2012-12-13 06:16:28.329 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62
2012-12-13 06:16:28.587 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:46efe802
2012-12-13 06:16:29.079 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 46efe802 (difficulty 2.40814)
2012-12-13 06:16:30.521 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:aa93f019
2012-12-13 06:16:30.728 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:1422781c
2012-12-13 06:16:31.014 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share aa93f019 (difficulty 64.59587)
2012-12-13 06:16:31.221 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 1422781c (difficulty 1.26259)
2012-12-13 06:16:44.814 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000ca0f9d41964b74c60c68ab64de35a729e409c23ccf868a3be228fd94fb3fa87850c9021c1a04fa62
2012-12-13 06:16:49.856 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000ca0f9d41964b74c60c68ab64de35a729e409c23ccf868a3be228fd94fb3fa87850c9021c1a04fa62:9aac053c
2012-12-13 06:16:50.348 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 9aac053c (difficulty 9.85461)
2012-12-13 06:17:01.276 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000085b8cac2e25292a734010f5e687906cdf93c1bc7aafe1fc6cb65476178aa0ce650c902271a04fa62
2012-12-13 06:17:14.991 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000085b8cac2e25292a734010f5e687906cdf93c1bc7aafe1fc6cb65476178aa0ce650c902271a04fa62:e1044fa3
2012-12-13 06:17:15.499 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share e1044fa3 (difficulty 1.51086)
2012-12-13 06:17:17.737 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000a2d4413fe814fc48f3b07ee7881278d3dd1f14c2a86e97604066e9428003f43850c902321a04fa62
2012-12-13 06:17:34.054 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000a2d4413fe814fc48f3b07ee7881278d3dd1f14c2a86e97604066e9428003f43850c902321a04fa62:5d274bc2
2012-12-13 06:17:34.223 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000011cc538da3d1dcc4174450caeb300ece6939700eb1fc6ae0e619599fdb709bbe50c9024d1a04fa62
2012-12-13 06:17:34.547 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 5d274bc2 (difficulty 1.88073)
2012-12-13 06:17:50.684 [400] XUPV5-LX110T_2: Mining BTCGuild_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000295a4b8e6ec6a551531a8f2f18808a1bedd352ee2e733272e600d06cfed0dbcc50c9026b1a04fa62
2012-12-13 06:18:07.146 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000bf23314317eb595d2a901802d5b503539c7ad3e932515a2ecba91db67f447bf450c9028e1a04fa62
2012-12-13 06:18:13.332 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000bf23314317eb595d2a901802d5b503539c7ad3e932515a2ecba91db67f447bf450c9028e1a04fa62:eaa1a449
2012-12-13 06:18:13.824 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share eaa1a449 (difficulty 2.23519)
20
2012-12-13 06:16:28.587 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:46efe802
2012-12-13 06:16:29.079 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 46efe802 (difficulty 2.40814)
2012-12-13 06:16:30.521 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:aa93f019
2012-12-13 06:16:30.728 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f000000002f4367b48db99438166efa247ce096343e64a76f02ed404c3e767653cb80ad6250c901c81a04fa62:1422781c
2012-12-13 06:16:31.014 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share aa93f019 (difficulty 64.59587)
2012-12-13 06:16:31.221 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 1422781c (difficulty 1.26259)
2012-12-13 06:16:44.814 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000ca0f9d41964b74c60c68ab64de35a729e409c23ccf868a3be228fd94fb3fa87850c9021c1a04fa62
2012-12-13 06:16:49.856 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000ca0f9d41964b74c60c68ab64de35a729e409c23ccf868a3be228fd94fb3fa87850c9021c1a04fa62:9aac053c
2012-12-13 06:16:50.348 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 9aac053c (difficulty 9.85461)
2012-12-13 06:17:01.276 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000085b8cac2e25292a734010f5e687906cdf93c1bc7aafe1fc6cb65476178aa0ce650c902271a04fa62
2012-12-13 06:17:14.991 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000085b8cac2e25292a734010f5e687906cdf93c1bc7aafe1fc6cb65476178aa0ce650c902271a04fa62:e1044fa3
2012-12-13 06:17:15.499 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share e1044fa3 (difficulty 1.51086)
2012-12-13 06:17:17.737 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000a2d4413fe814fc48f3b07ee7881278d3dd1f14c2a86e97604066e9428003f43850c902321a04fa62
2012-12-13 06:17:34.054 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000a2d4413fe814fc48f3b07ee7881278d3dd1f14c2a86e97604066e9428003f43850c902321a04fa62:5d274bc2
2012-12-13 06:17:34.223 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f0000000011cc538da3d1dcc4174450caeb300ece6939700eb1fc6ae0e619599fdb709bbe50c9024d1a04fa62
2012-12-13 06:17:34.547 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share 5d274bc2 (difficulty 1.88073)
2012-12-13 06:17:50.684 [400] XUPV5-LX110T_2: Mining BTCGuild_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000295a4b8e6ec6a551531a8f2f18808a1bedd352ee2e733272e600d06cfed0dbcc50c9026b1a04fa62
2012-12-13 06:18:07.146 [400] XUPV5-LX110T_2: Mining abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000bf23314317eb595d2a901802d5b503539c7ad3e932515a2ecba91db67f447bf450c9028e1a04fa62
2012-12-13 06:18:13.332 [350] XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T:0000000111f16115409110dad5130b59b32010045a13517849f3f62d0000030f00000000bf23314317eb595d2a901802d5b503539c7ad3e932515a2ecba91db67f447bf450c9028e1a04fa62:eaa1a449
2012-12-13 06:18:13.824 [250] XUPV5-LX110T_2: abcpool_XUPV5-LX110T accepted share eaa1a449 (difficulty 2.23519)
20
everything works ok.
November 27, 2012, 08:21:46 PM
Hi MintCondition,
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Hi Ciuciu,I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Chlorine notified me of the situation, and the fee compensation for april through october has just been transferred for your account. All other affected accounts have also just received their compensation for these months.
Sorry for the delay. I've been a bit demotivated by the fact that getting the new pool software ready is taking so much longer to than I had hoped, and had not checked the forum and my PM's for quite some time as a result.
Rest assured the compensation agreement still stands until your stolen BTC are fully compensated.
Regards,
MC
11.52 BTC received. Scammer request canceled.
Thanks for the payment.
November 27, 2012, 07:23:22 PM
Hi MintCondition,
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Hi Ciuciu,I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Chlorine notified me of the situation, and the fee compensation for april through october has just been transferred for your account. All other affected accounts have also just received their compensation for these months.
Sorry for the delay. I've been a bit demotivated by the fact that getting the new pool software ready is taking so much longer to than I had hoped, and had not checked the forum and my PM's for quite some time as a result.
Rest assured the compensation agreement still stands until your stolen BTC are fully compensated.
Regards,
MC
November 27, 2012, 02:34:24 PM
Hi MintCondition,
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Still no answer. MintCondition if you don't contact me by the end of the week, I will request a scammer tag for you.
No contact whatsoever. Scammer tag for MintCondition requested.
https://bitcointalksearch.org/topic/solved-mintcondition-of-abcpool-128050
November 23, 2012, 12:21:06 PM
Hi MintCondition,
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
I was one of the users affected by the security breach a while ago. You promised you will return the BTC from the fees I pay. I believe your last payment was in February. I contacted you direct, but I got no answer.
Thank you.
Still no answer. MintCondition if you don't contact me by the end of the week, I will request a scammer tag for you.
November 13, 2012, 08:43:44 AM
Getting a LOT of found shared being rejected by ABC as "unknown-work", or timeout errors.
Job:
Mining abcpool_XUPV5-LX110T_2:00000001bc736f0366b85e7f2f266353a1f72dc12f5bab3facf4cdfe000003fd000000000cd5a78 ec3d3d1c6b191c0900ba65c4b765bdde44027e9175d6338ff63765c0e50a249ed1a04faeb
found:
XUPV5-LX110T_2: Found share: abcpool_XUPV5-LX110T_2:00000001bc736f0366b85e7f2f266353a1f72dc12f5bab3facf4cdfe000003fd000000000cd5a78 ec3d3d1c6b191c0900ba65c4b765bdde44027e9175d6338ff63765c0e50a249ed1a04faeb:f8d30a4d
Rejected?
abcpool_XUPV5-LX110T_2 rejected share f8d30a4d (difficulty 1.80061): unknown-work
Jump to: