> For the complete documentation index, see [llms.txt](https://docs.openeden.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openeden.com/hybond/risks.md).

# Risks

### Risks

HYBOND involves exposure to a tokenised interest in the BNY Mellon Global Short-Dated High Yield Bond Fund, blockchain-based infrastructure, and third-party service providers. Participation involves material risk, including the potential loss of some or all invested value.

The following risk categories are applicable to HYBOND:

#### Fund & Market Risk

The underlying BNY Mellon Global Short-Dated High Yield Bond Fund invests in high-yield (sub-investment grade) fixed income securities. These securities carry a higher risk of default and are more sensitive to changes in credit conditions, interest rates, and macroeconomic outlook than investment-grade bonds.<br>

#### Credit & Default Risk

High-yield bonds are issued by borrowers with below-investment-grade credit ratings. Issuers may default on interest or principal obligations, resulting in losses to the fund and a decline in HYBOND token value.

#### &#x20;Interest Rate Risk

Bond prices are inversely correlated with interest rates. Rising interest rates may reduce the NAV of the underlying fund, and by extension the value of HYBOND.\
NAV Volatility. The NAV of HYBOND reflects the performance of the underlying fund and will fluctuate. There is no capital protection or guarantee of returns.<br>

#### Currency Risk

The underlying fund may hold assets denominated in currencies other than USD. Currency movements may affect fund performance and HYBOND token value.<br>

#### Liquidity Risk

Liquidity risk is the risk that HYBOND cannot be redeemed in a timely or cost-effective manner.

#### &#x20;Redemption Gating

Redemptions are subject to a T+4 settlement period and a 10% NAV gating limit per epoch. During periods of elevated redemption demand, investors may not be able to redeem their full requested amount within a single epoch.

#### &#x20;Underlying Fund Liquidity

The underlying fund may itself impose redemption restrictions, gates, or suspensions in stressed market conditions. These restrictions would flow through to HYBOND redemptions.

#### &#x20;Secondary Market Liquidity

There is no guarantee of a liquid secondary market for HYBOND tokens. Holders wishing to exit prior to settlement may be unable to do so at a fair price or at all.

#### Counterparty Risk

\
HYBOND depends on a chain of third-party service providers. Failure, insolvency, regulatory action, or operational disruption at any provider may adversely affect investor assets.

#### &#x20;Fund Manager & Custodian Risk

BNY acts as both fund manager and custodian for the underlying fund. Failure, misconduct, or operational disruption at BNY could materially impair the fund's assets and the value of HYBOND.

#### Crypto Custody Risk

HYBOND tokens and associated crypto assets are held in custody by Coinbase and/or BitGo. The insolvency, regulatory action, or security failure of either custodian may affect access to or recovery of assets.

#### Service Provider Dependencies

OpenEden relies on third-party providers for KYC/AML, fund administration, oracle price feeds, and blockchain infrastructure. Disruption to any of these services may delay or impair normal operations.

#### Smart Contract & Oracle Risk

#### &#x20;Smart Contract Risk

HYBOND operates via smart contracts deployed on Ethereum. Smart contracts may contain bugs, logic errors, or vulnerabilities that could be exploited. All contracts are subject to third-party security audits prior to mainnet deployment, but audits do not guarantee the absence of undiscovered issues.

#### &#x20;Oracle & Price Feed Risk

The HYBOND token price is updated by an off-chain keeper bot and subject to Price Guard protections. A failure, manipulation, or delay in the price feed may result in incorrect minting or redemption amounts. In extreme scenarios, the Price Guard may pause operations to prevent adverse outcomes.

#### Operational Risk

Manual Process Risk\
Certain operational steps including KYC whitelisting, NAV updates, fund wire transfers, and token minting, involve manual processes or human intervention. Errors, delays, or failures in these processes may disrupt the normal operation of the vault.

#### &#x20;Key Person & Vendor Risk

Disruption to key personnel or critical vendors may affect OpenEden's ability to operate HYBOND in accordance with its normal processes.\
Blockchain Network Risk\
HYBOND operates on Ethereum & BNB Chain. Network congestion, protocol upgrades, or forks may affect transaction settlement, gas costs, or smart contract behaviour.

#### Regulatory Risk

The regulatory treatment of tokenised real-world assets and digital securities is evolving across jurisdictions. Changes in applicable laws, regulatory interpretations, or enforcement actions may restrict HYBOND's operation, require structural changes, limit redemptions, or result in suspension or wind-down.\
HYBOND is only available to eligible investors who have completed the required KYC/AML onboarding. Regulatory changes may affect eligibility criteria, transfer restrictions, or reporting obligations.

#### No Guarantee of Returns

HYBOND does not provide capital protection. The value of HYBOND tokens may fall below the subscription price. Returns are not guaranteed, and investors may lose some or all of their investment.


---

# 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:

```
GET https://docs.openeden.com/hybond/risks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
