Skip to Content
Draft v0.2 — this specification is under active design and may change before implementation.

Keys

KeySignsLevel requiredNotes
resolverAuthorityresolve, void, reject; fee-recipient changes; acceptance evidenceMelee user account, created for you at activationBound to each market at creation. Immutable per market. Must be fresh at registration.
proposerAuthorityproposeMelee user accountOptional; only for disputable resolvers. Defaults to resolverAuthority.
feeRecipientclaims feesany walletPer-market recipient can be changed later by resolverAuthority (below).
payerpays fees and rentany wallet with SOLDefaults to resolverAuthority; may be any key you control.

All keys are Solana Ed25519 keypairs. Public keys are base58 in every payload. In market payloads the bound keys appear as authorities: { resolverAuthority, proposerAuthority }; for a non-disputable resolver both values are equal.

Changing the keys on your record is coming soon. The change needs an on-chain transaction; until this API issues it, PATCH /resolvers/me refuses a new resolverAuthority or proposerAuthority with 422 invalid_config (not_patchable). Once it arrives, markets already created keep the old key, so keep it available until those markets are resolved. A compromised key means voiding your open markets.

Acceptance evidence

When you accept a market or a change to it, you sign the agreed definition hash with resolverAuthority: a 64-byte detached Ed25519 signature over the raw UTF-8 bytes of melee-accept:v1:{marketPubkey}:{definitionHash}, base58-encoded. No Solana off-chain-message wrapper. Melee stores that signature as the record of what you agreed to and shows it in GET /markets/{market}/definition. A test vector is in the Integration reference.

Fee recipient per market

Fee terms (rate and up-front fee) are stamped per market at creation and never change for that market. The recipient wallet of an existing market can be changed by resolverAuthority with PUT /markets/{market}/fee-recipient { feeRecipient, payer? }, which returns a transaction envelope. This does not change your record’s default feeRecipient for future markets. On the current program markets have no resolution fees, and this call answers 501 feature_unavailable.

Payer

Every transaction we return has a separate payer that funds the network fee and any rent the transaction creates. It defaults to resolverAuthority, but you may pass any key you control in the payer field of an action request. The payer is never read for authorization, so a dedicated gas wallet is fine. The signers list in every envelope tells you exactly which keys must sign, and estimatedLamports tells you what the payer will spend. Fund the payer with SOL on the target network; see Environments & testing.

Last updated on