Why Tokenized Stocks Need Portfolio-Native Lending

Tokenized stocks are not only assets to trade.

Their bigger opportunity is collateral.

If equities, ETFs, commodities, and other real-world assets are moving onchain, users should be able to do more than buy and sell them. They should be able to borrow against them, combine them with crypto collateral, and manage them as part of one portfolio.

That requires a lending engine built for heterogeneous assets from day one.

Trading is only the first use case

The first wave of tokenized stocks naturally focuses on access and trading.

Can users buy tokenized exposure? Can they transfer it onchain? Can they use it in DeFi? Can liquidity form around it?

Those are important questions. But once the assets exist onchain, the next question is obvious:

Can these assets become productive collateral?

If the answer is yes, tokenized stocks become part of the credit layer.

Why RWAs are different from crypto collateral

Real-world assets bring different risk assumptions.

Tokenized stocks may have different trading hours, liquidity profiles, oracle behavior, issuer constraints, custody structures, and regional access rules. They do not behave like SOL, ETH, or USDC.

A protocol should not force them into a generic crypto collateral model. It should also not isolate them so aggressively that they become unusable.

The right answer is more nuanced: allow the assets where the risk relationship makes sense, and stay conservative where it does not.

The portfolio use case

Consider a user who holds:

• tokenized S&P 500 exposure;
• tokenized Nvidia;
• SOL;
• USDC.

The user wants to borrow USDC without selling long-term holdings.

In a fragmented system, each asset may belong to a different market or receive crude treatment. The user may need to split capital, accept worse borrow power, or avoid using certain assets entirely.

In a portfolio-native system, the account can be evaluated as one collateral basket.

Asset basket

Equities + crypto

Pairwise rules

Risk parameters

Liquidity

USDC credit

Tokenized stocks become more useful when they can participate in portfolio-native borrowing.

Pairwise risk is essential here

Borrowing USDC against tokenized treasuries is not the same as borrowing SOL against tokenized Tesla.

Borrowing against a diversified equity basket is not the same as borrowing against one high-volatility stock.

Pairwise risk lets the protocol express these differences. Some collateral/debt pairs can be efficient. Some should be conservative. Some should be disabled.

That flexibility is what makes RWA lending credible.

Collateral	USDC debt	SOL debt	RWA debt
USDC collateral	84%	62%	48%
SOL collateral	70%	58%	42%
Equity collateral	55%	38%	34%

The exact values here are illustrative. The primitive is the shape: collateral quality is defined relative to the debt asset.

Why Zodial fits this market

Zodial is not trying to bolt tokenized assets onto a single-asset lending model.

The protocol is designed around portfolios. It can evaluate crypto, stablecoins, and tokenized real-world assets through pairwise risk relationships and a portfolio-wide health engine.

That matters because the future onchain user will not hold only one asset class. They may hold SOL, stablecoins, tokenized equities, commodities, and yield-bearing assets in the same wallet.

The lending layer should be able to understand that.

What users get

For users, portfolio-native RWA lending can unlock:

• liquidity without selling tokenized stocks;
• collateral use across asset classes;
• more natural portfolio management;
• better recognition of stable buffers and diversification;
• new strategies that combine crypto-native assets with real-world exposure.

None of this removes risk. But it makes the risk model more aligned with the actual portfolio.

Takeaway

Tokenized stocks need a lending layer that understands relationships between assets.

Zodial’s portfolio-native model is built for exactly that: heterogeneous collateral, pairwise risk, and one account-level view of solvency.