# Checkpoints as a Service

Due to [NestBFT](/docs/canopy-network/core-features/nestbft.md)'s Verifiable Delay Function mechanism, Canopy is uniquely resilient to [Long-Range-Attacks](/docs/canopy-network/core-features/nestbft/pos-is-trusted.md#whats-a-long-range-attack).

{% hint style="info" %}
You can learn more about Long-Range Attacks in the Canopy [white paper.](https://canopy-network.github.io/whitepaper/The%20Blockchain%20Incubator%20Model_%20Bridging%20Dependent%20Applications%20to%20Autonomous%20Networks.pdf)
{% endhint %}

**Canopy extends this security to its Nested chains through decentralized checkpointing.**

Where:

1. While nested or&#x20;
2. After independence (not recommended)

Chains may utilize a Canopy root to publish succinct cryptographic proofs of blocks of the chain — enabling proper 'fork-choice' selection when under attack.&#x20;

***

The core feature of being a decentralized 'checkpointing-as-a-service' provider...

* Enhances Canopy chain security by offering decentralized access to critical information
* Helps thwart **Long-Range Attacks** by ensuring chains can verify past states
* Enables **subjectivity** even under adversarial conditions, preventing attackers from rewriting history

{% hint style="info" %}
When a chain goes independent, checkpoints may be exported at their convenience to move to another provider or method. 🤝 Chains are never locked with Canopy, and history is always preserved.
{% 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://canopy-network.gitbook.io/docs/canopy-network/core-features/checkpoints-as-a-service.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.
