đź““
đź““
đź““
đź““
Old ReSource Whitepaper V1.0
Search…
đź““
đź““
đź““
đź““
Old ReSource Whitepaper V1.0
00 Glossary
01 Executive Summary
02 Mutual Credit
2.1 Definitions and Rationale
2.2 History
2.2.1 WIR Bank
2.2.2 Modern Multilateral Barter Networks
2.3 Mutual Credit on the Blockchain
2.4 The Basic Economic Questions for DLT-based Mutual Credit Systems
03 The ReSource Protocol
3.1 Introduction
3.1.1 Distributed debt collection and obligation enforcement
3.1.2 Distributed risk management
3.2 Underwriting and risk assumption
3.2.1 The Underwriting process - a breakdown
3.3 Ambassadors and network administration
3.4 Monetary Flow , Reserves and Default Insurance
3.4.1 Default Insurance
3.4.2 SOURCE Reserve and stable coin pegging mechanism
3.4.3 rUSD on the Open Market
3.4.4 SOURCE Token Dynamics
04 Protocol and Network Governance
04 Protocol and Network Governance
4.1 Reputation
4.2 SOURCE Governance Token
4.3 Initial SOURCE Allocation and Distribution
Powered By GitBook
3.4.4 SOURCE Token Dynamics
SOURCE is the governance token of the ReSource protocol and will, as elaborated above, be used to underwrite debt accounts and pay network fees. For an overview of the SOURCE token supply and distribution, please refer to the chapter titled “SOURCE Governance Token” below.
The chart below depicts the flow of SOURCE between the market and natural monetary sinks within the ReSource Network.
The ReSource Network consumes SOURCE through: 1. The payment of fees by members, 2. Staking requirements imposed on underwriters. The ReSource Network emits SOURCE to the market via: 1. Staking rewards paid to underwriters, and 2. The purchasing of rUSD to maintain its peg to cUSD (or, alternatively: via reimbursing rUSD holders in the form of rUSD to SOURCE conversions as explained in chapter 3.4.1). Excess SOURCE, that are not currently required to monetarily stabilize rUSD, are sequestered within the network’s Reserve.
‌It is important to note that fee payments and staking requirements are both facilitated via SOURCE payments but denominated in rUSD. For example: a member might be obligated to pay a 3% transaction fee. This fee is denominated in rUSD, but will be paid in SOURCE. I.e, a 100 rUSD transaction will entail 3 rUSD fee, which will be paid in SOURCE.
If the current SOURCE price is SOURCE=3cUSD, one SOURCE will be consumed by the transaction. If the price of SOURCE drops to 1 SOURCE=1 cUSD, 3 SOURCE will be consumed by the transaction, etc.
Likewise, staking requirements are denominated in rUSD. If an underwriter is, for example, obligated to stake 20% of a credit line’s maximum overdraft amount, they would be required to stake 200 rUSD worth of SOURCE to underwrite a credit line of up to 1000 rUSD. I.e, 100 SOURCE in case that SOURCE price equals 1 SOURCE=2 rUSD. Consequently, if the price of SOURCE rises above 2 rUSD, the staking contract will pay out the excess SOURCE as staking rewards until the locked SOURCE equals 200 rUSD again. Vice versa, if the SOURCE price sinks below 2 rUSD, the staking contract will withhold staking rewards until locked SOURCE equals 200 rUSD again.
This way fee payments and staked SOURCE serve as a monetary buffer that smoothens the SOURCE supply and keeps it primarily influenced by the size and transaction volume of the ReSource Network.
For more information about SOURCE allocation, distribution, and supply, please refer to chapter 4.3 - “Initial SOURCE Allocation and Distribution”.
03 The ReSource Protocol - Previous
3.4.3 rUSD on the Open Market
Next - 04 Protocol and Network Governance
04 Protocol and Network Governance
Last modified 8mo ago
Copy link