0
Under review

Concerns about CF

Mul Vak 6 years ago updated by Oliver 6 years ago 4

Granted I am new.  CF is recommended around the web as being a solid, new user friendly pool.  I get there are issues with XMR, where you are hosting, Verge hack last week, among I am sure a ton of other things involved in running a pool.  I do feel for you running this solo. 


So I built/bought 4 rigs.  3 are GPU, 1 ASIC.  I mine ETH (Dwarfpool) on one GPU rig, 2X XMR GPU (Coinfoundry) and testing ASIC Antminer D3 here for Dash.


In one month I have almost $100 in ETH in my wallet. (Dwarfpool)

In one month I have ZERO XMR in my wallet. (Coinfoundry)

Dash too early to say.


Now to be fair two things happened, first I changed wallets and Oliver graciously offered to transfer that work to my new wallet. https://feedback.coinfoundry.org/communities/1/topics/875-switching-wallets-what-do-you-with-remaining-amount-in-pool


Then the Monero fork.


I did post a private message and email and I have not heard a thing.  I have over 3.1B share on the old, and just hit 1.1B on the new.  So that is about 4.2B, likely due for a payout when we get the next block.


So I guess the bottom line is it seems like this may be too much for one person to handle?  I really like the idea of supporting a smaller pool, but there is no daily update/news (maybe I missed something but twitter seems the only thing), you need to dig around in posts to find out scraps of what is going on.  From a new user's eye, I read a lot of the posts and think wow this is too much trouble.  I'm happy you have some good twitter metrics, but one minute to just respond would be nice.


I'm hooked on mining, I've got free electric and resources to bring up mining rigs.  I really like the idea of CF and will support what you got going but like everyone I am mining for the coin.


I'll apologize in advance if I am off base or unfair, I do not intend this to be.  I just would like a better feeling about sticking around.


Thanks

+3

I've tried several pools. This is the only one where I hear anything from the admin. He's on here every day. He replies to all posts. I get what you are saying. Mining ETN and now XMR has been frustrating for me too. I don't blame Oliver for any of the problems. 


Check out each coin on this pool. Look at the total coins mined. Convert to $ and multiply by 0.0075 (it used to be less).  It isn't enough to run this site. 



Under review

@Mul Vak: I completely understand your concerns and I don't think anything you wrote is unfair, especially regarding the XMR Pool which depresses me to no end. Let me elaborate a bit ...


When comparing CF to giants like DwarfPool one factor is playing a big role: variance. Both our XMR and ETH pools are absolutely tiny in comparison, which results in higher variance in block times. For the ETH, it is at least regulary finding blocks and paying out instantly. I haven't heard any complaints towards the ETH pool so far. Same for the Dash pool (except for the rocky start back then in Mid 2017). Now to the XMR pool. This is what I've tried so far without success:


  • Switch back and forth between unpatched and patched versions of monerod (the XMR full-node software powering the pool)
  • Bring up a new daemon that's been synced from scratch and switch the stratum servers over to it
  • Increasing inbound/outbound connections of the daemon
  • Bumping process priority of the daemon
  • Tried different software for powering the stratum endpoints for XMR: MiningCore vs nodejs-pool (this is the software responsible for actually unlocking blocks from submitted shares)
  • Tried different commit versions of MiningCore and nodejs-pool (I'm the author of the former and I'm maintaining a fork of the latter)
  • Finally gave each stratum server its own local monerod to eliminate any latency between block updates and work getting sent to miners

None of this helped and I'm honestly on the brink of compensating miners from own money and closing down the XMR pool for good as I can't justify letting miners waste their time and money with that PoS.


Finally, regarding your ticket, I'm sorry, must have slipped through somehow. Just let me know if you still wish to have the requested changes implemented and I'll do it right now.

Thanks for the detailed reply.  Yes please move forward with the ticket and move the wallet.


I'm not looking for compensation until I normally would get it.  I don't think it is a waste of time, unless you think the work being done will not eventually lead to something.


I'm not a developer but I've worked closely with devs throughout the years, I've been a network and sysadmin and now I own a small tech company.  Just some context for my next possibly ignorant comments/suggestions.


I know troubleshooting can get you mired down in the details.  When I was thinking about this problem I was thinking "why not just setup a clean test bed and try"  you already have all these things covered and tried.  So this is the time I usually tell my guys to take a step back away from it and clear you head.  Work on something else. 


After that what fresh angle can you take.  One big thing that stands out to me on this is all the rejected work from numb-nuts who did not upgrade.  That HAS to have even some little effect.  Is it possible that what CF submits is somehow being blocked or rejected further up the line due to the massive pool rejects? 


Assuming you did this but did you take a "clean" stratum build and daemon on a clean server (virtual or otherwise) and a single clean miner and run it through? 


The basics we know are that mining software works after the fork.  Pool software (I know this is many components) work on other pools.  So if you put yourself in the mindset of a new pool operator just starting an XMR pool.  Put out of mind everything experiential you know from running a pool.  Work backwards from there.  I can't tell you how many times things appear to be setup right, logs look good, everything appears to work process wise but the end result just doesn't happen.  Then I find either a missing CR or something commented out in a config file.


I know this is superficial troubleshooting but maybe helps. 


I sincerely appreciate your response and will get back on the pool, I'll pass the word around to my small group of people who mine.  Don't shut down the XMR pool, XMR is hot now and well worth mining.  If you have to shitcan what you have now and bring up a fresh one then I can see that.  I also really feel for you on the big issue driving you nuts.  All I can say is you will find the issue and fix it.  You seem like a very competent tech/dev so it will work out.


Lastly I do have tech resources.  If you need assistance in infrastructure type stuff to help in troubleshooting I may be able to help.  Not talking about getting into your systems, but if you need some free temporary VMs or bandwidth, whatever PM me.

Thanks for your kinds words Mul Vak. Will respond in more detail tommorow. I'm currently totally exhausted after working for 13 hours straight on migrating our infrastructure over from linode to a high-performance dedicated hex-core server at hivelocity.