Resolvement
Sentico uses two different resolution paths for outcome markets. Spot markets do not use this flow.
Binary Options
Binary Options resolve automatically through an oracle median policy.
Each Binary Option has an oracle binding and deterministic cutoff rules. When the market reaches its resolution point, Sentico reads the configured exchange sources, takes the median value, and applies the market rule against that value.
The result is binary:
| Side | Final value |
|---|---|
| Winning side | 1.00 |
| Losing side | 0.00 |
After the outcome is set, resolved positions move into the normal settlement path. Settlement remains validator-verified before withdrawals become final.
Prediction Markets
Prediction Markets use an economic dispute process because the answer often depends on public evidence rather than a single exchange price.
Any eligible wallet can submit a resolution case through the API once the market is closed or halted:
POST /api/v1/protocol/markets/{market_id}/resolution-cases
The resolver submits:
- proposed outcome,
YESorNO, - a signed payload,
- claim text,
- evidence artifacts or source links,
- a resolution bond.
When the bond is accepted, the market is halted for the challenge and review window. The default challenge window is 24 hours.
Bond And Incentive
The bond exists to make low-quality or dishonest resolution attempts expensive.
For Prediction Markets, the bond is computed from the market-size snapshot. The current implementation uses 1% of the market-size snapshot, bounded by a minimum and maximum protocol limit.
If the resolver is correct:
- the resolver bond is refunded,
- the resolver earns the resolution fee,
- the resolution fee is funded from the winning-side settlement payout.
The resolution fee is currently 1% of the market-size snapshot.
If the resolver is wrong:
- the resolver bond is slashed,
- the slashed bond goes to protocol treasury handling,
- the incorrect resolver does not receive the resolution fee.
Challenges
During the challenge window, another eligible wallet can challenge the submitted outcome:
POST /api/v1/resolution-cases/{case_id}/challenges
The challenger must submit a different outcome, evidence, and a matching bond.
If the resolver is correct, the resolver bond is refunded, the challenger bond is slashed, and the resolver can receive the resolution fee. If the challenger is correct, the challenger bond is refunded and the resolver bond is slashed.
Finalization
After the challenge window, the case is finalized against the submitted evidence, market rules, fallback policy, and operational review.
Finalization sets the market outcome, records the audit trail, and triggers resolved-position settlement. Users should treat resolved payouts as final only after the corresponding settlement path has completed.
API Surface
Useful public endpoints:
| Endpoint | Purpose |
|---|---|
GET /api/v1/protocol/markets/{market_id}/resolution-dashboard | Read current resolution state and recent cases |
GET /api/v1/protocol/markets/{market_id}/resolution-simulator | Preview eligibility, bond, fee, and timing |
POST /api/v1/protocol/markets/{market_id}/resolution-payload-hash | Compute the payload hash to sign |
POST /api/v1/protocol/markets/{market_id}/resolution-cases | Submit a resolver proposal |
POST /api/v1/resolution-cases/{case_id}/challenges | Challenge an active resolver proposal |