You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
YieldVault is a Soroban smart contract vault on the Stellar network that accepts USDC deposits from retail users and generates yield by allocating funds into tokenized Real-World Assets (RWAs) such as sovereign debt instruments and US Treasuries. This document describes the mathematical strategies and risk parameters governing the vault.
5
+
YieldVault is a Soroban smart contract vault on the Stellar network that accepts USDC deposits
6
+
from retail users and generates yield by allocating funds into tokenized Real-World Assets (RWAs)
7
+
such as sovereign debt instruments and US Treasuries. This document describes the mathematical
8
+
strategies and risk parameters governing the vault.
6
9
7
10
---
8
11
9
12
## 2. Core Mathematical Strategies
10
13
11
14
### 2.1 Share Price Model (ERC-4626 Style)
12
15
13
-
YieldVault uses a proportional share model. When a user deposits USDC, they receive vault shares (yvUSDC) representing their fractional ownership of the total vault assets.
16
+
YieldVault uses a proportional share model. When a user deposits USDC they receive vault shares
17
+
(yvUSDC) representing their fractional ownership of total vault assets.
Yield is accrued by the admin (or strategy contract in future phases) calling `accrue_yield(amount)`. This transfers real USDC into the vault and bumps `total_assets`, immediately increasing the share price for all existing holders.
46
+
There are three yield accrual paths, all of which increase `total_assets` without minting new
47
+
shares, thereby raising the share price for all existing holders.
48
+
49
+
#### 2.2.1 Admin Direct Accrual (`accrue_yield`)
50
+
51
+
The admin transfers USDC directly into the vault:
52
+
37
53
```
38
54
new_total_assets = total_assets + yield_amount
39
55
new_share_price = new_total_assets / total_shares
40
56
```
41
57
42
-
This means yield is **socialized proportionally** — all shareholders benefit instantly and equally based on their share holdings.
The vault is a single Soroban contract with no upgrade mechanism in Phase 1. All state is stored in instance storage. An audit is required before mainnet deployment (Phase 4).
173
+
Single Soroban contract with no upgrade mechanism in Phase 1. All state is stored in instance
174
+
storage. An audit is required before mainnet deployment (Phase 4).
89
175
90
176
**Counterparty Risk**
91
-
In Phase 1, yield is manually accrued by a trusted admin. In future phases, yield will be pulled from RWA issuers (e.g. Franklin Templeton BENJI, tokenized Korean bonds, US Treasuries) via strategy bridge contracts. Each RWA issuer introduces its own counterparty risk.
177
+
Phase 1 yield is manually accrued by a trusted admin. Phase 3+ yield is pulled from RWA issuers
178
+
(Franklin Templeton BENJI, tokenized Korean sovereign bonds) via strategy bridge contracts. Each
179
+
issuer introduces its own counterparty risk.
92
180
93
181
**Liquidity Risk**
94
-
Withdrawals are processed immediately against vault USDC balance. If vault funds are deployed into illiquid RWA strategies in future phases, a withdrawal queue or lock-up period may be required.
182
+
Withdrawals are processed immediately against the vault's USDC balance. If funds are deployed
183
+
into illiquid RWA strategies in future phases, a withdrawal queue or lock-up period may be
184
+
required.
95
185
96
186
**Admin Key Risk**
97
-
The current implementation uses a single admin address for yield accrual and strategy control. Phase 2 will introduce multi-sig or DAO governance to mitigate this risk.
187
+
A single admin address controls yield accrual, strategy configuration, and DAO threshold. Phase 2
188
+
introduces multi-sig or DAO governance to mitigate this.
98
189
99
190
**Oracle / Price Risk**
100
-
Phase 1 has no oracle dependency — USDC is treated as 1:1 USD. Future phases integrating non-stablecoin RWAs will require price feeds and introduce oracle risk.
101
-
102
-
---
191
+
Phase 1 has no oracle dependency — USDC is treated as 1:1 USD. Future phases integrating
192
+
non-stablecoin RWAs will require price feeds and introduce oracle risk.
103
193
104
-
## 4. Contract State Reference
105
-
106
-
| State Key | Type | Description |
107
-
|---|---|---|
108
-
|`Admin`| Address | Controls yield accrual and initialization |
0 commit comments