# Restore old 2018/19 Wallet.dat with Zcash Node

**URL:** <https://forum.zcashcommunity.com/t/restore-old-2018-19-wallet-dat-with-zcash-node/49701>\
**Category:** Zcash Apps\
**Created:** [December 12, 2024, 12:32pm UTC](https://forum.zcashcommunity.com/t/restore-old-2018-19-wallet-dat-with-zcash-node/49701 "2024-12-12T12:32:32Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Shawn](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/shawn/32/187_2.png) [@Shawn](https://forum.zcashcommunity.com/u/Shawn)\
**Post date:** [December 15, 2024, 1:41pm UTC](https://forum.zcashcommunity.com/t/restore-old-2018-19-wallet-dat-with-zcash-node/49701/13 "2024-12-15T13:41:49Z")

</div>

You are likely hitting the time of the spam attack, it will appear frozen but it is working.

Unfortunately Zcashd sync is not multi threaded so you have to wait for it to crunch through.

> [@Heavily increased transaction load since June 14](https://forum.zcashcommunity.com/t/heavily-increased-transaction-load-since-june-14/42349):
>
> I find it strange there’s no serious discussion about this neither from users nor from protocol devs (could be that I massively overlooked some threads), but the chain has been seeing an increased load of transactions since June 14, resulting in huge blocks: daily average block size in the past 1 year (source: [https://bitinfocharts.com/comparison/size-zec.html#1y](https://bitinfocharts.com/comparison/size-zec.html#1y)) the only higher historical value was in April 2017, but that load wasn’t sustained for this long. taking a look at the r…

---

_[View the full topic](https://forum.zcashcommunity.com/t/restore-old-2018-19-wallet-dat-with-zcash-node/49701)._
