⚡ Kleros Development Update | May 2026
Kleros Foresight opens the month: movies round 2 is now live, so you can trade today. Batch redemption shipped, redemption values were corrected with a pre-check before claiming, resolved answers now show right on the market cards, and a resolution email tells you the moment your winnings are ready to claim.
Kleros Skills is being prepared for launch: knowledge packs that teach AI agents how to use Kleros, whatever assistant they run on. The first two packs are almost ready. One lets an agent pin files to IPFS for $0.01 in USDC, the other lets it interact with
@KlerosCurate and Scout. A Kleros CLI, ERC-8004 agent verification, and an Escrow pack are on the roadmap.
Scout reached its definitive version: 2.6M curated addresses on the homepage, a dedicated new-submission page, a transaction-result page, and an in-app file viewer. Uploads now flow through Atlas with limits sourced from role restrictions, submissions defer uploads until sign-in, and ATQ duplicate detection plus JavaScript Court landed in the disputes view.
Atlas shipped v1.6.0. Signup is now per product: Court V1, Court V2, and Foresight each get their own confirmation email, unsubscribe link, and onboarding flow. Court reminders moved to a fixed, configurable time, and every batch send is preceded by a transaction simulation.
@proofofhumanity V2 email notifications now cover the complete profile lifecycle: pending revocations, vouching activity, disputed flows, and challenge outcomes, processed end to end by Atlas. Only the frontend opt-in toggle remains. An evidence-key fix means older cases render attachments properly again, and the referral system spec went through review.
Vea published the veashi-sdk to npm at v0.0.2, the first packaged version of the cross-chain SDK. The
@LayerZero_Labs contracts were reorganized under the adapter layout, the Hashi executor decoupling merged after April's review pass, and an
@envio_indexer HyperIndex indexer for the relayer is on the way.
Court V2: The contracts are being simplified, the partial-coherence kit was merged, and the security findings are being worked through. From here, the code heads into another round of internal reviews. We'd rather take the time and get it right.
Full breakdown 👇