# 4.4.1 RSD/USD Soft Peg

While not relying on a “hard” pegging mechanism as described above, RSD does provide a “soft pegging” mechanism, allowing its holders to use the US Dollar as a reference when pricing goods and services in RSD. This soft peg is supported by the following factors:&#x20;

1. RSD deficits convert 1:1 into debt denominated in US dollars if not paid in time.&#x20;
2. Staking requirements and transaction fees are paid in SOURCE, but are calculated using USD as a reference. If a 1000 RSD credit line requires a 20% SOURCE stake to be underwritten, this 20% will be calculated using the SOURCE/USD price as a reference. Meaning that a 1000 RSD credit lines would require a $200 stake, payable in SOURCE only. The same holds for transaction fees, which are paid in SOURCE but are denominated as a percentage of the transacted RSD amount.&#x20;
3. SOURCE reimbursements paid to RSD savers are likewise calculated as if 1 RSD equals 1 USD.

This “carrot and stick” arrangement organically drives members to regard their RSD balances, positive as well as negative ones, as akin to USD balances, and consequently to price their goods and services within the network accordingly.&#x20;

It should be noted however, that this soft peg is not an absolute necessity. It is completely possible to run instances of ReSource protocol in which the network’s stable credit is completely de-tethered from any external asset.


---

# 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://resource-network.gitbook.io/resource-technical/04-monetary-flow-reserves-default-insurance/4.4-rusd-on-the-open-market-1.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.
