Your responsibilities as a resolver
Being listed in the resolver catalogue makes you a service provider to Melee’s market creators and traders. This page collects the expectations spread across the specification into one place. Where a policy has a number, the number is stated.
Availability
| Expectation | Detail | If not met |
|---|---|---|
Keep GET {baseUrl}/health (unsigned) answering 200 { ok: true } | probed every few minutes while you are Active | 5 consecutive failures, the first at least 15 minutes ago → Unhealthy: not selectable for new markets; existing markets unaffected; POST /resolvers/me/reinstate when fixed |
Answer decision calls (evaluate, accept, change) synchronously | within 30 s by default; up to 120 s by prior agreement | treated as refused; the creator cannot proceed with you for that draft or change |
Acknowledge live and applied | answer within the same handshake timeout; these are notifications, so a missed answer is not a refusal: Melee re-delivers the same notification (same X-Melee-Delivery-Id) with exponential backoff for up to 24 hours until you acknowledge | the market cannot launch until you acknowledge; after 24 hours without acknowledgement the delivery is dead-lettered and flagged to Melee |
Answer trigger, lifecycle, cancelled, RulesRequest with 2xx | within 10 s | retried with exponential backoff for 24 h, then dead-lettered and flagged to Melee |
Answer GET {baseUrl}/status/{market} | polled every 30 min before your trigger, 5 min after, 1 min while a proposal stands | invalid past timeoutTs displays to traders as Unknown; Melee does not void for it |
Security
- Verify our HMAC on every inbound request except
health, using the secret named byX-Melee-Key-Id, and reject timestamps more than 5 minutes from your clock. Deduplicate onX-Melee-Delivery-Id. - Keep
resolverAuthorityandproposerAuthorityunder your control. They are bound to every market you accept and cannot be changed for those markets. A compromised key means voiding your open markets. - Rotate
apiSecretandcallbackSecretif exposed; both have a 1-hour overlap on rotation. If that is too long, ask Melee to revoke them. - Check every transaction before signing it (Integration reference).
- Validate every
programIdagainstGET /platform/programs; ids change and several may be live at once (Environments & testing).
Evaluation and acceptance
- Score honestly under the confidence policy.
0means “no”. Your floorminConfidenceBpsis binding on you: refuse anyacceptfor a hash you scored below it. - Use
proposedDefinitionto make a market resolvable, not to change the question. SetendDatewhen the creator omits it. - Sign acceptance evidence only for hashes you have evaluated. The signature is the durable record of your agreement.
- Verify
liveandappliedpayloads against the chain (Verifying the definition) before acknowledging. An unacknowledged market never launches.
While the market is live
- Own the rules. If the rules need clarification for you to resolve correctly, update them through the rules update process, with a rationale, before you resolve. Creators can only ask; you decide, and you can answer them.
- Keep your status accurate.
Resolvingwhile you are working,Disputewhile your dispute process is open,Pendingotherwise. Yourmessageis shown to traders verbatim. - Act on the trigger.
endDateis when you are told to start, not a deadline. Resolve as soon as the outcome is determinable and well beforetimeoutTs.
Resolving
- Always send the current
definitionHashwithpropose,resolveandvoid. A stale hash is refused (definition_mismatch); re-read the definition and decide again. - Disputable resolvers propose first, run their dispute process, then resolve the same outcome. A proposal you
no longer stand behind is changed with
proposeagain or cleared withreject. - Void when the event is cancelled or the question cannot be answered under the rules. Voiding refunds traders and pays you no trading-based fee. It is preferable to a forced outcome.
- Sign and submit transactions promptly; envelopes expire about 25 seconds after issue.
Fees
- Keep
upFrontFeesaligned withGET /platform/creation-fee-mints. If no entry matches a market’s creation-fee mint, your index-0 amount is charged verbatim in that mint’s base units. Misconfiguration is your cost, not the creator’s. - Fee terms are stamped per market at creation and never change for that market. The recipient wallet of an
existing market can be changed with
PUT /markets/{market}/fee-recipientonce resolution fees exist (Contract versions).
Melee’s policies that affect you
| Policy | Value |
|---|---|
| Platform minimum confidence | 9000 bps, may be raised for an individual resolver |
| Handshake timeout | 30 s default, 120 s maximum |
| Draft expiry | 24 h without a creator decision |
| Void by Melee (void authority) | never for time alone. Only when the market’s on-chain authorities or outcome count drifted from what you accepted (AuthorityDrift, DefinitionDrift) or an operator intervenes, for example on suspension (Operator). The void is sent once timeoutTs plus 24 hours has passed, the earliest the program allows plus a grace. You are notified with PlatformVoided and the reason (Platform void) |
| Launch gate | a market launches only after you acknowledged live; there is no override |
| Verification badge | granted by Melee after review of your integration, scoring and rules-update patterns; unverified resolvers are still selectable and the badge is shown to creators |
Unhealthy | 5 consecutive health failures over at least 15 min; self-service reinstatement after the smoke check passes |
| Suspension | set by Melee for bad faith; reads only, no self-service way back (Suspension) |
| Rules history | every rules change, by you or the creator, is public with attribution and rationale |
What Melee commits to you
- Nothing is created on-chain with your keys before you accept, and nothing launches before you acknowledge.
- Every payload carries the
definitionVersionanddefinitionHashit reflects, plus the on-chain facts you need to verify independently. - You are notified of every phase change of every market you accepted, including cancellations before launch.
- Your acceptance evidence, rules updates and status messages are shown to traders as you provided them.
Last updated on