> For the complete documentation index, see [llms.txt](https://docs.cian.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cian.app/bondify/for-partners-integration-hub/collateral-asset-onboarding.md).

# Collateral Asset Onboarding

Onboarding turns a tokenized asset into Bondify collateral with its own YT and Looper vaults.

#### Asset Review

* **Track record:** 12+ months operating history, with documented yield sources, realized returns, risk sources, risk-adjusted returns, and Sharpe.
* **Legal:** defined legal structure and regulatory compliance.
* **Technical:** ERC-20 token from an audited tokenization provider.

#### Integration Path

**1. Oracle integration (information required from the issuer).** This is the core dependency - the asset cannot be parameterized until the issuer provides:

* **Oracle source & mechanism:** provider (Chainlink / Pyth / etc.), pricing basis (Proof-of-Reserve, NAV, or DEX market price), data source, and update frequency.
* **Mint route:** price basis (NAV vs market), cadence (real-time vs periodic), and whether minting requires a whitelist / recommended path.
* **Exit route:** redemption cooldown and execution logic, the unstake contract interface, redemption cost and who bears it, a pre-confirmation price-estimation interface, and base-stablecoin swap slippage.
* **External lending listings:** whether the asset is already listed as collateral on Aave or Morpho (this unlocks the migration fast track below).

For credit RWAs, additionally: NAV methodology (net of expected and realized bad debt), write-off policy, monthly vintage + recovery data, FX-risk bearer, and the fixed SLF rate / looper-buffer commitment (fixed senior rate / junior-buffer commitment) need to be pre-discussed.

**2. Risk modeling (Bondify-side)** - LTV and debt-ceiling calibration from the inputs above.

**3. Vault deployment (Bondify-side)** - we deploy the asset with custom risk parameters, set SLF allocation across assets and across strategies (YT vs Looper), and enable the YT and Looper vaults with target underlying-yield and borrow-cost ranges.

**4. Liquidity bootstrap (optional)** - integrate with Staple DEX to enable secondary trading. This seeds two kinds of pools: the RWA token against USDC (so the asset itself has an on-chain spot market), and the Junior Token, the standardized leveraged position, against USDC (so holders can buy and sell leveraged exposure directly). It's additive, not blocking.

#### Fast track: assets already on Aave or Morpho

If the asset is already collateral on Aave or Morpho, Bondify enables External Position Migrate from day one. Users import existing single-collateral / single-debt (USDC) looping positions directly into a Bondify Junior position - no unwind-and-rebuild - leaving only oracle and parameter setup.

#### What onboarding unlocks

Onboarding is not a one-off liquidity event. It gives the asset a standing place in a leveraged-yield market, which compounds over time:

* **Asset growth.** Looper leverage turns each dollar of issuance into several dollars of effective demand for the asset, so the same investor base supports a larger book than spot buying alone.
* **Sticky holders.** YT and Junior Token holders hold to maturity to earn, and can roll into the next term rather than redeem - turning one-time buyers into a recurring, lower-churn base.
* **A continuous price.** Standardized Junior Tokens and a live YT market give the asset an on-chain secondary price and exit, which makes new holders more willing to enter in the first place.
* **Distribution.** Direct exposure to Bondify users actively seeking leveraged-yield and yield exposure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cian.app/bondify/for-partners-integration-hub/collateral-asset-onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.