Risk Factors
Participating in TRTH involves material risks. This page highlights categories users and integrators should understand; it is not exhaustive and is not financial advice.
Smart contract risk
Section titled “Smart contract risk”TRTH logic is implemented as on-chain contracts. Bugs, unexpected interactions between modules, or incorrect parameters could cause loss of funds, stuck states, or incorrect reward accounting. Even well-reviewed code can fail if deployed configuration diverges from assumptions.
Mitigations include reading official documentation, verifying addresses, and preferring small exploratory positions until you are comfortable with the system behavior.
VRF dependency
Section titled “VRF dependency”Bonus and king outcomes rely on Chainlink VRF randomness delivered through ChainlinkVrfWordAdapter. Risks include:
- Delayed fulfillments during network congestion or operator issues.
- Oracle configuration errors (wrong key hash, subscription funding, or coordinator settings).
- User experience impact if epochs cannot finalize until randomness arrives.
Randomness is verifiable, but liveness of fulfillment still matters for when you can claim.
Keeper / orchestrator liveness
Section titled “Keeper / orchestrator liveness”Off-chain orchestrator services coordinate operational steps that keep epochs and auxiliary processes moving. If automation is offline or backlogged, the protocol may experience delays. Documentation references a maximum backlog of up to 16 epochs worth of work in adverse conditions—treat this as a planning horizon, not a guaranteed worst case.
Oracle risk
Section titled “Oracle risk”Beyond VRF, any price or reference feeds used for operational decisions (liquidity actions, parameter tuning, or monitoring) can be wrong, stale, or manipulated in thin markets. Integrators should never trust a single oracle read for high-stakes automation without safeguards.
Liquidity risk
Section titled “Liquidity risk”TRTH is a DeFi token. Slippage, thin pools, MEV, and volatile demand can make entering or exiting positions costly. The LiquidityBootstrap and FeeSink mechanisms aim to support market depth over time, but they do not guarantee liquidity at any price level.
Regulatory risk
Section titled “Regulatory risk”Digital assets face uncertain and evolving regulation. Depending on your jurisdiction, using TRTH could have tax, securities, AML, or sanctions implications. You are responsible for compliance with applicable laws.
Operational and social risk
Section titled “Operational and social risk”Phishing sites, fake tokens, and malicious approvals are common in DeFi. Always confirm URLs, contract addresses, and token symbols against official channels.