# Capital Efficient Restaking

Unlike protocols that require the new chain to stake tokens to receive security services, Canopy onboards chains through social consensus of the Validators, powered by **Restaking**.

{% hint style="info" %}
Using the same stake for multiple chains is capital efficient&#x20;
{% endhint %}

<figure><img src="/files/WI08NrcB1zbk0l3Yu35D" alt="" width="375"><figcaption></figcaption></figure>

Here's how it works:

* Validators may opt-in to provide security to any Nested Chain by using their existing locked tokens as collateral. This means that **supporting a new chain requires no additional stake.**&#x20;
* Staking for a Nested Chain earns Validators the Nested Chain native token.
* Additionally, Validators earn the Security Root token if a Chain has committed stake above the *StakePercentForSubsidizedCommittee* parameter.
* The amount of chains per Validator is limited only by the Security Root DAO&#x20;

In other words, Nested Chains receive security services **through community-driven popularity rather than financial investment**, significantly lowering the barrier to entry for new chains.

{% hint style="warning" %}
No competition for block space - no gas fees - no economic barriers!
{% 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/capital-efficient-restaking.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.
