Lien Wrapped Leverage for RWA Liquidators
Where should additional capital sit when a liquidator already has a senior lender? Not on the balance sheet. Inside the asset.
1. Where the Capital Goes
Start with a liquidator who borrows $750K from a senior lender, puts in $250K of their own equity, and uses the $1M to buy a tokenized asset trading at 90 cents on the dollar. The strategy works: acquire cheap, redeem at NAV, keep the spread. The constraint is not skill or deal flow. The constraint is that $1M is all they can deploy.
The obvious move is to borrow more. But borrowing more means adding debt to the liquidator's balance sheet. The senior lender sees a new creditor. Even if the new capital is subordinated, the senior lender's covenants may prohibit it. Even if the covenants allow it, the liquidator's debt ratios change, which affects every other relationship they have. The new lender, meanwhile, takes subordinated risk and expects to be compensated for it, which cuts into the economics of the trade.
This is the wrong framing. The question is not "how do I borrow more." The question is "where should the additional capital sit."
If the capital attaches to the liquidator's balance sheet, it creates an intercreditor problem. If it attaches to the acquired asset itself, there is no second creditor. There is only an asset with an embedded claim.
2. Why Lending Is the Wrong Primitive
Lending creates a creditor. A creditor can be defaulted on. A default creates legal proceedings. Legal proceedings freeze assets. Frozen assets cannot be redeemed at NAV. The entire strategy depends on the liquidator being able to move fast. Adding a creditor adds friction at the exact moment it matters most.
Lending also competes with the senior position. Even unsecured debt is a claim on the liquidator's balance sheet. The senior lender monitors debt ratios. The senior lender has covenants. Every dollar of new debt changes the calculus, regardless of where the new lender sits in the stack.
The deeper issue is that in this strategy, the collateral is not the liquidator's balance sheet. The collateral is the discounted RWA that was acquired. The value is in the asset. If it recovers to par, everyone gets paid. If it does not, the loss should be absorbed by whoever had exposure to that specific asset. A lending relationship does not allow this clean separation. The borrower owes the money regardless of what happens to any specific asset.
The alternative is to put the capital where the value actually is: inside the asset. RAVA deposits capital alongside the liquidator into a triparty custodian. The custodian acquires the discounted RWA tokens. Upon acquisition, the tokens are wrapped into wRWA tokens that encode RAVA's claim directly: principal owed, upside share, and waterfall position. The claim lives inside the token. It is not a side agreement. It is the token.
3. The Participants
4. The Flow
The lifecycle of a position from identification through settlement.
An RWA token is trading below NAV. The liquidator sees a redemption or secondary sale opportunity.
The liquidator deposits their own capital (which may itself be borrowed from a senior lender). RAVA deposits additional capital alongside it. Both go to the custodian.
The custodian acquires the discounted RWA tokens using the pooled capital. Upon acquisition, the tokens are wrapped into wRWA tokens that encode RAVA's lien: principal, upside share, and waterfall position. The lien becomes part of the token.
The liquidator has full operational control. They decide when to redeem with the issuer, when to sell on secondary markets, and how to manage the position. They hold the OPERATOR_ROLE on the custodian contract. They cannot withdraw or move the underlying assets directly.
When the liquidator redeems or sells, the wrapped token must be unwrapped. Unwrapping triggers the settlement waterfall automatically in a single atomic transaction. There is no separate repay action. There is no way to access the underlying without satisfying the waterfall.
5. Settlement Waterfall
Every exit routes through the same waterfall. There is no alternative path. The proceeds from redemption or sale flow in strict priority order.
If the liquidator never exits, both parties' capital remains locked. There is no incentive to hold indefinitely. If proceeds are insufficient to cover RAVA's principal, RAVA takes the loss. There is no recourse to the liquidator's balance sheet.
6. What Makes This Work
The reason this structure holds together is that the claim and the asset are the same object. The wRWA token is not a receipt for an asset with a separate lien attached. The lien is encoded in the token. You cannot interact with the underlying without going through the settlement logic. This is a different enforcement model than a traditional security interest, where the lien is a legal agreement that must be enforced through courts.
Because the claim resolves through the asset, there is no default scenario in the traditional sense. RAVA has not lent money to the liquidator. The liquidator does not owe RAVA anything. If the acquired RWA drops in value and the custodian winds down the position, RAVA takes the loss on their portion. There is no recourse, no collections process, no legal dispute over who owes what. The waterfall executed. The numbers are what they are.
The senior lender's collateral position is structurally unchanged. RAVA's capital went to the custodian, not to the liquidator. It never appeared on the liquidator's balance sheet, never triggered a covenant, never changed a debt ratio. The senior lender's claim is against the liquidator's equity and cash flows, which are the same as before. The liquidator now controls a larger pool of acquired assets, which if anything improves their ability to generate returns and service the senior debt.
There is a subtlety worth noting. The liquidator's operational capacity is now split across a larger position. If the custodian position requires attention during a stress period, that is attention not being spent on the liquidator's other obligations. The senior lender is not economically diluted, but the liquidator's operational bandwidth is not infinite. This is a real consideration and one that scales with position size.
7. How the Senior Lender Benefits
Consider what the senior lender sees before and after RAVA enters.
Before: the liquidator borrows $750K, puts in $250K equity, deploys $1M against discounted RWAs. The senior lender has a $750K claim against a $1M asset base. Coverage is 1.33x. The lender's recovery depends on the liquidator's ability to exit positions profitably.
After: RAVA deposits $250K into the custodian alongside the liquidator's capital. The custodian acquires $1.25M of discounted RWAs. The senior lender's $750K claim against the liquidator's balance sheet has not changed. No new debt was added to the liquidator. No covenants were triggered. But the liquidator now controls a $1.25M pool instead of $1M. If the assets recover, the liquidator generates more profit, which strengthens their ability to service the senior loan. Coverage effectively improves from 1.33x to 1.67x.
If the assets do not recover, RAVA absorbs the loss on the $250K that went through the custodian. The senior lender's collateral is the liquidator's equity, not the custodian's assets. These settle from separate pools. RAVA's loss does not reduce the senior lender's recovery.
The senior lender can also participate directly. If the lender wants exposure to the upside of the discounted RWA acquisition, they can invest alongside RAVA into the custodian. Their senior claim against the liquidator remains unchanged. Their investment into the custodian is a separate position with its own waterfall priority, governed by the same embedded lien mechanics. The two positions are independent. The lender participates in the upside without altering the risk profile of their senior loan.
8. Risk Engine
RAVA's risk engine continuously monitors positions and sets parameters dynamically. Signals are repriced every 5 seconds.
These signals determine two parameters. maxLeverage sets how much additional capital RAVA will provide relative to the liquidator's deposit. marginThreshold sets the point at which the custodian triggers a forced wind down, unwrapping and settling everything through the waterfall automatically.
The liquidator does not need to post additional margin or respond to margin calls. If the threshold is breached, wind down happens programmatically.
9. Contract Interface
10. Custodian Implementation
The custodian can be implemented at different levels of decentralization depending on the asset type.
Starting with an on chain contract for fully tokenized RWAs. Hybrid or institutional custodians may be needed for assets with off chain redemption steps.
Ravariant Labs · March 2026