Aave Horizon lets eligible holders borrow stablecoins against supported, permissioned tokenized assets. Stablecoin suppliers fund the lending side. Borrowers keep a collateral position while taking on interest and liquidation risk.
Aave Horizon combines permissioned real-world asset collateral with permissionless stablecoin liquidity. It adapts the lending workflow to assets whose holders, valuation and recovery processes differ from ordinary crypto collateral.
That makes it a useful example of tokenization becoming part of an application. The questions move beyond issuing a token: who can pledge it, which price the lender trusts and how the lender realizes value when the borrower needs to repay.
Two sides of the market have different access
Eligible holders can supply supported tokenized assets as collateral after satisfying the relevant issuer's requirements. Other participants can supply supported stablecoins to earn the market's lending return. Supplying stablecoins doesn't give them permission to borrow against an RWA position they don't hold. Horizon overview.
The collateral tokens aren't offered as assets for other users to borrow. This differs from treating every supplied asset as a general lending-market reserve. The two sides have different functions.
For a prospective borrower, issuer eligibility comes before the loan. Holding an asset in a wallet doesn't automatically make the wallet eligible for the specific Horizon reserve. The exact supported asset and its allowlist need checking.
For a stablecoin supplier, the risk isn't identical to buying the collateral fund. The supplier participates in a lending market whose repayment depends on borrowers and the market's risk controls. The yield comes through that lending relationship.
Borrowing adds a second claim on the same position
The collateral product and the lending market impose separate eligibility and risk rules.
Track collateral valuation, interest and the health of the borrowing position.
A breach can trigger liquidation under the market’s eligibility and settlement constraints.
The collateral receipt has restrictions
When a user supplies an RWA, Horizon records the collateral position through a specialized receipt token. The RwaAToken design disables ordinary user transfers and approvals, with administrative mechanisms for specific recovery or migration actions. RwaAToken documentation.
That matters for someone expecting to move the collateral position like a normal transferable token. A deposit changes the form in which the position is managed. An arbitrary transfer of the receipt isn't the intended way to transfer or sell it.
Administrative powers also need an owner and process. A recovery function can help a user who loses wallet access, while creating authority that belongs in the product's operating description. It shouldn't be confused with permissionless holder control.
Before depositing, identify the issuer restrictions and the market's access roles. The ownership claim of the original asset still matters inside the lending application, as explained in our RWA introduction.
Health factor changes even when you do nothing
A lending position compares collateral value with outstanding debt using its risk parameters. A health factor below one indicates liquidation eligibility under Aave's general framework, with market-specific mechanisms determining how a Horizon liquidation proceeds. Aave health factor and liquidations.
Consider a hypothetical single-asset position with $100,000 of collateral, an 80% liquidation threshold and $60,000 of debt. The health factor is about 1.33. Those are illustrative parameters, not current settings for a named Horizon asset.
If collateral value falls to $85,000 and debt rises to $70,000, the health factor becomes about 0.97. The holder hasn't sold the fund, but the borrowing position has crossed the simplified liquidation boundary.
The debt can rise through interest. The collateral can change through market value, fund income or a revised reported price. A position needs monitoring even when the holder takes no new action.
Fund yield doesn't guarantee a positive carry
A borrower may expect the fund's income to exceed the borrowing cost. That comparison needs net returns, a matching time period and any transaction or liquidation-related costs.
Borrowing rates can change as the stablecoin pool's utilization changes. A fund's reported trailing yield measures a different period from the current loan rate. Comparing them as fixed numbers can overstate the expected spread.
Leverage can also change the risk profile. If borrowed funds buy more collateral, the user creates a larger exposure and another debt-financed dependency. The underlying asset's ordinary cash-management risk doesn't describe the whole leveraged position.
The tokenized Treasury comparison identifies product-level income and redemption differences. Horizon adds a loan whose terms need a separate calculation.
A reported NAV isn't an executable sale
Some RWA assets use issuer-reported net asset values, rather than a continuously traded crypto market price. A reported value can be delayed or erroneous. The lender needs a policy for accepting updates and reacting to abnormal ones.
Horizon documentation describes price-feed bounds that reject out-of-range issuer updates, with emergency actions around those events. Those safeguards constrain one failure path. They don't establish that every accepted value equals a realizable sale price or that every reporting error will be detected. Horizon pricing safeguards.
That distinction is practical during stress. A fund can have a defensible accounting value while its normal redemption process takes time. Immediate buyers may demand a discount. The liquidation design has to account for the asset's actual exit conditions.
For credit funds, the gap can be wider because borrower recovery and fund redemption can follow different schedules. Our credit comparison explains why a liquidity service and the underlying fund's exit aren't interchangeable.
Liquidation has a permissions layer
The market needs a way for permitted participants to take over or realize restricted collateral while repaying debt. An ordinary liquidator can't assume it can receive and redeem every financial asset merely because the health factor crossed a threshold.
The required eligibility and operational route should be checked for the specific collateral. A transaction repaying debt and a later fund redemption can be different stages. Their timing affects the capital and pricing a liquidator needs.
This can change the market's response during heavy liquidations. Available stablecoin liquidity, eligible receivers and fund exit conditions all matter. The risk parameters should be read as part of that operating design.
A stablecoin supplier should therefore inspect the collateral set and controls rather than assuming government-related assets remove all lending risk. The application adds valuation and liquidation dependencies to the underlying claims.
An onboarding proposal isn't a live reserve
A tokenized fund appearing in a governance discussion doesn't establish that it can be supplied or borrowed against today. The proposal, approval, execution and usable reserve are distinct milestones.
Horizon has its own asset-onboarding process and current governance discussions. Check the deployed reserve and effective parameters before presenting a new fund as supported. Horizon governance, asset-onboarding update.
The same applies to commercial announcements. A partnership can describe a future integration, while the user's actual route still needs deployment and issuer access. An application screenshot is useful evidence only when it shows the intended market and asset.
Model the position before using it
Write down the collateral, its current risk parameters and the expected debt path. Change the collateral value and borrowing rate in a simple stress model. The calculator below uses fictional inputs to show that relationship, with no claim to represent a live reserve.
Then identify how you would repay during a disrupted redemption period. A plan relying on instant fund liquidity should name the route and its limits. A loan can remain due when an independent liquidity service pauses.
The combination can make an eligible asset more useful, but its suitability depends on the complete position. The useful output of the research is an exit and repayment plan, alongside the income figure.
How much debt must be repaid to rebuild a buffer?
Use the stressed example above: $85,000 of collateral, an illustrative 80% liquidation threshold and $70,000 of debt. The collateral value used in the simplified health-factor numerator is $68,000. Reaching a health factor of 1.2 would require debt of about $56,666.67, so the borrower would need to repay about $13,333.33.
This ignores further interest, fees and any position-specific constraints. It is not a live Horizon parameter or a recommendation to use that buffer. Its purpose is to connect a chosen target to a repayment amount before a redemption delay makes that funding difficult.