XPlotter for optimized plots (CPU)
-
@AngryChicken I've just recently assigned this pool. Should I just wait it out? Still no confirmations.
-
@k.coins It's up to you to be honest. I would let the admin of this pool know whats going on so they can address the problem. I my self use http://pool.burstcoin.eu/ because I know how to get a hold of the admins and they are usually on top of any problems. But pools are pools they all have problems once and a while. Besides I checked your pool and it looks like they have been processing your DL's
EDIT: Yea just look what happen 5 hours ago at my pool https://forums.burst-team.us/topic/3071/eu-pool-forked (Nothing big)
-
@AngryChicken I just came back to a screen full of NOT confirmed DLs and Really Bad deadlines... Since it's probably not the plots, maybe I'll post more questions somewhere else.
Now I'm wondering, can conflicts happen by mining with the same pool using two different wallets but over the same IP?
-
@k.coins Maybe @haitch can help answer that question, but to be honest I can't see why that would be an issue. But if it is the pool the problem won't be fixed until the admin check/fixes the problem. If your really in a hurry try a different pool only takes 14 mins to complete the switch.
By any means try posting your own threads lots of people love to help around here.
-
@AngryChicken Alright, thanks for the advice. I'll mess around with the pools a bit. This is a new wallet, my other wallet's plots are still reporting fine.
-
@Rendavu looks like that's a similar error to mine... I tried changing pools and it didn't fix it. Not sure what to do now... wplotgenerator?
-
@k.coins well i just start over with wplotgenerator and after i optimize it ! much faster just make small plots 1000 gb or 1500 gb
i also changed the pool to different kinds but still i get this 1007 error i think the file was corrupt because i started with the wrong nonce
-
Does the last number here in the plot's file name indicate the stagger size?
4442517158180149549_100000000_3072000_3072000
If so, I've never used a stagger that large and am wondering if this is the reason the pools are receiving such terrible (really bad) deadlines from these plots?
-
@k.coins The last number is the stagger, and if you've used Blago's new plotter - it creates optimized plots, so the stagger is correct.
-
@haitch So no ideas on what could be up with the pools reporting crazy deadlines back to us?
I just deleted it and started a new one with XPlotter at 100000000 instead of 100000001. Not sure why this would matter but I figured I'd give it one more try anyway.
-
@k.coins Don't know why the crazy deadlines come up - the pool and the miner should be using the same algorithm to determine the deadline - I don't know why the miner thinks it's good and the pool thinks it's bad. I've had a number of them as well, and couldn't find anything to explain it.
-
@haitch Fair enough. So no go on the new plotter for you?
-
@k.coins I've used it without problems, and have another 5TB to plot - will be using the new plotter.
-
@haitch Wait.... so your plots are working? Should I just keep trying to report to the pool even though all I receive back are really bad deadline warnings?
-
@k.coins Yeah, mine are fine, but have been done with a variety of plotters. Check the log files - determine which plot file they're coming from and recreate it.
-
@haitch Alright, word. I am just trying to get this new plot I made with XPlotter to work. It seems to be the only plotter that has given me this problem.
-
@k.coins I've got another 5TB to plot - I'll use the new plotter and see how it goes.
-
I have a couple of retries but still having the deadline problem, went back to wplotter and optimizer. no more problems.
-
@Yey_09 perhaps you could switch pools to see if its just the pool your mining on?
-
@ZapbuzZ I've tried switching pools - didn't help anything, still getting really bad DLs back from them.


