Corporate bonds in DeFi: design around the obligation

A bond can suit a portfolio and still fail a lending market’s requirements. For curators, the difference starts with what the product owes its users.

A corporate bond can pay every coupon on time and still be the wrong asset for a DeFi product.

Consider a vault with terms that allow it to hold a bond through a period of thin trading. The curator may have a sound reason to wait for repayment. Put that same bond into a lending market, and someone may need to turn it into stablecoins after a borrower breaches a limit. The issuer’s ability to repay at maturity does not answer whether the collateral can be sold today.

That distinction should shape how corporate bonds are used onchain. Start with the obligation the product takes on, then work backwards to the securities and processes needed to meet it.

Individual tokenized bonds give curators more choice over the underlying portfolio. The value of that control depends on how well the portfolio supports the product built around it.

Choose who makes the investment decisions

A curator allocating to a tokenized bond fund chooses a managed portfolio. The fund’s investment manager selects securities and weights within its mandate. The curator’s work is to assess that mandate, the manager’s decisions, and the terms on which the fund can be held or exited. Tokenization does not change that division of responsibility. FINRA’s overview of bonds and bond funds explains the underlying structures.

With individual tokenized bonds, the curator makes the portfolio decisions security by security, subject to eligibility and availability. It can select maturities, set issuer weights, and exclude a bond whose terms do not fit the strategy.

A managed fund can suit a team that wants to delegate security selection. Individual bonds can suit a team with a specific mandate and the capacity to research and monitor its holdings. Greater control brings responsibility for those choices, including the decision to sell when the investment case changes.

The distinction matters when combining the two. A direct holding and an allocation to a fund may expose the vault to the same issuer. The curator needs enough information about the fund’s holdings to assess the combined exposure.

Write a mandate that survives a breach

An issuer limit is incomplete until the team knows what happens when it is breached.

Take a hypothetical $100 million vault with a 20% limit per issuer. It holds $20 million of one company’s bonds. Other holdings fall in value, reducing the vault’s total value to $80 million, while this position stays unchanged. Its weight is now 25%. The curator has breached the limit without buying another bond.

An immediate sale would restore the limit if it could be executed at a suitable size and price. It might also impose costs on holders during a difficult market. A temporary exception avoids that sale but leaves the vault with more concentration than its stated limit allows.

The mandate should define how that decision is made. It should distinguish a limit on new purchases from a limit that requires exposure to be reduced, and identify who can approve an exception and how it is reported.

The same discipline applies to the interest-rate exposure of the portfolio. Maturity tells the curator when principal is contractually due, subject to issuer performance. Duration estimates price sensitivity to changes in rates. Two bonds with similar coupons can make very different contributions to the vault’s risk.

Make collateral approval a separate decision

Approval to hold a bond should not automatically become approval to borrow against it.

A lender needs a credible way to recover the debt if the borrower cannot maintain the position. In Aave’s liquidation mechanism, a liquidator repays debt and receives collateral plus a liquidation bonus. That incentive depends on the liquidator being willing and able to take the collateral.

For a lending market considering tokenized bonds, the review must follow the proposed transaction all the way through. Can the intended liquidator receive the token? Can it sell to an eligible buyer in the required size? When would the proceeds be available, and in which currency or asset?

A quoted price answers only part of that review. A valuation used for portfolio reporting may not be executable for a large sale. Transfer restrictions or servicing dependencies may narrow the available exit routes further.

A haircut reduces the collateral value recognized for borrowing purposes. It can provide a buffer against losses, but increasing the buffer cannot create an eligible buyer. A market may need a different liquidation process, tighter borrowing limits or a decision to exclude the asset.

Put withdrawals and bond payments on the same calendar

The product’s end date needs to be reconciled with the dates on which its assets produce cash.

Suppose a hypothetical vault is due to return capital in two years, but some of its bonds mature in three. Those positions create a funding requirement at the vault’s end date. The product will need to sell them, refinance or use another documented source of cash. Each route has assumptions that need to be tested.

Bonds that mature earlier introduce a different decision. The curator can hold the proceeds as cash or reinvest at the terms available then. Either choice can change the portfolio’s income and exposures.

Coupon payments also need to be compared with withdrawal terms. A portfolio receiving interest every six months cannot fund frequent withdrawals from coupon receipts alone. The design needs to identify what funds the intervening payments and how that funding behaves under stress.

Nor does a fixed coupon establish a fixed return for vault holders. Purchase price, fees, credit losses and any sale before maturity affect the outcome. FINRA’s explanation of bond yield and return makes the distinction clear.

For collateral, maturity adds another operational question: what happens to the outstanding borrowing when the bond repays? The market needs a defined process for handling the proceeds and any release or replacement of collateral.

Reuse services, but set limits for each use

Position records, valuation data and coupon processing can support several products. The decisions made with that information will differ.

A diversified vault needs to know whether a bond belongs in its portfolio and how large the holding should be. A lending market needs to establish borrowing terms and a workable liquidation process. A maturity ladder needs repayment tracking and reinvestment rules. A structured strategy needs to specify which claims receive cash first and which absorb losses.

Treating an asset as simply “integrated” obscures those differences. The approval should name the use, the limits and the conditions under which the asset stops being suitable.

Responsibility for changing a limit should also be distinguished from responsibility for placing the trade. Morpho Vault V2’s documentation provides a useful reference: the curator configures risk parameters, while the allocator executes allocations. The broader design lesson is to make decision rights explicit, including who can act when the normal process is disrupted.

Turn the review into an allocation decision

Gyld is building the corporate bond layer for onchain finance. Its focus on individual securities gives this portfolio-construction work a specific starting point: the issuer, terms and cash flows of each bond.

For a curator evaluating an asset, a useful next step is a short acceptance memo for one intended use. It should establish:

• The obligation: what the product owes holders, when it is due and under which conditions.
• The claim: the underlying security, token-holder rights, custody arrangements, eligibility rules and authoritative records.
• The allocation: why the bond fits, its proposed weight and its contribution to portfolio risk.
• The operating limits: the pricing source, permitted uses, concentration limits and available exit routes.
• The response to an exception: who acts after a missed payment, stale price, transfer failure or limit breach, and what they are authorized to do.

Test that memo against one awkward event. A coupon arrives late while a withdrawal is due. Identify the source of cash, the approval required to use it, and the effect on holders who remain. If the answer relies on a service or funding arrangement that does not yet exist, make that an explicit condition of approval.

The product examples are hypothetical and do not announce Gyld offerings or integrations. Tokenization does not remove issuer credit, interest-rate, or liquidity risk; legal, custody, smart-contract, and operational dependencies also require review.