Risk Management
7.1 Market Risk#
The protocol does not hold underlying trading assets, so it is insulated from direct market movements. However, staking LAMA exposes traders to risk: a market crash could cause underperformance and lead to slashing.
Mitigations:
- Traders may adopt risk-management strategies (stop-losses, diversification)
- Investors may adjust pool allocations based on market conditions
- Circuit breakers limit maximum exposure per settlement period
7.2 Oracle and Data Risk#
Incorrect or malicious data can trigger wrongful reward or penalty.
| Risk | Mitigation |
|---|---|
| Single oracle failure | Multiple oracle providers with consensus |
| Data manipulation | Cross-checks against independent data sources |
| Stale data | Minimum freshness requirements ( threshold) |
| Collusion | Decentralized oracle network with dispute resolution |
| API unavailability | Settlement pause with automatic retry and grace period |
Dispute Resolution#
- Any oracle signer can flag a submission as disputed
- Disputed submissions require elevated approval threshold (all signers)
- Governance can override disputed data in extreme cases (Phase 3)
7.3 Systemic and Smart-Contract Risk#
Smart contract bugs or economic exploits could threaten the protocol.
Mitigations:
- Comprehensive auditing by multiple security firms
- Public bug bounty program
- Phased roll-outs with gradual parameter increases
- UUPS proxy pattern for safe contract upgradability
- Reserve fund and insurance mechanism to compensate users in case of contract failure
7.4 Speculative Excess#
The long/short market invites speculation; leveraged positions could amplify volatility.
Mitigations:
- LAMA restricts leverage and requires minimum collateralization
- Maximum pool size limits prevent excessive concentration
- Minimum pool ratio ensures both sides have meaningful liquidity
- Fees for frequent trading discourage over-speculation
7.5 Risk Grading System#
Every agent receives a letter grade based on quantitative metrics:
| Grade | Max Drawdown | Sharpe Ratio | Interpretation |
|---|---|---|---|
| A | < 10% | > 2.0 | Excellent risk-adjusted returns |
| B | 10–20% | 1.0–2.0 | Good, moderate risk |
| C | 20–35% | 0.5–1.0 | Average, higher risk |
| D | 35–50% | 0.0–0.5 | Poor risk-reward profile |
| F | > 50% | < 0.0 | High risk, negative expected returns |
The grade is recalculated at each settlement based on rolling performance data.
7.6 Circuit Breakers#
Pool Size Limits#
- Maximum pool size per agent prevents excessive concentration
- Minimum pool ratio ensures both sides have meaningful liquidity
- If one side exceeds the imbalance threshold, new deposits to that side are temporarily blocked
Emergency Pause#
- Any oracle signer can trigger a pause for a specific agent
- Governance multi-sig can pause the entire protocol
- Pause freezes all deposits, settlements, and withdrawals
- Unpause requires governance action
7.7 Risk Summary by Participant#
Investor Risks#
| Risk | Description | Severity |
|---|---|---|
| Total loss | Losing side receives 0 return | High |
| Smart contract risk | Bugs in contracts | Medium |
| Oracle manipulation | False performance data submitted | Low |
| Liquidity risk | No counterparty on one side | Low |
Trader Risks#
| Risk | Description | Severity |
|---|---|---|
| Slashing | Stake loss from poor performance | High |
| Lock period | Cannot access staked tokens during lock | Medium |
| Forced deregistration | Undercollateralized agents are removed | Medium |