Bitcoin Forum

Other => Beginners & Help => Topic started by: BathoryAria on February 15, 2018, 06:16:17 AM



Title: How to prevent Rejected Shares?
Post by: BathoryAria on February 15, 2018, 06:16:17 AM
Hello, pretty new to all of this. Im mining ZEC with EWBF on Nanopool. And per day i usually can get 2500 accepted shares and ill usually get like 5-8 rejections. Not sure what casues this, and how can i go about fixing it? Thanks


Title: Re: How to prevent Rejected Shares?
Post by: HabBear on February 15, 2018, 06:48:51 AM
Hello, pretty new to all of this. Im mining ZEC with EWBF on Nanopool. And per day i usually can get 2500 accepted shares and ill usually get like 5-8 rejections. Not sure what casues this, and how can i go about fixing it? Thanks

Great question! But this is the wrong board to get the level of expertise you're seeking. You should post this thread to the Mining Support board (in the Mining section). Once there you will find many more mining experts that can offer a wider variety of qualified opinions.

You'll find the Mining Support board HERE. (https://bitcointalk.org/index.php?board=40.0)


Title: Re: How to prevent Rejected Shares?
Post by: mocacinno on February 15, 2018, 10:42:41 AM
In general, there are only a couple things you can do to get a lower rejected share %:
1) make sure you have up-to-date firmware/mining software
2) make sure your network connectivity is OK... Maybe switch to a pool with a lower ping latency?

Getting a rejected share once in a while is normal, usually it's a stale or a duplicate share... I wouldn't worry about the numbers you indicated in your OP, they seem well within bounds to me.



Title: Re: How to prevent Rejected Shares?
Post by: bicoin110 on February 16, 2018, 08:26:18 PM
Hello, pretty new to all of this. Im mining ZEC with EWBF on Nanopool. And per day i usually can get 2500 accepted shares and ill usually get like 5-8 rejections. Not sure what casues this, and how can i go about fixing it? Thanks

This problem occurred when your connection or the database connection failed. so do not warry it is natural