So the abbreviation is FC? Because Freicoin is already using FRC..
|
|
|
I've enabled a (hopefully) unobtrusive Google text ad in the footer. It'll help keep fees low if people turn off AdBlock on the site. I promise not to run any giant banner ads.
IF it helps keeps fees low/ no fee im all for 1 little ad. Well there are no plans to increase the PPLNS fee from 1% as of yet.
|
|
|
Looks like great minds think alike! haha I know this is lame but nobody else I know will get it -- Just noticed this in stratum while fixing table names: def get_pool_stats(self): self.dbc.execute("select * from pool_bte") ret = {} for data in self.dbc.fetchall(): ret[data[0]] = data[1] return ret
code I wrote the other night for the frontend: function poolStats($query,$curr) { $uwa = Array(); global $read_only_db; $sql = "SELECT * from pool_$curr"; $result = $read_only_db->query($sql); while ($row = $result->fetch()) { $uwa[$row[0]] = $row[1]; } return $uwa[$query]; }
|
|
|
I've enabled a (hopefully) unobtrusive Google text ad in the footer. It'll help keep fees low if people turn off AdBlock on the site. I promise not to run any giant banner ads.
|
|
|
Nice work so far Something should be done about the stats. They should take into account the difficulty (multiplying share by difficulty) if that's possible, so we get the real picture. For ex, I currently mine at 3.54GH/s, but seeing around 500~600MH/s. It also affects the estimated reward, so until the TRC show up in the balance, there's no way to really know how many TRC we made And, again, thanks The reward code already takes difficulty into account. I fixed that part a few days ago. Only the display is off. The user hashrate speed should also be correct on the stats page as it comes directly from stratum (stratum inserts your speed directly into the DB). If it's off, then something else may be wrong. (OR you may just not have waited long enough as it's a 10 minute average)
|
|
|
I was able to click "withdraw" and the transaction went through but nothing has shown up on the blockchain yet... Getting worried...
Give it some time. After the hack last year, in which all Bitfloor users' BTC funds were stolen, Bitfloor moved to storing most BTC funds in a cold wallet. Now that everyone is rushing to withdraw their funds, BTC transactions cannot all be processed automatically. The funds have to be manually taken out of the cold wallet first. transaction just showed up on the blockchain.
|
|
|
I was able to click "withdraw" and the transaction went through but nothing has shown up on the blockchain yet... Getting worried...
|
|
|
Something is wrong with the pool. If the pool hashrate is 37000gh/s, how come there's no block solved within the last hour?
Stratum port was down.. It's back up now. 37,000 was likely the last value stratum inserted into the db.
|
|
|
how to mine BTE on your site? i mine trc
I have a BTE pool set up on 3336 but it doesn't have a frontend yet. If you want to mine shares on there send me an email with your username and I'll create a worker for you.
|
|
|
Mh/s being displayed better, though shows it way higher sometimes.
Difficulty is still a prob (at 15 most times), keep losing a ton of shares when the difficulty goes down to 5k and back up again.
Edit: Server sets the diff to 15 when I'm mining at under 10k diff but doesn't change again when the diff goes up to 100k, for instance.
Yeah, unfortunately I don't think stratum server is built to handle difficulty swings the way they happen on the TRC network. I will look into allowing you to set your difficulty manually.
|
|
|
Was getting loads of stratum disconnects earlier on, seems to have settled now. Difficulty is sensible, too.
Is the Estimate fixed?
Estimated TRC/day on the stats page should be correct. Current estimate displaed under the menu bar is still not fixed.
|
|
|
User hashrates should now be correct. Please let me know if you see a major (>10%) discrepancy between your miner's reported hashrate and what you see on the website.
|
|
|
A question about difficulty...
I'm using stratum proxy. I can see that when I start mining, the difficulty is 1. However, after a short time, difficulty wander between 2 and 5. So I guess that the pool is just throttling me so I send lower traffic. So far so good.
However, when I look at the stats, for example in the 'account detail' page, the MHash/s does not reflect the difficulty change. So I mine at around 2.2GH/s, and suddenly the displayed MH/s lower. However, I'm still mining at 2.2GH/s.
Is this normal? Does this lower my income?
Also, the stats page is displaying the rates incorrectly. It is as if the MHash/s is multiplied by 100.
The payout algorithm takes share difficulty into account. Working on higher difficulty shares does not lower your income. The stats issue is a known issue.
|
|
|
it's up now. sql issue
Hello! Can you please explain reward system on your pool, miner gets payment for every share he sends, newermind on what pool block was found, or pool takes into account only shares from the block, that was found by the pool? Thanks Reward system is PPLNS (Pay-per-last-N-shares). PPLNS - Pay Per Last N Shasres. Similar to proportional, but instead of looking at the number of shares in the round, instead looks at the last N shares, regardless of round boundaries. We don't have a PPS (Pay-per-share) option at the moment but it's something I'd look at offering once the pool has built up some reserves.
|
|
|
Cannot get to pool webpage. R u down?
it's up now. sql issue
|
|
|
There must be something wrong with the estimate reward...About half of pool's power is from me, but it shows estimate 0.05-0.06...
The estimate is currently broken, that's something else I need to work on. What's your username?
|
|
|
Still getting a way too high difficulty after a few minutes. It sets it to 30 which churns out 1 share per minute Hmm, I will look at that later. I thought it was set to optimize for a share every 15 seconds.
|
|
|
if something looks off, please let me know.
Well... haha yeah, one nice thing about stratum is that it keeps track of the hashrates of each worker automatically, so they don't need to be calculated.. But the SQL is a little different since they are stored in a different table. The SQL and/or calculation is still a little wonky. But this is just a display issue. The payout algorithm is not affected.
|
|
|
OK so here is how things are breaking down.
The last paid block before I turned off the site was 103951. I have scored and paid out all the blocks that were found yesterday and today.
I am implementing a weighted average scoring system. Earnings will be paid out as follows:
per block earnings = your_submitted_shares/weighted_round_shares * your_average_difficulty/round_average_difficulty * 20
I've capped the round shares at a lower limit of 5000 for those cases where the difficulty is swinging really low during payment times (which results in only a few people getting paid since so few shares are counted).
Stratum is back up, the site should be back up tonight and tomorrow. Some auto-payments went out earlier. If you don't have an auto-payment set up you should be able to login tomorrow night (at latest) and have your earnings paid out. Here are the blocks we've found since I moved over to the new db:
| 49 | 104008 | bitcoin184. | 18241123 | Y | 20 | 868 | 7f1590f421fa87a3b6c2665a207caad6433a1a3cfb4beb75402118e0bd2c2c75 | Y | | 537 | 104092 | atoronjo.1 | 18243659 | Y | 20 | 860 | 183cd1bb619831ddf1ba4e944d9bb70e0facd35f005a9a05a9d65e4e86e9cc5c | Y | | 538 | 104100 | atoronjo.1 | 18243667 | Y | 20 | 844 | 4a59aa1828a6bc65d0a86cc31617728f239e91430847cd31cd6bfbd8dd35e7f9 | Y | | 539 | 104144 | BlackDuck.1 | 18245588 | Y | 20 | 841 | 47cff6bca6ac0bd2c1fc9aee4d20787dfb9cb14eb54344a06a58c7c9860e0ec0 | Y | | 540 | 104146 | pyraproxy.2 | 18245593 | Y | 20 | 838 | fd9e6b9b1db8022b2055f522eb77e7c8197fafcbceab76cb0fc0f75cc4361931 | Y | | 541 | 104175 | atoronjo.1 | 18246516 | Y | 20 | 837 | 5990dd3099147a8057e4bc6a1e8efa2f24669432157a4dc56f780a8601c81e1b | Y | | 542 | 104182 | atoronjo.1 | 18246523 | Y | 20 | 831 | a4daf2458e42dce07f841fb2d57feae487393ce8cd07f4192d7bd8db985825e3 | Y | | 544 | 104184 | STJumper.1 | 18246525 | Y | 20 | 828 | 52c0e60668308b983007dc1ea7754ef23c132fb6797509e875353e6bf34a823c | Y | | 545 | 104209 | arto40k.w1 | 18247383 | Y | 20 | 823 | bee328b2711c8a051878ea7ce455a921e126cca2dca8bf74ea162ca364472302 | Y | | 546 | 104215 | atoronjo.1 | 18247384 | Y | 20 | 814 | d92671b1f92d1733b55ff3716e88006ef31adf2016404823446fd09678f66414 | Y | | 547 | 104233 | pyraproxy.2 | 18247448 | Y | 20 | 592 | d6029d70c5ecf12cffc50452d6bd1fc4a57130f93ae2c7571e9da4fb3eecf432 | Y | | 548 | 104275 | pyraproxy.2 | 18248341 | Y | 20 | 503 | 743cdbcd93c76793384df50c0beb9866110b66a19893df9b00f713e2fff32260 | Y | | 549 | 104287 | pyraproxy.2 | 18248639 | Y | 20 | 449 | 2b5330cd9b98f7cc3bd2cd96130d6345685df7dfcaa57ca7922e0129754fe86e | Y | | 550 | 104312 | pyraproxy.2 | 18249157 | Y | 20 | 424 | 9a4f2b4387014cbf3e727bbfc9c8a2a1363bc63e89b9fc575e21a8366c32d11a | Y | | 551 | 104377 | chr0me.1 | 18249694 | Y | 20 | 359 | 022c627197d1000572c9853bb71d298272de4e38ff4d6c5513d4b3074d4b93e6 | Y | | 552 | 104396 | caish5 | 18250083 | Y | 20 | 340 | 209de273051569eeb70c65277c83d12d83942886efe6b0798708175e9d79458f | Y | | 553 | 104435 | Lasergun.2 | 18251678 | Y | 20 | 301 | 65b1fd61c3202e4d4900d65749f5e3592c0ded6398107a658dc960fa26849563 | Y | | 554 | 104568 | chr0me.1 | 18255913 | Y | 20 | 168 | 0b2159133a21df39d170d581feda944276a89bc1f0b6314d4e8e705c40e516d5 | Y |
Once you're able to login and see your balance, if something looks off, please let me know.
|
|
|
stratum is up, frontend is still down while I work out the new payment code in SQL.
All of your submitted shares are being recorded and will be paid out. It might be another day though. We did find a few more blocks last night so that's good.
|
|
|
|