What Kervyxa doesn't do yet, stated plainly.
Kervyxa claims one thing: payment is released only for a verified result, and if no qualifying submission succeeds before expiry your funds are refunded according to the contract terms. It does not claim guaranteed delivery, savings, or superiority over hiring a person directly — in any mode. Below is what's actually missing or constrained today, not a vague disclaimer.
Known limitations
Kervyxa itself decides challenge outcomes in this version — there is no permissionless challenger network or staked verifier marketplace. Every resolution is auditable after the fact through the Resolution Proof, but it is not decentralized adjudication.
A contract can only pay out on FIRST_VERIFIED_PASS — the first submission whose pass survives the challenge window takes the whole reward. Highest-score, ranked prizes, and pay-per-valid-unit are not implemented, even where a draft's wizard shows them.
A DRAFT → CANCELLED status exists in the underlying state machine, but nothing in the application actually reaches it: there is no API route and no UI to cancel a contract, draft or otherwise.
Replaying the identical winning commit's benchmark was measured to vary 4x-19x in duration purely from host load. Time-thresholded benchmarks are excluded from approval until that's resolved, so "must run in under N seconds" is not a criterion Kervyxa can verify fairly today.
The verifier clones over https and checks out a specific commit, with no credential of any kind and no network access inside the container that runs the checks. Private repositories are not supported. Invite-only routing restricts who may submit and keeps a contract off the public marketplace listing, but it does not let the verifier read proprietary code — so open competition over a private repository is not something Kervyxa offers.
Escrow and verification decide who gets paid; they do not make anyone show up. If no submission passes verification and survives resolution before the contract expires, the requester is refunded under the contract's terms — that is the only promise. "Delivered by Kervyxa" is a hand-reviewed intake queue that can approve an outcome, propose converting it to open competition, or decline it. Its eligibility check is coded never to return "eligible" in this version, so nothing is ever routed into a guaranteed lane. Kervyxa does not bear execution risk on a requester's behalf today.
The deliverable is a git commit. There is no route that packages a run's outputs, logs, or build artifacts for a requester to download — you get the winning commit and the Resolution Proof, and anything else must be reproducible from those.
Specifications, submissions, verification logs and evidence are kept indefinitely. There is no implemented retention or deletion schedule, and no self-service way to have a contract's off-chain record removed.
Kervyxa settles real USDC on Solana mainnet-beta. It has not processed a large volume of contracts. Treat it accordingly: start with a contract whose reward you're comfortable putting at risk while the platform is early.