So is this the start of a new round?
If the block matures, yes it has already begun. |
|
|
|
|
This will be the first payout, so bear with me if anything goes awry.
The dry run calcs look correct, so your balance should be fine. It's the payout that untested so far.
|
|
|
|
cross your fingers, we're waiting on a block to mature  |
|
|
|
If my account details show a hash rate of 770 or so, but my actual hashrate is about 1300 does that mean there is a problem with my account? Or is this just a display or average or time or some such.
Thanks!
It is a direct calculation of shares received over the last 10 minutes. It can fluctuate, usually +/-10% |
|
|
|
I'm not sure it's even possible to poolhop on your pool currently. For poolhopping you need to know when a new block starts, and the only stat you provide is the hash rate, e.g. not enough  I bet he has implemented long polling... from then on it's trivial!  ^^  yep. this is why I want to switch to the new scoring method on the new round. Even if estimates are off still, I will make the switch to reward our loyal users. |
|
|
|
|
Update: Login is now valid for a week! No more logging in every half-hour!
|
|
|
|
|
using (1-rd.f)*(1-rd.c)*p*rd.b*sum(exp(lscore-lastlscore)) to calculate an estimated earning, I'm getting wildly incorrect results.
For example my account says 11.x, when I run the full round calc it's closer to 6.
Additionally, the sum of estimates is >88, when it should be < 50.
I'm looking at a round with ~1mil shares.
|
|
|
|
I'm not sure it's even possible to poolhop on your pool currently. For poolhopping you need to know when a new block starts, and the only stat you provide is the hash rate, e.g. not enough It's possible, but it is much tougher to gauge. The cheat-proof method also really rewards those who evenly participate in the whole round. Does this "cheat-proof" scoring prevent my earnings from decreasing?
I'm working out the new estimation now. That said, your earnings don't actually decrease now, they are based on your participation % in the round. Until a block is found your earnings are 0. Your ultimate amount now is roughly "(your valid shares/totalroundshares)*50" |
|
|
|
hey all, couple of quick questions.
i'm fairly new at this and don't really understand a large portion of it. i'm currently mining on btcmine.com w/ 650mh/s, avging ~.9 btc a day. my questions are these:
1. does server location effect mining? (i'm in the us)
2. would i see any increase by switching to simplecoin?
3. how do you like simplecoin so far?
4. have they addressed the issues w/ attacks, how is there uptime?
thankyou in advance for your help.
1. Marginally, it seems you get less stale shares using a better network route. I'm not 100% on this but some get far fewer stale shares on simplecoin than the big players. Others see more on simplecoin. It's trial and error. 2. Statistically you should receive the same payout anywhere minus fees. On a smaller pool there is a greater chance for luck either way. I'll leave the last 2 to be answered by the users. Thanks for considering the pool |
|
|
|
I agree, I just want to know what the users want |
|
|
|
|
1 final question.
How do I calculate estimates while using the logarithmic scaling?
(Update, nvm, think I got it)
|
|
|
|
|
Just put up a poll to switch to cheat-proof scoring before the next round. Cast your votes.
|
|
|
|
|
Ok, I've run the numbers.... Those that have stayed with the pool should fair better than those that have come and gone.
|
|
|
|
Got it! I haven't had to wrap my head around this much math in a while. |
|
|
|
I'm getting close  seems like r^i is huge! even a 53digit double gets rounded eventually. You'll need to use either periodic rescaling or logarithmic scale, as discussed in this thread. I'm going for logarithmic, since the other seems hackish. So, I'm close...... it looks like max is the previous row lscore value, is that right? |
|
|
|
I just did that, and I still don't have a saved payout address. Unless it isn't supposed to show up.
PM me your username, I'll get it sorted |
|
|
|
Sorry if this has been covered, but when I try and put in my payout address I get this error. Notice: Undefined index: donatePercent in /var/www/accountdetails.php on line 95 Any idea why? Yes, it's just a small bug. You can set it to 0, 0.00001, or 100% and it will go away  The site errors are on to make sure I don't miss anything before the framework goes live elsewhere That said, the first 3rd party simplecoin framework pool went online this morning |
|
|
|
|
Yes, all the early adopters will now get paid FASTER. more GHs in the pool means more money at a quicker payout.
Unfortunately, seeing your estimated payout decrease is a bit unnerving at first. It confused the crap out of me when I first started mining.
The difference is getting your estimated payout FASTER.
The more GHs the pool has, the faster it solves blocks and the more likely it is to solve the block at all.
Your payout may be smaller, but you'll get it more frequently.
Basically over time the amount should be the same, unless you get unlucky or overly lucky in a very small pool
|
|
|
|
|
Share score is now being counted, I just need to make sure the numerics aren't lost in conversion.
Current round will stay proportional. Once the cheat-proof method is 100% working, I will flip the switch on the after the next successful round.
|
|
|
|
Are you going to wait until after this block to implement it?
(Note: I am #45, so I am still hashing so this would probably benefit me, but it might not really be perceived as fair to those who put a lot of work in at the beginning. Generally speaking though, I think score based is a great idea).
That's not a bad idea. |
|
|
|
|
Show Posts
