# Peer-To-Peer Security

Canopy Network's stack is recursive and self-reinforcing in nature:

1. New chains launch under a **Security Root** chain that alleviates the [cold start problem](/docs/canopy-network/why-canopy/background-and-industry-state.md#are-hard-to-launch) of L1s by:
   * Utilizing the Total Locked Value (TLV) to prevent hostile takeover
   * Provides interconnection with its ecosystem
   * Lends its diverse validator set for decentralization
   * Enables instant liquidity through token swaps to chains outside of the ecosystem
   * Cross-pollinate tokens through block rewards
2. Once matured or independent, **they become security roots to seed the next generation**:
   * See point 1 

<figure><img src="/files/sRl5k8j8Pbf2SUeLJyAS" alt=""><figcaption></figcaption></figure>

This stack adopts the ease of [Ethereum's dApp model](/docs/canopy-network/why-canopy/comparables/ethereum.md#what-is-ethereum) but couples it with the true independence of a L0 and fortifies the security mesh with each new blockchain that is added.&#x20;

{% hint style="warning" %}
Hint: Because Canopy enables a mesh of L0 peers - this design addresses the [Monolith](broken://pages/WmNCvttUJghV81UCMYRc) problem too!
{% 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/peer-to-peer-security.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.