 Show Posts
|
|
Pages: [1]
|
|
The DGM estimate is still only half of what it should be. I'm hoping something is just broken/misconfigured... but I've moved my miners elsewhere.
|
|
|
|
|
So uh... since the DGM adjustment didn't settle out before the block was found, we're getting shafted with the last block? It only paid out 13 BTC. That's pretty awful after we spent 7.5 days on a single block. Variance only averages out if we're paid roughly the same for every block... only getting 1/2 of the subsidy on a quick block after waiting a week on a long block is really screwing us over.
|
|
|
|
Ok, since I'm newish to bitparking maybe someone can put me at ease a little.
Right now we are at 6 days on the current block with round cdf at 92.53%. What is the longest a block has run on bitparking, and is there a time limit that it will say hey this isn't working let's start over?
Still working on the app, emailed the admin about the json data, so hopefully that should be in beta soon.
If there is any android developers that has made an app that parses bitparking and is willing to share their source let me know. The json format that bitparking spits out is a little odd, it's valid but the apple json decoder doesn't like it so much.
Michael
There is no 'starting over' when it comes to mining. Every hash has the same chance to solve a block. This block does indeed massively suck... but it'll be solved sooner or later. In the long run, it'll all average out. Looking at the DGM payments in total for each block, there are still a few that paid out more (29-30 BTCs for the block) whereas we're only at 28-29 BTCs for this block, so it's not the longest yet for the past month or so. Another day or two before we set a "new" record. Except it is the longest block? That 30 BTC block you were referring to took 132:53:32 to solve. This has taken longer. |
|
|
|
Ok, since I'm newish to bitparking maybe someone can put me at ease a little.
Right now we are at 6 days on the current block with round cdf at 92.53%. What is the longest a block has run on bitparking, and is there a time limit that it will say hey this isn't working let's start over?
Still working on the app, emailed the admin about the json data, so hopefully that should be in beta soon.
If there is any android developers that has made an app that parses bitparking and is willing to share their source let me know. The json format that bitparking spits out is a little odd, it's valid but the apple json decoder doesn't like it so much.
Michael
There is no 'starting over' when it comes to mining. Every hash has the same chance to solve a block. This block does indeed massively suck... but it'll be solved sooner or later. In the long run, it'll all average out. |
|
|
|
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). |
|
|
|
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. |
|
|
|
|
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?
|
|
|
|
|
