<p>As Erik mentioned, Daedalus is a full node and thus requires downloading the chain from peers and validating it locally on your machine. <strong>However, if you already have a trusted copy of the chain (either from previously syncing a full node or some other source), you can manually copy it into Daedalus' state directory.</strong> Doing this will speed things up because Daedalus will only have to validate the provided chain instead of downloading the whole thing from genesis. Of course, it will also have to download whatever is needed to extend the provided chain's tip to the current tip.</p>
<p>First, launch Daedalus, and click on Help &gt; Daedalus Diagnostics. Under the &quot;Core Info&quot; section, the &quot;Daedalus State Directory&quot; specifies the filepath that Daedalus uses on your computer. In this directory should be a folder titled <code>chain</code>, containing 3 subdirectories: <code>immutable</code>, <code>ledger</code>, and <code>volatile</code>, as well as 2 files: <code>lock</code> and <code>protocolMagicId</code>.</p>
<p>Next, shutdown Daedalus, then replace the 5 assets in the <code>chain</code> folder with the other 5 found in your local copy of the chain (they should all have the same filenames as mentioned above). Also, make sure the <code>chain</code> folder and files have appropriate permissions (chmod 775 for <code>chain</code>).</p>
<p>Restart Daedalus and enjoy a faster sync!</p>

CC BY-SA 4.0
2022-06-21T12:19:00.910Z
Man your Daedalus knowledge is impressive you seem to be answering all my questions. A well-deserved upvote and tick.
KryptoKing
CC BY-SA 4.0
2022-06-20T14:04:11.490Z
2022-06-20T14:04:11.490Z
zhekson
<p>Define &quot;forever&quot;.</p>
<p>Sorry, but there are no tweaks to make it faster. If there were, they would be the default.</p>
<p>Please remember that Daedalus is a &quot;full node&quot;. That means it downloads and stores the complete blockchain history, which on my full synced Linux machine uses disk store of 67 Gig for mainnet. I have not done a full sync with Daedalus recently, but I suspect it would be about 24 hours to sync.</p>
<p>There are however some thing that might help, like use a recent machine with at last 16G of RAM, use an SSD disk (which is faster than the older electro-mechanical ones, have a decent network connection.</p>

CC BY-SA 4.0
2022-06-20T05:29:49.737Z
2022-06-20T05:29:49.737Z
Erik de Castro Lopo
<p>So I started using my Daedalus Node as the node (instead of the direct build) for the cardano-cli, but it always takes forever to sync and I am wondering if I misconfigured something or if there's a better setup.</p>
<p>Can you please share your Daedalus optimisations/Configs?</p>
<p>Thanks</p>

CC BY-SA 4.0
2022-06-20T23:12:17.500Z
To help others with a similar issue, can you list for system specs and the time it has taken so far. It would be good to know your RAM size, SSD or HDD, and network speed via fast.com or similar.
MC_Brisbane - JUST Pool
<cardano-cli><cardano-node><daedalus><node>
How To Optimise Daedalus Syncing?
# How To Optimise Daedalus Syncing?

(Asked by: username_0 on 2022-06-20)

So I started using my Daedalus Node as the node (instead of the direct build) for the cardano-cli, but it always takes forever to sync and I am wondering if I misconfigured something or if there's a better setup.

Can you please share your Daedalus optimisations/Configs?

Thanks

**Tags:** cardano-cli, cardano-node, daedalus, node
> **Comments:**
> **username_1**: To help others with a similar issue, can you list for system specs and the time it has taken so far. It would be good to know your RAM size, SSD or HDD, and network speed via fast.com or similar.  

---

## 2 answers

### Answer by username_2 on 2022-06-20. Score: 2 | Accepted answer

As Erik mentioned, Daedalus is a full node and thus requires downloading the chain from peers and validating it locally on your machine. **However, if you already have a trusted copy of the chain (either from previously syncing a full node or some other source), you can manually copy it into Daedalus' state directory.** Doing this will speed things up because Daedalus will only have to validate the provided chain instead of downloading the whole thing from genesis. Of course, it will also have to download whatever is needed to extend the provided chain's tip to the current tip.

First, launch Daedalus, and click on Help > Daedalus Diagnostics. Under the "Core Info" section, the "Daedalus State Directory" specifies the filepath that Daedalus uses on your computer. In this directory should be a folder titled `chain`, containing 3 subdirectories: `immutable`, `ledger`, and `volatile`, as well as 2 files: `lock` and `protocolMagicId`.

Next, shutdown Daedalus, then replace the 5 assets in the `chain` folder with the other 5 found in your local copy of the chain (they should all have the same filenames as mentioned above). Also, make sure the `chain` folder and files have appropriate permissions (chmod 775 for `chain`).

Restart Daedalus and enjoy a faster sync!

> **Comments:**
> **username_0**: Man your Daedalus knowledge is impressive you seem to be answering all my questions. A well-deserved upvote and tick.  

---

### Answer by username_3 on 2022-06-20. Score: 1

Define "forever".

Sorry, but there are no tweaks to make it faster. If there were, they would be the default.

Please remember that Daedalus is a "full node". That means it downloads and stores the complete blockchain history, which on my full synced Linux machine uses disk store of 67 Gig for mainnet. I have not done a full sync with Daedalus recently, but I suspect it would be about 24 hours to sync.

There are however some thing that might help, like use a recent machine with at last 16G of RAM, use an SSD disk (which is faster than the older electro-mechanical ones, have a decent network connection.


---

