# Archival Node Sync Time **URL:** \ **Category:** General\ **Created:** [April 20, 2021, 2:58pm UTC](https://forum.algorand.co/t/archival-node-sync-time/3059 "2021-04-20T14:58:20Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![tsachi](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/tsachi/32/29_2.png) [@tsachi](https://forum.algorand.co/u/tsachi)\ **Post date:** [April 20, 2021, 4:41pm UTC](https://forum.algorand.co/t/archival-node-sync-time/3059/8 "2021-04-20T16:41:00Z")
When running a full catchup ( what you’re doing ), you’re validating each block against its predecessor. That’s quite a cpu and disk intensive process if you have a long running network. When you want to start off with a non-archival node, you don’t really need the entire history. You only need the recent 1000 blocks as well as a copy of the accounts state. Catchpoints labels are the hash of that state. They allow you to use the catchpoint catchup ( sometimes referred to as “fast catchup” ), which does the exact opposite - rebuild the hash from the data, and make sure it’s matching your expected hash. If you’ll ever need to want to catchup another node, you don’t need to trust anyone - you can use your own archival node that already calculated the “correct” catchpoint label. --- _[View the full topic](https://forum.algorand.co/t/archival-node-sync-time/3059)._