How RWAs get lending-protocol listings
Liquidation-grade DEX depth, NAV-tracked positions, and mint/redeem backstops.
An RWA gets listed as collateral on a lending protocol by proving that liquidators can sell meaningful size onchain, atomically, at bounded slippage. Risk teams and curators evaluating a listing look past market cap and issuer credentials to one operational question: if $2M of this collateral must be liquidated in a bad hour, what does the execution path look like? Without liquidation-grade DEX spot depth, the answer is "it cannot be done," and the listing stalls regardless of the asset's quality; building that depth is the work liquidity operators like Amplifi are engaged for.
The one question that decides the listing
Risk curators all converge on the same test: model the worst-hour liquidation, plot the execution path, price the tail. The RWA needs a DEX pool deep enough that the liquidation prints inside the protocol's liquidation bonus. If it does not, the listing is either rejected or capped at a size so small it is not useful.
Build the depth before you apply
Deploy a NAV-tracked pool with in-range depth sized to the target liquidation window. Get aggregator coverage. Run the position long enough to produce a public track record of tight spreads and fills. That track record is the evidence risk teams need; you cannot substitute credentials or issuer size for it.
Publish the mint/redeem backstop
Document exactly how a liquidator or arbitrageur can hit mint/redeem: the spread, the settlement time, the KYC gate. Risk teams need to know where the tail liquidity comes from when the DEX pool is exhausted. A pool without a backstop is a pool that can be broken.
Talk to the curators early
Risk curators publish frameworks. Read them, size the pool to the requirements, then engage the curator with data, not with a pitch. Listings move at the pace of evidence.
To scope liquidation-grade liquidity for an RWA listing, contact contact@amplifiliquidity.com.