Skip to main content

Common Issues

Resolution Issues

Symptoms:
  • Resolution time has passed but market not resolved
  • getResolution() still shows resolved: false
Possible Causes:
  1. Data source delay: External API hasn’t updated yet
  2. Low confidence: AI waiting for more data confirmation
  3. Network congestion: Transaction stuck in mempool
  4. Criteria unclear: AI unable to parse criteria
Solutions:
Prevention:
  • Add buffer time between event end and resolution time
  • Specify multiple reliable data sources
  • Write clear, unambiguous resolution criteria
Symptoms:
  • Resolution submitted but confidence < 90%
  • Your contract rejects low confidence resolutions
Common Causes:Example Fix:Bad criteria (causes low confidence):
Good criteria (high confidence):
Debugging:
Symptoms:
  • Resolution fails or delays
  • Error: “Data source unavailable”
Solutions:
  1. Always specify backup sources:
  1. Use reliable providers:
  • ✅ CoinGecko, CoinMarketCap (crypto)
  • ✅ ESPN, Official League APIs (sports)
  • ✅ NOAA, OpenWeatherMap (weather)
  • ❌ Unknown or unreliable APIs
  1. Test data source accessibility:
  1. Check API rate limits:
  • Some free APIs have rate limits
  • Use paid tiers for critical markets
Symptoms:
  • Resolution outcome doesn’t match expected result
  • Users dispute the resolution
Investigation Steps:
Common Reasons:If Resolution is Wrong:
  1. Review proof and attestation data
  2. Check if criteria were ambiguous
  3. Implement dispute mechanism in your platform
  4. Contact support with proof if TEE malfunction suspected

Integration Issues

Symptoms:
  • Market resolved on oracle but your contract not updated
  • ResolutionSubmitted event fired but your callback didn’t execute
Checklist:
Testing Callback:
Debug Failed Callback:
Symptoms:
  • verifyAttestation() returns false
  • Your contract rejects resolutions
Common Issues:
  1. Code hash not approved:
  1. Attestation expired:
  1. Wrong verification library:
  1. TEE address not authorized:
Testing:
Symptoms:
  • Callback transactions cost too much gas
  • Resolution requests expensive
Optimization Tips:
  1. Efficient storage:
  1. Minimize callback logic:
  1. Batch operations:
  1. Use events instead of storage:
Common Issues:
  1. Wrong oracle address:
  1. Missing interface implementation:
  1. Contract size too large:
Deployment Checklist:
  • ✅ Correct network (mainnet/testnet)
  • ✅ Correct oracle address for network
  • ✅ Sufficient gas for deployment
  • ✅ Contract verified on block explorer

Network & Infrastructure Issues

Symptoms:
  • Transaction pending for long time
  • Resolution not confirming
Solutions:
  1. Check gas price:
  1. Speed up transaction:
  1. Cancel transaction:
Symptoms:
  • Contract calls failing intermittently
  • “Execution reverted” with no reason
Solutions:
  1. Use reliable RPC providers:
  1. Implement retry logic:

Debugging Tools

Check Resolution Status

Monitor Events

Test Callback Locally

Getting Help

FAQ

Check frequently asked questions

Telegram Support

Ask the community or team

GitHub Issues

Report bugs or request features

Documentation

Review the full documentation