Common Issues
Resolution Issues
Resolution is taking longer than expected
Resolution is taking longer than expected
Symptoms:Prevention:
- Resolution time has passed but market not resolved
getResolution()
still showsresolved: false
- Data source delay: External API hasn’t updated yet
- Low confidence: AI waiting for more data confirmation
- Network congestion: Transaction stuck in mempool
- Criteria unclear: AI unable to parse criteria
- Add buffer time between event end and resolution time
- Specify multiple reliable data sources
- Write clear, unambiguous resolution criteria
Resolution has very low confidence score
Resolution has very low confidence score
Symptoms:
Example Fix:❌ Bad criteria (causes low confidence):✅ Good criteria (high confidence):Debugging:
- Resolution submitted but confidence < 90%
- Your contract rejects low confidence resolutions
Issue | Solution |
---|---|
Vague criteria | Be more specific about data sources and logic |
Unreliable data source | Use established providers (CoinGecko, ESPN, etc.) |
Ambiguous question | Rephrase with clear YES/NO logic |
Data unavailable | Wrong API endpoint or source offline |
Premature resolution | Resolution time before data is available |
Data sources are unreachable
Data sources are unreachable
Symptoms:
- Resolution fails or delays
- Error: “Data source unavailable”
- Always specify backup sources:
- Use reliable providers:
- ✅ CoinGecko, CoinMarketCap (crypto)
- ✅ ESPN, Official League APIs (sports)
- ✅ NOAA, OpenWeatherMap (weather)
- ❌ Unknown or unreliable APIs
- Test data source accessibility:
- Check API rate limits:
- Some free APIs have rate limits
- Use paid tiers for critical markets
Resolution resolved to unexpected outcome
Resolution resolved to unexpected outcome
Symptoms:Common Reasons:
If Resolution is Wrong:
- Resolution outcome doesn’t match expected result
- Users dispute the resolution
Reason | Fix |
---|---|
Wrong data source queried | Verify exact API endpoint in criteria |
Timing issue | Check if data was available at resolution time |
Criteria misunderstood | Rephrase criteria more clearly |
Data source error | Use multiple sources for verification |
- Review proof and attestation data
- Check if criteria were ambiguous
- Implement dispute mechanism in your platform
- Contact support with proof if TEE malfunction suspected
Integration Issues
Callback function not being called
Callback function not being called
Symptoms:Testing Callback:Debug Failed Callback:
- Market resolved on oracle but your contract not updated
ResolutionSubmitted
event fired but your callback didn’t execute
Attestation verification failing
Attestation verification failing
Symptoms:Testing:
verifyAttestation()
returns false- Your contract rejects resolutions
- Code hash not approved:
- Attestation expired:
- Wrong verification library:
- TEE address not authorized:
Gas costs are too high
Gas costs are too high
Symptoms:
- Callback transactions cost too much gas
- Resolution requests expensive
- Efficient storage:
- Minimize callback logic:
- Batch operations:
- Use events instead of storage:
Contract deployment fails
Contract deployment fails
Common Issues:Deployment Checklist:
- Wrong oracle address:
- Missing interface implementation:
- Contract size too large:
- ✅ Correct network (mainnet/testnet)
- ✅ Correct oracle address for network
- ✅ Sufficient gas for deployment
- ✅ Contract verified on block explorer
Network & Infrastructure Issues
Transaction stuck in mempool
Transaction stuck in mempool
Symptoms:
- Transaction pending for long time
- Resolution not confirming
- Check gas price:
- Speed up transaction:
- Cancel transaction:
RPC node issues
RPC node issues
Symptoms:
- Contract calls failing intermittently
- “Execution reverted” with no reason
- Use reliable RPC providers:
- Implement retry logic: