Great tool btw. It has worked well. However I am running into one small issue. I can't seem to add more than 5 machines before the 5th field gets shared with the 6th. I had hoped to be able to scale out. Is this possible?
For instance if I have 5 and add a 6th the two fields are shared I have no way of separating them. Anything I can do to address this?
I've had 9 Ants running on here (see op screenshot) and I know others have had a lot more than that. Can you post a screenshot of what you mean? There is an issue where if you have two ants with the same ending address only one will appear on the grid. ie, 192.168.0.90 192.168.1.90 only the first will appear and it gets overwritten with the second. But both are configurable for monitoring, they just don't both show up. M |
|
|
|
Excuse me if I don't want to read through 26 pages, but... can this be used for Ant's outside the home ?
I have four S3's hosted about 5hrs from me and I usually just leave a browser tab open for each one but this program intrigues me.
All of my S3's have an IP like this, all using the same PW.
1.2.3.4:5676
1.2.3.4:5677
1.2.3.4:5678
1.2.3.4:5679
If you use the Web based screen scraping, as opposed to the API, there's a good chance it'll work for you. M |
|
|
|
the amount of time and effort that would be needed to eliminate the very few failsafes that do occur far outweighs the benefits of doing so at this time. Exactly the opposite of what you want to hear from your pool operator. I have no dog in this fight, just pointing out the "fail safes" have been the #1 complaint (next to delayed payouts, don't get me started on the 6 month no NMC payouts) for almost a year or more now? You'd think you'd personally want to fix this issue to better your pool, your supporters and miners (and to minimize the complaints!).. but evidently that is far from the case. Again, nothing against wk or eligius- I've mined, donated etc. but have moved on to a more comfortable and less stressful pool. Happy mining all  There are 9.5 PH/s of hashpower here which doesn't seem to be too concerned about it. I'm a drop in the pond, and I certainly do not consider this pool uncomfortable or stressful. To each their own.. M |
|
|
|
Your argument about prior 150% luck is useless for any new miner that might have joined a week ago. They have zero benefit when they weren't here.
Your point could be applied to any pool. M |
|
|
|
What's going on with this pool??
Seems fine to me. Normal luck swings. Pays out. Responsive. Low variance because of high hash rate. Good op. What's your issue? M Yet another failsafe?? But, speaking of luck swings, it looks terrible as of late. Failsafes are there for a reason. It wasn't that long ago that we had 150+% luck. How come you weren't complaining then? M |
|
|
|
What's going on with this pool??
Seems fine to me. Normal luck swings. Pays out. Responsive. Low variance because of high hash rate. Good op. What's your issue? M |
|
|
|
O M G
After all that, can you advise what would be the right way to go???
/0 /1
or just leave it alone???
All of this on the ants??
Thanks...
I recommend leaving it alone. M |
|
|
|
Can you add the ghash.io pool?
Thanks
It's on the todo list, but I have no idea when it's going to happen. M |
|
|
|
Wizkid
You are doing a mountainous job. I have been a ISP owner since 1995. A service that runs 24 hours a day 7 days a week, is a huge job to maintain and support. Server failure is a massive pain, I have been there done that.
I just want you to know there are allot of people here that know what your going thru and how much work it is, and want to truly thank you, when some one worries about a .2 pay out they just do not have a clue.
If there is anything I can do to assist just let me know. I am sure there is not. But of there is just ask.
Again thanks for all you do for this pool.
JC
While I hear you and agree with you ... 0.2 BTC is a lot to some people. Myself included. M Depends on how you look at it... Eligius mines on average 10-11 blocks per day, at 25 BTC+ each... 0.2 BTC over 4 days is less than 0.02% of what the pool mines (on average). If just 1% of the earnings in the same situation needed support over 0.2 BTC.... that'd be 5000 support requests... And thank you JC for the supportive words. It is good to know that some people do understand how much effort all of this is sometimes.  I'm not suggesting it's worth falling over yourself for.. just stating 0.2 BTC is a lot for some people. M |
|
|
|
Wizkid
You are doing a mountainous job. I have been a ISP owner since 1995. A service that runs 24 hours a day 7 days a week, is a huge job to maintain and support. Server failure is a massive pain, I have been there done that.
I just want you to know there are allot of people here that know what your going thru and how much work it is, and want to truly thank you, when some one worries about a .2 pay out they just do not have a clue.
If there is anything I can do to assist just let me know. I am sure there is not. But of there is just ask.
Again thanks for all you do for this pool.
JC
While I hear you and agree with you ... 0.2 BTC is a lot to some people. Myself included. M |
|
|
|
hash rate they may be out doing the 2 terra's but earning wise what happening may pay to look at how many shares they are putting in ...... in theory on a s1 you should hit around 16mil diff 1 shares every 2 days on normal mining pools that is 2-3 shares p2 wise they are luck to hit 1 so off your example above 3 by 12 ants = 36 ant miners in total you should be seeing around 90 odd share every 2 days between them or there abouts to be on par with their diff 1 share rate and that the issue they are hitting no where near their diff 1 share rates......
The last 27 shares found on my node (out of 52 total for 1.5 day uptime): 8 shares - S1 group 1 5 shares - S1 group 2 5 shares - S1 group 3 9 shares - Terraminer group Very appropriately proportional. Roughly 7.2TH/s for the S1's, roughly 3TH/s for the Terraminers. 2:1 hash ratio, 2:1 share ratio. dude look at them number close they are no where near what they should be for an s1 diff 1 share rate....... the 1st group has hit at less than a share each in 1.5 days and it get worst from there I rest my case 8 * 6.5 mil = 5200000 diff 1 share for that 1st group of 12 miners they should be around 32000000 diff 1 share at the end of day 2 they are about 26 mil shares down atm vs ya mining a normal pool...... diff 1 share wise so there a huge loss there atm vs mining at a normal pool You're comparing apples and oranges. A share in the p2pool alt chain is worth a *lot* more than a normal diff 1 share on a normal pool. M |
|
|
|
Updated list to include FSC (fusioncoin):
To help other p2pool ops that may be interested in sharing their merged mining income, I have dedicated addresses you can send to that I'll then convert to BTC and feed back into the pool:
DVC: 1f56VqR9ajX3K42qSaDezvKXFmruSDg1B
IXC: xaNQ54gxowcwHyxqGtFM4vwCfS84V6fmKF
NMC: N1XhWNmvGhFL145zmQGQv7Vug6mThNh1iQ
I0C: jMDtRnMAk2WxaoAw8HUceMaxPPqAuZ8AEN
FSC: Fjhv8Sk8iC7AF76CTJbKo1zkHLUbTTTBs2
(I haven't given up on this yet... despite the fact that it doesn't seem be going anywhere.)
M
Are these still current and correct? Yes. M |
|
|
|
I think I'm just going to put a 24 hour delay on answering any questions related to "I didn't get a payout!" from now on....
Maybe use that time to adjust the stats API to be able to show individual worker stats instead of just by the payout address? M |
|
|
|
Unless you are running 1th rigs forgot p2pool as you will earn no where the amount you would on a normal pool... I don't necessarily agree with this statement, although I don't have empirical data to back it up. Hashrate is hashrate, it should even out in the end. Even if you don't get a share today in this block, your share will count for the next block and you would get a payout then. This is regularly stated here, however it only holds true *if* bitcoin difficulty remains the same. Which it doesn't, so therefore it's false. If your luck averages out over the difficulty period, then yes, it will. However, the lower your hashrate, the less likely it is to average out over a fixed period of time (a given difficulty period). The higher the difficulty, the worse it gets. M |
|
|
|
Any opinions?  I think I am finding a good amount of shares, its just that the blocks are not paying enough. If we had a few more blocks it would be better? ? But we really are not. 1 month ago my payouts were 0.14xxxxxxx As more hashpower is added to the pool, payouts amounts will decrease in size, but payout frequency will increase. It should balance out. Also keep in mind overall Bitcoin difficulty keeps increasing, although not quite as much per jump as it used to. M |
|
|
|
How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.
It would be great if someone could take p2pool over and make it perform better and address the issues. I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load. What do you mean by handle the load? It's at 1.81PH/s right now, share difficulty is at 6.5 million. If you've got hardware that works with p2pool, this is as good as it gets right now. M I think what flound getting at here is the diff issue as that hash rate goes up the diff will also keep rising and knocking more and more rigs off the face the earth of hitting shares unless ya running mining farms..... Think of it in terms of the BTC diff the more hash added the faster the blocks are found the higher the diff rises.... The same issue applies here to P2POOL as that hash rate keeps rising that share diff will keep going up as the find times will be faster.... What someone needs to do somewhere down the line is change the amount of shares from what is is 3000 odd per block to a larger number eg 12000 odd per block to match the rise in the hash rate on the network to bring it back down diff wise on the shares to gave the smaller miner a chance of hitting the shares as they once were able to do when the hash rate was low..... How do that has been hashed and re-hashed here. If you decrease the share difficulty, you increase the time between job restarts. Right now it's at 30 seconds, which I believe is what causes the problem with S2s and likely other ASIC hardware. Those that have been with p2pool for a while will remember that it used to be 10 seconds, and it was changed to 30 seconds because 10 seconds was way too short for ASICs. I don't believe this "more hashrate means higher share difficulty means harder for smaller miners" problem is solvable with the current p2pool design. That's why I suggested a new design not that long ago. If I was single, didn't have two kids, and wasn't working on moving across the country I'd try to code my design a proof of concept, and maybe become the new p2pool author. Alas, I barely have time to do what I need to do anymore, let alone what I'd like to do.  M |
|
|
|
How's that saying go, damn if you do; damned if you don't. It appears that the larger p2pool gets the worse it is for smaller miners....quite the dilemma since it needs to keep getting bigger to stay relevant.
It would be great if someone could take p2pool over and make it perform better and address the issues. I would move Multipool's ~250TH back to BTC p2pool in a heartbeat if it could handle the load. What do you mean by handle the load? It's at 1.81PH/s right now, share difficulty is at 6.5 million. If you've got hardware that works with p2pool, this is as good as it gets right now. M |
|
|
|
|
I appeared to have got a payout. Doesn't look like it was manual.
M
|
|
|
|
So, my local node is up and running all happy, and I have a couple miners pointed to it. All I have to say is - Holy good DOA Batman! Local node DOA rates so far are well under 2%, hovering around 1.1-1..2% pretty consistently, for around 2.6Th/s. Will see how things progress over time and if all stays good I'll point all my miners to it.
Right now have 6 outbound peers, 0 in until we get the DMZ openings done. Seems to be working fine without opening it so far.
So, silly n00b P2Pool question - if I use the same mining address as I switch pools, will the share history cross over? I've been mining on coincadence and have obviously much share history there, will it transfer so I don't have any gaps in my earnings?
Share history is based on your shares in the alt chain ... so yes, it'll follow you. M |
|
|
|
Take a look at my graph. The guy averaging at 157GH/s found two shares while I, averaging at 1TH/s found none. My Antminer interface shows I just found a share with 13,352,425 difficulty but that's not displayed.
Looks like you got some shares finally? Don't forget there are stales here. They suck when it happens, especially if you wait a day for a share, but they do happen. M |
|
|
|
|
Show Posts
