# Subsidies

Subsidization is the rewarding of participants through a native asset. While Nested Chains may be automatically [subsidized](/docs/canopy-network/canopy-economics/staking.md#committee-subsidization) by the protocol through new mint — Canopy comes pre-built with manual Subsidization functionality.

This means that anyone from community leaders to average patrons may donate tokens on the [Security Root](/docs/canopy-network/core-features/peer-to-peer-security.md) to ensure participants are appropriately compensated for their efforts.

### A Competitive Fee Market

Similar to **Gas Fees** in Ethereum, additional subsidization may be the norm at Canopy's maturity. Specifically, the economic barrier for a chain to get security services on a root may be dictated by the market conditions of the Security Root at any given time. However, unlike Ethereum, the risk of Security Root monopoly is greatly diminished through the Peer-to-Peer architecture of Canopy, where each chain is expected to offer Security Root functionality. This allows the market to naturally ebb and flow through cycles of high and low demand.

### Life After Minting

Subsidies allow the system to continue functioning after supply inflation ends (in many decades). The community can simply patronize the chains it wishes to support through subsidization, effectively replacing the mint incentive once the final halvening occurs. This future vision takes great inspiration from Bitcoin’s sustainability model, promoting an ecosystem where long-term security is maintained through voluntary economic participation rather than perpetual inflation.


---

# 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/canopy-economics/subsidies.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.
