Bitcoin Forum
June 13, 2024, 07:45:50 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: High Number of Rejects  (Read 471 times)
RicRock (OP)
Sr. Member
****
Offline Offline

Activity: 290
Merit: 250



View Profile
September 16, 2013, 04:46:35 AM
 #1


I've got a few BE's and Blades that I've been using to mine various Alt Coins.

I get a very large number of Rejects and I believe it's due to expiry and scan time settings of my instance of bfgminer.

Does anyone have some tips? Maybe it's the pool?
iGotSpots
Legendary
*
Offline Offline

Activity: 2548
Merit: 1054


CPU Web Mining 🕸️ on webmining.io


View Profile WWW
September 16, 2013, 04:50:32 AM
 #2

What coins are you mining?

RicRock (OP)
Sr. Member
****
Offline Offline

Activity: 290
Merit: 250



View Profile
September 16, 2013, 05:21:37 AM
 #3


ZET and TRC mainly
bitcoinreactor
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
September 16, 2013, 05:24:10 AM
Last edit: September 16, 2013, 05:47:51 AM by bitcoinreactor
 #4

GBT / stratum ?
Using getwork for such rapid coins makes no more sense, your miner will get notified of new blocks way too late, leading to this high number of rejected submits

BTC: 17CHqn3XE3Waf7Qfkm9p2MQE1VgB8gVbG4
RicRock (OP)
Sr. Member
****
Offline Offline

Activity: 290
Merit: 250



View Profile
September 16, 2013, 06:02:29 AM
 #5


Sorry for the lack of that info.

I am using stratum pools
bitcoinreactor
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
September 16, 2013, 06:07:45 AM
Last edit: September 16, 2013, 06:25:55 AM by bitcoinreactor
 #6

i'd then personally contact the pool admin an ask him if he uses a blocknotify command instead of just relying on gbt data to detect new blocks.
(This should be quite obvious to any pool admin, but .. )

If he does not use blocknotify to notify his pool of new blocks, his pool just "wait" for the next getblocktemplate call to detect new blocks, what will lead to late detections.

note that if this pool have a poor connectivity to the coin network, using blocknotify will not change anything : his pool will always get notified way too late.
The first basic check you can do is try to find if at least one of the pool TRC|ZET daemon nodes have opened p2p ports (otherwise he will rely on outbound connections to detect new blocks, adding quite some time to the process).

Then, if choosen pool
* does not use blocknotify
* or have no open TRC|ZET p2p port opened,
just switch to another pool Smiley

BTC: 17CHqn3XE3Waf7Qfkm9p2MQE1VgB8gVbG4
RicRock (OP)
Sr. Member
****
Offline Offline

Activity: 290
Merit: 250



View Profile
September 16, 2013, 06:35:31 AM
 #7

Then, if choosen pool
* does not use blocknotify
* or have no open TRC|ZET p2p port opened,
just switch to another pool Smiley



Very helpful, Thanks!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!