Little orange devil is flashing regularly on first .....
I'm seeing green... |
|
|
|
- wait until we hit a 800% one day (maybe) then you'll be wondering why you were mining  (longest so far is 525%) Is this the one you were warning us about?  |
|
|
|
Everyone using ckpoolmonitor.zachmonroe.com please double check your apikey. When you try to save it now it will check it for you, if it is bad it won't save it and you will get an error message. I see a couple that are wrong and several that are blank, no apikey or a bad one and no graphs. Wrong apikeys have been removed, there are 8 users with no apikey, 3 of which have no username either. Make sure you check to box to get an email when we find a block, saves having to check constantly all day like I usually do. Also make sure you use a valid email address when you sign up. (I will make it so you change your email address soon.) |
|
|
|
There is absolutly no need for an apology. If anyone thinks the down time is due to laziness, neglect or anything like that is mad.
Thanks to the both of ya for all your hard work. Cheers.
Yes, You guys are great! |
|
|
|
Sorry .... I know nothing about code. I live by the Baseball rule. If you try something 3 times with the same result then you need to change.
With code: 1. Try something 2. If it works go to 4. 3. If it doesn't work go to 1. 4. Use it until something breaks then go to 1. |
|
|
|
ckpoolmonitor.zachmonroe.com is back up and running, if you have more than 25 workers you will not be able to track them all. It will track your first 25 and your total hashrate. I'm going to try to work something out to track all workers, but right now it overloads the system. Also notice the main page has an average of payouts per day.
|
|
|
|
Pool shows 4.6ph/sec rollin, but none of my miners can connect, they all rolled over to their backups.
I don't think that calculates in the zeros for the last 2 hours. The site is also not grabbing the last network block. |
|
|
|
|
I found an issue with my database/php, there is a user with so many workers that script that enters everything into the database crashes when processing his workers, so any user who signed up after him was not getting tracked. I have (temporarily) limited the number of users tracked to 25. Your total hashrate will still be tracked. When I have more time I will try to sort it out.
|
|
|
|
I am good Zach! I pointed all miners to a single worker.
Good, have you tried the option for getting an email when we find a block? If so is it working, if so is there more info you would want in the email? |
|
|
|
Glad to see another competition, the pool is upto 5.2 PH right now. I have 43 TH on the pool now, and just got my two S5's in the mail today, so I'll have them up and running soon. I see a couple users on ckpoolmonitor.zachmonroe.com that are showing 0 hashrate, but they show hashrate on kano.is, is anyone having problems? |
|
|
|
Soon Zach will be able to overlay his graphs from when he implemented to compare hashrate on pool to found blocks. Very cool stuff.  Yes, I have something in the works. |
|
|
|
with very bad luck, the share may not even get paid once - if it is more than 500% before the next block i.e. an unlucky block that is over 500% Diff%
We've so far only had one block over 500% - it was 525%
This is looking like one of those very unlucky blocks, almost 32 hours.  5 Ph and one block per day ? And actually over the last 42 blocks the pool average has been almost 2.5 blocks per day. |
|
|
|
Especially if you look at the fact that we hit 4 blocks on the 16th and 5 blocks on the 17th! We definitely had a run of good luck. And only 68% average for the last 42 blocks. |
|
|
|
5 Ph and one block per day ?
For the most part it is all about luck, more hash increases odds, but does not guarantee anything. |
|
|
|
with very bad luck, the share may not even get paid once - if it is more than 500% before the next block i.e. an unlucky block that is over 500% Diff%
We've so far only had one block over 500% - it was 525%
This is looking like one of those very unlucky blocks, almost 32 hours. |
|
|
|
That was only their broken initial firmware and should be fixed by now after I showed them why it happens in their driver.
That makes sense, I am using the latest firmware. |
|
|
|
|
I just leave the difference at 0 (variable) for my S4. It seams to running fine, what would be the advantage oof setting it to 2048? It is running at 1.75k right now.
|
|
|
|
I have 4,8 TH (you can see me at the pool) https://www.miningrigrentals.com/rigs/4161block 339486 - 0.00188319 BTC block 339552 - 0.00823398 btc block 339586 - 0.00579804 btc 1MfoQRP8wGUA82w5RTuonL2n9mK3hYrzm9 I had more than 0.1% of block when blocks was found 25btc : 1000 = 0,025 I feel disappointed You were only on the pool for 12 hours, which was about 150% so you were not on for the full 500%. You should notice that you still get a couple more payouts because you were part of the 500% of the next couple blocks. If your going to rent rigs for use on a PPLNS Pool, I would suggest you rent for a couple days. |
|
|
|
Zachm, thanks for this ... just registered on your site ... appreciate your work in getting this up and running. You Are Welcome! - had a server failure at home.
That really sucks!  I know it is probably a silly question but, is there anything we can do to help?  I'm going to send you some BTC to the address in your sig, unless you want it somewhere else? |
|
|
|
|
Show Posts
