USDD tvl include sUSDD #669
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sUSDD is an ERC-4626 yield-bearing vault token, similar to MakerDAO’s sDAI.
When users deposit USDD into the sUSDD vault, the underlying USDD is burned by the protocol, and the user only receives sUSDD as the claim on the burned USDD plus accrued yield. This means:
sUSDD is not an additional circulating asset
minting sUSDD does not increase the total market cap of the USDD ecosystem
Here is an example of minting sUSDD transaction: https://etherscan.io/tx/0xd2f954622b173a8df95361506e42da5913d5a33e2bb60a3d3ea257c35a19ca2c , as you can see, the USDD was burned and sUSDD was minted
Therefore, tracking sUSDD as a separate pegged asset causes double-counting of market cap, since its underlying USDD no longer circulates independently. The correct accounting method is to treat sUSDD as a yield-bearing wrapper, not as a second stablecoin.
Given that DeFiLlama already applies the same logic to sDAI and other ERC-4626 vault wrappers, the treatment for sUSDD should be consistent. The DAI circulating supply calculation: https://github.com/DefiLlama/peggedassets-server/blob/master/src/adapters/peggedAssets/dai/index.ts
Happy to provide more technical details or documentation if needed.