The RWA Yield Infrastructure Trade

RWA2,19%
KMNO-1,62%
MORPHO-0,11%
FLUID-3,7%

What to know:

  • Direct RWA token exposure doesn’t work. The economic value from tokenization accrues to curators and issuers, not governance tokenholders - Kamino’s 80% deposit growth alongside a 16% token decline is the cleanest proof of this.
  • The leverage problem is the most interesting infrastructure opportunity. RWA settlement delays (up to 122 days of exit exposure) make atomic crypto-native looping strategies impossible to replicate, creating a structural gap that protocols like Keyring and 3F are building toward - but neither has a liquid token yet.
  • Morpho is the prime institutional borrow layer, but the token thesis is contingent on a fee switch the Association has no structural incentive to flip. $6.8B TVL and $120.9M in annualized fees exist entirely for depositors and curators - MORPHO tokenholders currently capture zero of it.
  • Fluid is the cleaner token expression of the same thesis, albeit more indirect. Dominant DEX volume share for key RWA-adjacent stablecoins (100% of sUSDai, 87% of syrupUSDC, 68% of reUSD), a revenue-linked buyback mechanism, and structurally cleaner governance make it the more compelling tokenholder vehicle - but its RWA exposure runs through yield-bearing stablecoins rather than direct tokenized asset markets.
Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments