# Step 4.6 Add checkpoint URL

### What is a checkpoint URL?[​](https://www.staderlabs.com/docs-v1/Ethereum/Node-operator/permissionless-node-operator/node-registration-and-adding-validators/Step%204:%20Configure%20Stader%20services/step-4.6-add-checkpoint-url#what-is-a-checkpoint-url) <a href="#what-is-a-checkpoint-url" id="what-is-a-checkpoint-url"></a>

In the Ethereum proof-of-stake (PoS) network, a checkpoint URL refers to a specific location or endpoint that provides information about the latest checkpoints in the beacon chain. Checkpoints serve as reference points or milestones in the chain, indicating the state of the blockchain at a particular block height.

These checkpoints are crucial for validators to synchronize their local copy of the blockchain with the network and participate in the consensus process effectively. Validators can compare their local checkpoints with the checkpoints obtained from the URL to ensure they are on the correct chain and make informed decisions during block proposal and validation. [*Learn more*](https://lighthouse-book.sigmaprime.io/checkpoint-sync.html)

### How will adding a checkpoint URL help me?[​](https://www.staderlabs.com/docs-v1/Ethereum/Node-operator/permissionless-node-operator/node-registration-and-adding-validators/Step%204:%20Configure%20Stader%20services/step-4.6-add-checkpoint-url#how-will-adding-a-checkpoint-url-help-me) <a href="#how-will-adding-a-checkpoint-url-help-me" id="how-will-adding-a-checkpoint-url-help-me"></a>

By utilizing the checkpoint URL, your client can instantly copy the most recent state from a trusted Consensus client that you specify. In short, it will help to synchronize your node very quickly, enabling you to stay updated with the latest blockchain state.

### **How can I get a checkpoint URL**[​](https://www.staderlabs.com/docs-v1/Ethereum/Node-operator/permissionless-node-operator/node-registration-and-adding-validators/Step%204:%20Configure%20Stader%20services/step-4.6-add-checkpoint-url#how-can-i-get-a-checkpoint-url) <a href="#how-can-i-get-a-checkpoint-url" id="how-can-i-get-a-checkpoint-url"></a>

To quickly synchronize your node, click on the link below to access the checkpoint URLs. Please make sure to copy the suitable checkpoint URL based on your selected network. If you have chosen Mainnet, copy the URL from the Mainnet section; if you have opted for Holesky Testnet, copy the URL from the Holesky section.\ <https://eth-clients.github.io/checkpoint-sync-endpoints/>

<figure><img src="https://res.cloudinary.com/dfupsth9n/image/upload/v1712213073/Ethereum/Node%20Registration/Mainnet_Checkpoint_qq7vzp.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://res.cloudinary.com/dfupsth9n/image/upload/v1712213072/Ethereum/Node%20Registration/Holesky_Checkpoint_awd1yo.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://res.cloudinary.com/dfupsth9n/image/upload/v1692732056/Ethereum/image_42_qpzchb.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Adding a checkpoint URL is optional**[​](https://www.staderlabs.com/docs-v1/Ethereum/Node-operator/permissionless-node-operator/node-registration-and-adding-validators/Step%204:%20Configure%20Stader%20services/step-4.6-add-checkpoint-url#adding-a-checkpoint-url-is-optional)

* Adding a checkpoint URL is not mandatory. if it's not something you're interested in, feel free to leave it blank.
* Checkpoint URL is only to sync faster. You can continue even without a checkpoint URL, however, it make take more days to completely sync without a checkpoint
  {% endhint %}


---

# 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://stader.gitbook.io/stader/ethereum/node-operator/permissionless-node-operator/node-registration-and-adding-validators/step-4-configure-stader-services/step-4.6-add-checkpoint-url.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.