> For the complete documentation index, see [llms.txt](https://canopy-network.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canopy-network.gitbook.io/docs/canopy-network/core-features/checkpoints-as-a-service.md).

# 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 
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. 

***

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 %}