ONTON × ONION has proactively identified critical risks across technical, regulatory, and operational domains — and built in safeguards to protect users, contributors, and the protocol.
🧱 Technical Risks
| Risk | Mitigation |
|---|---|
| TON network congestion | Retry logic in Mini App; fallback queues |
| Smart contract bugs | External audits; modular Jetton-based contracts(TBD) |
| Merge logic misuse | One-time use, wallet-limited, verified input checks |
| Oracle/snapshot manipulation | IPFS-anchored versioned snapshots; multi-party sign(TBD) |
| Sybil attacks on airdrops | SBT verification; Telegram + wallet linkage (TBD) |
⚖️ Regulatory Risks
| Risk | Mitigation |
|---|---|
| MiCA alignment uncertainty | Legal opinion via Finnish firm; token classified utility (TBD) |
| U.S. participation | Geo-restricted T&Cs; blocked from presale/claim (TBD) |
| Compliance scope creep | Foundation entity structure; phased decentralization(TBD) |
📊 Market Risks
| Risk | Mitigation |
|---|---|
| TGE sell pressure | Conservative unlocks; staking incentives |
| Low LP depth | Pre-funded LP pool; DAO-backed liquidity programs |
| NFT fatigue | Merge system, ongoing utility, seasonal perks |
| Bear market launch | Low cap raise; phased emission strategy |
🤖 Operational Risks
| Risk | Mitigation |
|---|---|
| Community backlash | Transparent docs, early UI preview, public FAQs |
| Scaling team capacity | DAO-funded contributor network |
| Incentive gaming | On-chain proof (SBTs); referral SBTs in roadmap |
Risk-aware doesn’t mean risk-averse — it means designed for resilience.