Yeah... no rush for you  . By the way, I made changes to the pool stats page. KH/s was a bit stupid - who even thinks about mining BTC in terms of KH/s any more? So, I changed the pool stats page to display TH/s.  |
|
|
|
Alright, so I've taken a look at the stats code. It's stored in the database as KH/s. Example: my hash rate on my own pool is stored in the database stats tables as 96619545681. Displayed on the website stats it shows as 96,629,545,681 KH/s. Turning that into TH/s means dividing by 1,000,000,000 yielding 96.629545681 TH/s. Everything is written using smarty templates on the front end. So the choice is to either 1) change the template to display TH/s and recompile or 2) change the way the stats are stored in the database tables. Laziness would dictate that I just change the template to display it in TH, leaving the underlying stats stored as is. If I get around to it, I'll make the required changes and share the code with BCMonster. EDIT: Here's the code to add to the template if you want to show TH/s. Edit templates/bootstrap/statistics/pool/contributors_hashrate.tpl file. Add the following after line 24: {math assign="hashths" equation="hashrate / pow(10,9)" hashrate=$CONTRIBHASHES[contrib].hashrate}
Then you need to change line 29 to the following: <td class="text-right">{$hashths|number_format:"3"}</td>
Also, you need to change the table header label to TH/s. Edit line 13 as follows: <th class="text-right">TH/s</th>
Actually, it compiles itself properly. Here are the changes on my own pool: |
|
|
|
|
Good luck to you!
Laviathon, check your PMs... I sent you how to change from KH/s to TH/s on your pool.
|
|
|
|
|
Yeah, the signed binaries aren't available yet (should be within the next couple of days I'd guess)... however, the final v0.12 code is released and you can build it yourself - which is what I do.
|
|
|
|
|
No problem. I like 0.12 and was glad the final was released so I could safely put it up on the pool.
For example, if the pool found a block right now it would contain 2650 transactions and fees of 0.48BTC. If I wanted that information previously, I'd have to look in multiple places.
|
|
|
|
Both. I only have a Sidehack Compac Stick, a U3 and an R1 going solo as a lottery. One Miner on Jonny's pool and everything else is pointed at kano.is and has been for some time now. The little guys will never ROI and were bought for fun, so why not take a gamble at solo!  I appreciate you and every other miner who points hash to my pool. To OP: I mine on my own pool. Both my own hardware and rentals. I'm split between antpool and ghash.io, I love the dependability of antpool but the gains are higher on ghash when we hit a block. I've got some hardware solo mining but it's all in places where I don't have to pay for electricity, set it and forget it kind of stuff. If my wallet ever jumps by 25BTC I'll celebrate, then promptly have a heart attack.
Of all the pools you could choose... antpool is not dependable. They don't provide mining transaction fees to miners (you only split the base block reward). They SPV mine, which has caused hard forks in the past. They are one of the worst pools for submitting empty blocks. So many other good choices out there... |
|
|
|
|
All,
I will be taking down the pool servers at approximately 10:00am EST on 2/19 to perform some maintenance, including updating to Bitcoin Core version 0.12. I don't expect this to take longer than a couple of minutes; however, your miners will fail over. Please ensure you have backup pools properly configured.
I will post here as soon as the maintenance is complete.
Thanks!
EDIT: Pool coming down now at 10:19 EST.
EDIT: Pool back up at 10:30 EST.
|
|
|
|
Hey slush, I don't know if you've seen it, but here's some good analysis by OOC regarding early detection of block withholding attacks... might be something you could implement: http://organofcorti.blogspot.com/2016/02/detecting-unintentional-block.htmlEDIT: Appears OOC has already been in contact with you guys... but I'm leaving the link there for anyone else interested in reading up on block withholding. |
|
|
|
Great points, kano. You actually power cycled an S2? Were you actively trying to set it on fire? I remember pretty much the first thing one did with an S2 was to replace the PSU... before you ever even bothered turning it on  . |
|
|
|
|
I run my Avalons on the EVGA 1300 G2. Absolutely rock solid PSUs and I can't recommend them highly enough.
Edit:
Example of how good the PSU is... Before they ran my Avalons, each G2 was running 3 S3s nonstop since 2014. 20 months of constant usage powering miners, 24/7.
|
|
|
|
LOL... I can imagine that would have gotten old quick |
|
|
|
|
Sent. TxID: 362a68ca80ba29659f0f90dfade3feafaf35b804e102bae6ecaa760abb7c8207
|
|
|
|
Hi Jonny, That is perfect  . You can use the address wich i use in the pool. And, yes i found earlier payouts, but that is from the previous block, not most recent block Again, correct me if i am wrong ;-) Thanks for your effort on the pool and all things that come with that! I'm a supporter of this pool it's simpleness(positive:-) and small scale! Keep up the good work! Dennishh You're absolutely right. You got overpaid for block 2, and underpaid for blocks 1 and 3... Hence the discrepancy noted in the spreadsheet. I'll send the coins along to you shortly. |
|
|
|
Hi dennishh, You are reading it correctly. Looking at the spreadsheet, the pool underpaid you 0.0976 BTC for your contributed work. If it is alright, I will send the coins to the address you use mining on the pool. Otherwise, if you want it sent elsewhere, please provide me with a BTC address to send them. Edit, you did indeed receive payouts. Your actual payout records show the following: +----------+------------------------------------+----------------------------------+---------------------+
| type | coin_address | amount | timestamp |
+----------+------------------------------------+----------------------------------+---------------------+
| Credit | NULL | 0.257253014709827920740000000000 | 2016-01-11 05:33:56 |
| Fee | NULL | 0.001286265073549139630000000000 | 2016-01-11 05:33:56 |
| Debit_MP | REMOVED | 0.255866749636278811850000000000 | 2016-01-12 06:21:01 |
| TXFee | REMOVED | 0.000100000000000000000000000000 | 2016-01-12 06:21:01 |
+----------+------------------------------------+----------------------------------+---------------------+
|
|
|
|
Yeah... there's definitely an issue. You authorize fine, submit a few shares fine, then BAM you're sending massive quantities of rejects. The reason the pool looks dead? It bans you because of flooding. The following are snippets from the pool stratum server logs. Passwords and IP addresses removed . 2016-02-16 14:14:50 [Pool] [bitcoin] (Thread 3) Authorized nortron.s2: xxxx
2016-02-16 14:14:52 [Pool] [bitcoin] (Thread 3) Share accepted at diff 1042/1392.47875174 by nortron.s2
2016-02-16 14:14:56 [Pool] [bitcoin] (Thread 3) Share accepted at diff 1042/1663.54685942 by nortron.s2
2016-02-16 14:15:15 [Pool] [bitcoin] (Thread 3) Share accepted at diff 1042/1408.90212059 by nortron.s2
2016-02-16 14:15:18 [Pool] [bitcoin] (Thread 3) Difficulty update to diff 453.04347826 workerName="nortron.s2"
2016-02-16 14:15:28 [Pool] [bitcoin] (Thread 3) Share accepted at diff 453.04347826/8109.63273026 by nortron.s2
2016-02-16 14:15:29 [Pool] [bitcoin] (Thread 3) Share accepted at diff 453.04347826/7413.46597719 by nortron.s2
2016-02-16 14:15:40 [Pool] [bitcoin] (Thread 3) Share accepted at diff 453.04347826/2728.61401655 by nortron.s2
2016-02-16 14:15:47 [Pool] [bitcoin] (Thread 3) Share accepted at diff 453.04347826/1405.38320558 by nortron.s2
2016-02-16 14:15:50 [Pool] [bitcoin] (Thread 3) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":453.04347826,"error":"low difficulty share of 1.4178721372176153"}
2016-02-16 14:15:50 [Pool] [bitcoin] (Thread 3) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":453.04347826,"error":"low difficulty share of 2.2534057741723235"}
2016-02-16 14:15:50 [Pool] [bitcoin] (Thread 3) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":453.04347826,"error":"low difficulty share of 2.299571152495193"}
2016-02-16 14:15:50 [Pool] [bitcoin] (Thread 3) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":453.04347826,"error":"low difficulty share of 1.610991188080095"}
2016-02-16 14:15:50 [Pool] [bitcoin] (Thread 3) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":453.04347826,"error":"low difficulty share of 1.9361901540633337"}
... 2016-02-16 14:15:53 [Pool] [bitcoin] (Thread 3) Banned triggered for nortron.s2 : 492 out of the last 500 shares were invalid
2016-02-16 14:16:53 [Pool] [bitcoin] (Thread 4) Authorized nortron.s2:xxxx
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Share rejected: {"job":"ade0","worker":"nortron.s2","difficulty":1042,"error":"job not found"}
...
2016-02-16 14:16:58 [Pool] [bitcoin] (Thread 4) Detected socket flooding from nortron.s2
|
|
|
|
|
Let me take a look at the logs to see if I can spot anything...
|
|
|
|
Wierd... Seems ok now... Been running about 30 mins.. LSDiff is now showing 1536, but only 2 rejected and 0 stale....
Will let it keep going and see what happens...
Thanks,
Antminers had issues with diffs set as powers of 2. Not sure if that was the cause of your problems. If you want to test it on my pool, please feel free to do so (my pool starts at a 1042 - not a power of 2)... and then come back and mine with BCMonster - I'm definitely not trying to poach any miners, just offering you up another test environment. |
|
|
|
Under R I show a positive, but it doesn't match what I have still sitting in the pools wallet. Am I safe to withdraw or should I wait?
No. You can withdraw what is your balance. I'm not messing with people's balances. Please send the overpayment amount to the BTC address in my profile. |
|
|
|
|
The one in my profile if you please.
|
|
|
|
All, I have completed the spreadsheet and have uploaded it to the following location: https://www.dropbox.com/s/99ijt4by0jc8nq4/pool_payouts.xlsx?dl=0If you do not have Excel, or google docs, or any other spreadsheet program, please let me know and I will gladly present the data to you here on the thread. Looking at the spreadsheet, pay attention to column R. If that number is NEGATIVE, you were UNDERPAID. If the number is POSITIVE you were OVERPAID. Some of you have already committed to paying back any coins - and in fact, some of you have already sent those coins to me. If you are underpaid, and you wish to have things corrected, please let me know. I will send you coins from my own pocket. Of note: I was the worst affected of any miner on the pool. Even though I was overpaid for block 3, I was significantly underpaid for block 2. Net loss for me was 4.96 BTC. If you have any questions or comments, I will address them to the best of my ability. My GoJonnyGo account has -0.3329574 This is a little more than I'm willing to just let go so would be grateful if it could be sent to my payout address. Thank you. I will send as soon as I can... Been stuck in airports all freaking day. At least I was able to compile the spreadsheet while waiting for yet another delayed or canceled flight... Well... yet another flight just got canceled... so I am able to send you your coins now. TxID: 3e248b405f9a5947b8b4964831501deb8b20dde227da6389842173b5369c2fb0 Total sent: 0.33295743 |
|
|
|
|
Show Posts
