|
Lucko
|
 |
November 14, 2013, 07:19:06 AM |
|
It also makes me wonder about the longevity of the pool. Can the owner afford to keep this pool running? 88 BTC is almost $40k at the current price.
Most of that negative balance came from when the pool was still running using PPS with a really low fee. No it is from the time pool was still paying orphan blocks... |
|
|
|
|
|
|
|
|
|
|
|
|
|
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Alexis_Evo
Newbie
 Offline
Activity: 8
Merit: 0
|
|
November 14, 2013, 07:46:24 AM |
|
How would they lose any money?
If the pool is rather unlucky, every block could take 70-100 hours, which would result in every block paying out 28-30 BTC. Considering a block only gives 25 BTC, the chance of losing money is there. Given an infinite amount of time, assuming it is implemented properly, and 0% fees, it should balance out to 0. But, in the short term, it's still possible to lose money if the pool is unlucky. It also makes me wonder about the longevity of the pool. Can the owner afford to keep this pool running? 88 BTC is almost $40k at the current price.
Most of that negative balance came from when the pool was still running using PPS with a really low fee. No it is from the time pool was still paying orphan blocks... Ahh, that should explain it. Thanks. That's a pretty hefty loss for the pool to eat though... (but I wasn't around when that happened -- could've been when BTC was still $2 for all I know). |
|
|
|
|
|
Krak
|
|
November 14, 2013, 08:08:06 AM |
|
No it is from the time pool was still paying orphan blocks...
That's also part of it, yes. The pool was obviously paying for orphans on PPS too. |
BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
|
|
|
|
KrLos
|
|
November 15, 2013, 08:07:08 PM |
|
Finally! block found, took 132:53:32 hours
Hash Rate (GH/s) 15639.41
|
|
|
|
|
disclaimer201
Legendary
Offline
Activity: 1526
Merit: 1001
|
|
November 15, 2013, 08:18:02 PM |
|
Wow. It would be nice if we could get some more hashrate somehow. Tell your friends!
|
|
|
|
|
|
Lucko
|
|
November 17, 2013, 11:57:00 AM |
|
There is something wrong with DGM Estimate... It should be much higher... I guess you had another double block... Just not reported in stats... Please fix...
And when are you planing to fix error on DGM for the least 3?
|
|
|
|
|
kjlimo
Legendary
Offline
Activity: 2086
Merit: 1031
|
|
November 18, 2013, 01:30:24 AM |
|
Seems like this pool has been having awful luck, if the blockstats page is accurate. "-88.60940710" I assume this means the pool has lost this much due to bad luck/long blocks?
Longest block ever if I am correct. It happens. Sure it happens, but being -88 BTC would imply a long streak of bad luck rather than just a single long block :p. Infact, payoff for long blocks drops exponentially, seemingly capping at 30BTC or so, which would mean a couple of bad blocks wouldn't result in that high of a loss. It'd take a significant amount of unlucky blocks to hit -88 BTC. It also makes me wonder about the longevity of the pool. Can the owner afford to keep this pool running? 88 BTC is almost $40k at the current price. LOL, I assume doublec is doing alright... but I also assume he appreciates your concern  |
|
|
|
|
pat1900
|
|
November 25, 2013, 10:43:31 AM |
|
Can't connect to bitparking at the moment. 504 Gateway Time-out.
Even the json userstats don't work. Any changes to the URL recently?
|
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
disclaimer201
Legendary
Offline
Activity: 1526
Merit: 1001
|
|
November 25, 2013, 11:19:20 AM |
|
Can't connect to bitparking at the moment. 504 Gateway Time-out.
Even the json userstats don't work. Any changes to the URL recently?
DDOS? |
|
|
|
|
|
IYFTech
|
|
November 25, 2013, 01:15:18 PM
Last edit: November 25, 2013, 01:49:16 PM by IYFTech |
|
Any news?  EDIT: Back up again.... |
|
|
|
kjlimo
Legendary
Offline
Activity: 2086
Merit: 1031
|
|
November 25, 2013, 01:49:38 PM |
|
Seems like the stats pages are back up, but the miners are still using backup pools for now.
|
|
|
|
|
pat1900
|
|
November 25, 2013, 04:03:03 PM |
|
Looks ok now. Miners working at bitparking again. Main page says: 2013-11-26: The pool suffered a half day outage today due to a DoS attack. I'm hoping that service can be back to normal soon. |
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
disclaimer201
Legendary
Offline
Activity: 1526
Merit: 1001
|
|
November 25, 2013, 04:52:23 PM |
|
Hash Rate (GH/s) 11602.89
|
|
|
|
|
aerodactylrider
Newbie
Offline
Activity: 16
Merit: 0
|
|
November 25, 2013, 08:40:32 PM |
|
When I try to register to mine on this pool I get an error. Am I alone?
|
|
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
November 25, 2013, 08:48:30 PM |
|
When I try to register to mine on this pool I get an error. Am I alone?
broken |
|
|
|
|
pat1900
|
|
December 02, 2013, 09:48:27 PM |
|
Statistics say "Round Duration: 92:..:.. hours" although we've found quite a few blocks during the last 48 hours, see http://blockchain.info/blocks/BitparkingEven worse, user statistics "DGM Estimated Round Payout" has not changed for 24+ hours. Very odd. What's going on? |
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
|
Krak
|
|
December 02, 2013, 10:29:03 PM |
|
Statistics say "Round Duration: 92:..:.. hours" although we've found quite a few blocks during the last 48 hours, see http://blockchain.info/blocks/BitparkingEven worse, user statistics "DGM Estimated Round Payout" has not changed for 24+ hours. Very odd. What's going on? Blockchain.info is quite often wrong with their block sources. They look at the IP that relays the block to their server (which could be anybody really) instead of looking at the message in the coinbase. |
BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
|
|
|
|
pat1900
|
|
December 02, 2013, 11:00:41 PM |
|
Blockchain.info is quite often wrong with their block sources. They look at the IP that relays the block to their server (which could be anybody really) instead of looking at the message in the coinbase. You are right. I haven't looked at the coinbase. Latest block from blockchain.info/blocks/Bitparking says "Mined by user zhaodaniao1". This is certainly not us. Still, how come the DGM Estimated Round Payout has frozen? The json values (mmpool.bitparking.com/userstats/<username>) are contradictory, too. "dgmscore" goes up while "dgm" doesn't  |
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
caminilegroup
Newbie
Offline
Activity: 42
Merit: 0
|
|
December 02, 2013, 11:33:47 PM |
|
Is the pool working correctly, I know 93 hours is long, but we just had a 120 hour block. At 16 TH/s shouldn't we be solving at around 48 hours instead?
I'm newish to bitparking, been using it off and on. If we spend all this time trying to solve this one block what are the chances that it will get solved somewhere else and all our efforts are wasted?
Michael
|
|
|
|
|
|
pat1900
|
|
December 03, 2013, 12:24:45 AM
Last edit: December 03, 2013, 12:50:51 AM by pat1900 |
|
At 16 TH/s shouldn't we be solving at around 48 hours instead? This is correct, but it averages out. We recently found a block after 10 hours and another one after 29 minutes. If we spend all this time trying to solve this one block what are the chances that it will get solved somewhere else and all our efforts are wasted? No, we do not mine "this one block". We mine blocks at current difficulty, independently of other pools. If another pool finds a block then this doesn't affect our chances finding a block. Still, how come the DGM Estimated Round Payout has frozen? Problem solved, dgm values look normal now. Seems that doublec is listening to this thread  |
USD: 0.000 BTC ▶ EUR: 0.000 BTC ▶
|
|
|
|
