<p>Of course it isn't synced if you haven't mined blocks in a while. The assumption with networks similar to Bitcoin (and thus Dash) is that mining is constant so if a node sees that its most recent block is old, it will assume that it is not synced.</p>

<p>The RPC calls will check to see if you are synced and then only serve data to mining software if it is. You can just disable this check in the source code so that you can mine again.</p>

CC BY-SA 3.0
2018-02-23T05:08:48.753Z
2018-02-23T05:08:48.753Z
Ava Chow
<p>My suggestion (I do not know about Dash specifically), if there are no new blocks for a timeout period the node thinks it is behind. This is certainly the case with some (non-Dash) clients.</p>

CC BY-SA 3.0
2018-02-17T06:59:56.593Z
Thanks for your response. Same rules apply here i believe. I just don't know how I'm supposed to mine a new block when it won't allow it.
Chris_Null
CC BY-SA 3.0
2018-02-23T08:11:02.120Z
@sic_null Reset your time clock to just after the last block was mined.
Willtech
CC BY-SA 3.0
2018-02-17T06:52:46.830Z
2018-02-17T06:52:46.830Z
Willtech
<p>Okay, I cloned a Dash source (learning)</p>

<p>Compiles fine on Linux/Win, I have peers and it was mining blocks fine during the initial launch. 200 Blocks mined, all peers sync'd up fine, sent Tx between one another. Everything works perfect. </p>

<p>I killed mining on it as there was no need for me to keep mining it (just learning) but I have found that since then, It will not sync, at all. Is constantly showing "catching up" What I have tried:</p>

<ul>
<li>Rescan</li>
<li>Reindex</li>
<li>Tried a different machine</li>
<li>Let it sit for hours. </li>
</ul>

<p>Nothing moves sync wise and it no longer will load any blocks after reindex (stays at zero). I figured it was related to no hashrate but I can't mine anything on it since the wallet isn't synced (i'm assuming). The error i get trying to mine is </p>

<pre><code>json_rpc_call failed w/cpuminer 
</code></pre>

<p>setgenerate will only show 0 hash</p>

<altcoin>
Syncing Issues - Hashrate?
Chris_Null
# Syncing Issues - Hashrate?

(Asked by: username_0 on 2018-02-17)

Okay, I cloned a Dash source (learning)
Compiles fine on Linux/Win, I have peers and it was mining blocks fine during the initial launch. 200 Blocks mined, all peers sync'd up fine, sent Tx between one another. Everything works perfect. 
I killed mining on it as there was no need for me to keep mining it (just learning) but I have found that since then, It will not sync, at all. Is constantly showing "catching up" What I have tried:

Rescan
Reindex
Tried a different machine
Let it sit for hours. 

Nothing moves sync wise and it no longer will load any blocks after reindex (stays at zero). I figured it was related to no hashrate but I can't mine anything on it since the wallet isn't synced (i'm assuming). The error i get trying to mine is 
json_rpc_call failed w/cpuminer 

setgenerate will only show 0 hash

**Tags:** altcoin


---

## 2 answers

### Answer by username_1 on 2018-02-23. Score: 1

Of course it isn't synced if you haven't mined blocks in a while. The assumption with networks similar to Bitcoin (and thus Dash) is that mining is constant so if a node sees that its most recent block is old, it will assume that it is not synced.

The RPC calls will check to see if you are synced and then only serve data to mining software if it is. You can just disable this check in the source code so that you can mine again.


---

### Answer by username_2 on 2018-02-17. Score: 0

My suggestion (I do not know about Dash specifically), if there are no new blocks for a timeout period the node thinks it is behind. This is certainly the case with some (non-Dash) clients.

> **Comments:**
> **username_0**: Thanks for your response. Same rules apply here i believe. I just don't know how I'm supposed to mine a new block when it won't allow it.  
> **username_2**: @sic_null Reset your time clock to just after the last block was mined.  

---

