> For the complete documentation index, see [llms.txt](https://docs.shadeprotocol.io/shade-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadeprotocol.io/shade-protocol/advanced-topics-apps/silk/minting-and-redemption.md).

# Minting & Redemption

SILK minting methods

Minting a stablecoin is the act of issuing a token that ultimately takes the form of a liability that the protocol must answer for at a later time via redemption or sale of the stablecoin for a corresponding amount of underlying promised value. **The incentive for a protocol to issue a liability in the form of stablecoin to a user is on the basis of revenue received from the user for the service provided.** With SILK, users repay Shade Protocol for the service provided primarily via interest payments as well as liquidation profit-sharing. SILK uses a hybrid model utilizing the following stability and minting mechanisms:

| Method                     | Description                                                                                                                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Overcollateralized Minting | A minting model that follows the tried and true collateralized lending of MakerDAO. An overcollateralized amount of volatile assets back a finite set of stable assets via a process of interest payment incentives and liquidations. |
| Collateral Redemptions     | A redemption mechanism whereby SILK is redeemed against tranches of at risk lending positions.                                                                                                                                        |
| Bonds                      | A mechanism whereby the protocol can repurchase or issue SILK at a discount or premium to help grow the treasury as well as maintain stability of the SILK peg.                                                                       |

### Stability Principles

With many different stability mechanisms available for Shade Protocol, there becomes a need to address the collateralization philosophy of the protocol with respect to what stability and minting mechanism are most heavily relied on over the lifespan of the protocol.

The following are a set of stability principles for Shade Protocol:

* Stability > Growth 
* SILK > SHD
* Commerce creates stability
* Build reserves for unforeseen future bad debt
* Diversify where SILK is used in DeFi
* Openly plan for the failure of SILK
* Openly plan prevention steps in event of peg failure
* Natural pessimism towards bridging solutions
* Natural pessimism about quality of assets backing SILK
* Recommended that collateralization ratio of SILK targets 90 - 150%


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shadeprotocol.io/shade-protocol/advanced-topics-apps/silk/minting-and-redemption.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.