# 3.1 Introduction

The purpose of the ReSource protocol is to address and answer the basic economic questions for DLT-based mutual credit systems, while providing a flexible framework within which different kinds of mutual credit systems, serving a multitude of diverse use cases, can be established.&#x20;

While mutual credit systems, built on top of ReSource, may differ significantly in terms of purpose, scope, monetary dynamics, and loan policy, they all share core elements such as: 1. Endogenously created stablecoins 2. Overdraft-enabled current accounts, 3. Distributed underwriting and risk management, and 4. Distributed debt collection and obligation enforcement.

Participants may engage with the the ReSource protocol, occupying one or more of four roles:&#x20;

![](https://lh6.googleusercontent.com/beytWzkDUwIqdIWF2BJdgEbWzXzr6Jdpf5rocSFpw3YmUqeooWxda2EO2220sEUN0uqALEywgM0KmP1nAW6jwYB4OJRUxzim1cQ0Ehdn0vU_m-XqY3C9Jpeobw6FG9uU_vDZnprl)

The nature of these roles and their contribution to the ReSource protocol will be elaborated on in the following chapters. &#x20;

Naturally, as stated above, distributed risk management and debt collection are the most sensitive and novel aspects of the protocol. The general logic driving these aspects will be introduced in the following chapters below. The exact mechanics facilitating these processes, the required token economics and its implications will be elaborated in detail thereafter.    <br>


---

# 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-finance/03-the-resource-protocol/3.1-introduction.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.
