# Sync with State-Sync

The Cosmos SDK includes a feature called State-sync which facilitates rapid connection for validators to the network. By syncing with a snapshot-enabled RPC from a trusted block height, the time required to join the network is reduced from several days to mere minutes.

However, the drawback of this approach is that the node will only have access to the most recent state stored by the state-sync RPC and not the complete transaction history. On the positive side, the database size is much smaller compared to a fully synced node, thus using state-sync can help reduce operating costs by minimising storage usage. Furthermore, when syncing with the network using State-Sync, a node can bypass the need for upgrading procedures and simply sync with the most recent binary version.

{% hint style="warning" %}
For nodes that are intended to serve data for dApps, explorers or any other RPC requiring full history, state-syncing to the network would not be appropriate.
{% endhint %}

### Mainnet state-sync

State-sync with [Polkachu](https://polkachu.com/state_sync/migaloo)\\


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.migaloo.zone/validate/join-the-mainnet/sync-with-state-sync.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.