DocsReference

Safety and risk

The boundaries, irreversible actions, and operational assumptions every Yeeld user should understand.

User-facing risks

Token prices can move sharply and liquidity can be thin.
Locks cannot exit early, even during market stress.
Buyback schedules cannot be cancelled after funding.
Slippage protection depends on the minimum received you approve.
Smart contracts, oracles, Uniswap v4, Robinhood Chain, and approved adapters add technical risk.
Displayed fiat values depend on available trusted price data and can lag.

Before you transact

1
Verify the network
Robinhood Chain mainnet should show chain ID 4663.
2
Verify the contract
Compare the token and protocol address with the explorer and reviewed deployment records.
3
Review economics
Check the pair asset, phase, fee split, creator tax, and tax destination.
4
Protect the output
Use a suitable slippage tolerance or explicit minimum received.
5
Read the expiry
For locks and schedules, confirm the exact duration and resulting dates.

Production status

Do your own assessment

Documentation explains intended behavior; it is not an audit, investment advice, or a guarantee. Independent review, canonical-fork testing, governance controls, and monitoring remain essential for production safety.