Kleros Development Update February 2026

Court V2

February's focus was on working through the Certora audit findings. The final report was shared internally, and each finding was reviewed, with the team separating valid issues from suggestions considered over-engineering. A new tracking issue was opened to coordinate changes across dependent services.

On the contracts side, the Argentina Consumer Protection Dispute Kit was merged and confirmed as gated. Due to conflicts with a prior PR, changes were applied manually. The plan is to merge everything and redeploy devnet, with no contract changes required.

Frontend progress this month:

• The first SBT-gated dispute was successfully tested in the beta environment after resolving a subgraph sync issue that caused the frontend to point to the wrong DisputeKit contract.

Court V1

Dark mode went live, kicking off at the end of January, merged, and shipped to production.

Court V1 can now be accessed without a connected wallet, defaulting to view mode with a Connect prompt rather than blocking the UI entirely.

Beyond dark mode, eleven PRs merged during the month:

• January staking rewards added
• Color adjustments for visual consistency
• Menu navigation highlight fix for active state not reflecting correctly
• Error boundary fallback to prevent blank-screen failures
• Hardcoded subgraph URLs for Chiado and Sepolia replaced with environment variables
• iframe sandbox fix to allow popups to escape correctly
• Valid RPC restored for APY and reward calculations that had broken
• Seer Curate on Gnosis added to whitelist
• Kleros Tokens Registry added to whitelist

Escrow V2

February brought a production sync for Escrow V2. The dev branch was merged into master, meaning improvements that had been building up on dev were now reflected in the live environment.

Several fixes went in ahead of and alongside the launch:

• Token decimal assumption bug fixed: V2 had assumed 18 decimals for all tokens, which broke USDC and USDT support. The fix was verified with ETH, PNK, and USDC.
• Subgraph 2.2.1 deployed on Goldsky after a 2.2.1-test version synced cleanly without errors.
• Policies dropdown and enhanced file viewer added for attaching and viewing policy documents in transactions.
• Minor UI/UX improvements merged, including a discussion around adding Etherscan transaction links to the timeline (similar to how Court V2 handles dispute history).
• The display issue for very small escrow amounts (< 0.0001) resolved.
• The issue with checking the seller's address was resolved.

A generic escrow policy and best practices document were finalized and uploaded to IPFS. A .json MIME type issue in Atlas was caught and fixed during this work: the Policy role was rejecting .json uploads with an "Unsupported mime type" error. JSON was added as a valid MIME type.

On Escrow UI (V1), two improvements shipped in February:

• Token blacklist for unsupported tokens with toast notifications to inform users when a token cannot be used.
• Alert for non-standard ERC20 tokens in the token selector modal, surfacing a warning before a user proceeds with a token that may cause issues.

Dispute Resolver

Four PRs merged in February:

• Kleros Tokens Registry whitelisted
• Seer Market registry contracts whitelisted
• Broken evidence attachment links fixed: links were failing to render in certain dispute contexts
• iframe sandbox fix matching the fix applied in Court V1

Scout

February brought the chain and reward formula update announced at the end of January. MegaETH and Polygon are now eligible chains, and PulseChain support is live. The new reward formula has been running since February 1st. It distributes more fairly to newer projects while still rewarding high-activity tokens. Each registry stays at 100,000 PNK.

Code-side updates merged this month:

• Feedback improvements: better display for pending and resolved items
• Date handling fixed across the board to enforce UTC consistently
• Carousel optimization and date display fix
• Reward card click bug fixed

Scout 2.0 work is underway. Planned features include CSV export, analytics, and dispute management tooling. On the Atlas backend, issues were opened to migrate the Scout API to a local DB rather than forwarding all queries to Envio, build a bot to fetch and store data continuously, and set up a centralized DB covering ATQ and three other registries.

Atlas (Backend Services)

Atlas shipped v1.2.1

Key changes in this release:

• Multi-round vote reminders: jurors in multi-round disputes now receive correctly scoped reminders per round
• feeTokenSymbol fixed per chain: was previously resolving incorrectly across chains
• Gateway health decoupled from bot health: bot downtime no longer takes down the gateway
• viem safeFee fix: tx nonce was being returned incorrectly
• t2cr-to-IPFS bot merged: automates uploads of T2CR metadata to IPFS
• Seer credits bot merged after an extended review cycle
• Two deployment scripts consolidated into one

Testing infrastructure improvements:

• Template data validation added to Court V1 integration tests
• createServices helper extracted to a shared Court V1 helpers file
• Court V1 event reactions reorganized into a separate folder
• Custom error class added for missing contract events
• Zero values omitted from time format output for cleaner notification copy

The ongoing work as we move into March includes a votes endpoint supported by the database, backup court names to prevent issues with court name resolution that could stop notifications, tracking delivery status with SendGrid, verifying webhooks, and notifications for pending submissions in PoH V2.

Note: Atlas remains an internal backend library for Kleros development teams only and is not intended for community use or integration.

Vea (Cross-Chain Bridge)

Vea's bridge infrastructure expanded on two fronts in February: adding DeBridge as a second bridge protocol alongside LayerZero and getting the second Vea validator operational.

DeBridge integration:

The DeBridgeReporter contract was debugged, and two issues were resolved: a flag was added to expose the sender address correctly, and DeBridge's own chain ID format was adopted for source chain verification. Deployment scripts were written, a full end-to-end message was tested, and an execution fee increase on Story resolved the issue that required manual claiming on the Arbitrum side.

Second validator:

The second validator for Vea is now operational. A static call was added to the relayer to verify message execution after the threshold is met before batching, preventing incorrect batch submissions.

Hashi refactored into the Vea monorepo:

The veashi-contracts workspace was created inside the Vea monorepo. Contracts and the SDK package were moved over from the standalone hashi-lightbulb repo. The Hashi lightbulb frontend was updated to consume the new veashi package. The SDK is packaged with Typechain types and extracted ABIs and is ready to publish under the Kleros organization.

Relayer RPCs for Story and Arbitrum were also updated.

Kleros Foresight (Futarchy UI)

The project got its official name this month: Kleros Foresight.

February was heavy on UX and reliability work, driven by the movie experiment launch. Here is what shipped:

• Onboarding guides merged, with guide links, illustrations, and layout iterated throughout the month
• Transaction chunking: large prediction batches are now split into multiple transactions to stay within gas limits. This directly addressed the 16-movie-prediction gas ceiling issue.
• Predictions now persist on reload
• Collateral buffer added to handle edge cases in prediction calculations
• Luminance-based text color selection, adapting text color based on background brightness
• Scroll fade container for long content sections
• Slider clipping fix and center alignment fix
• First prediction calculation fix
• The guide button repositioned, guide modal responsiveness fixed on small-height screens
• RealT API wrapped with a 24-hour cache so property data loads dynamically without manual extraction

Reality (Oracle)

Automatic verification of Reality questions was merged. The Zodiac bot now validates keccak hashes for Reality questions automatically. When it cannot validate a hash, it issues a warning rather than failing outright.

Additional work this month:

• Fix opened for Reality questions with no linked Snapshot proposal
• Reality links normalized to consistent casing
• The partner notification approach worked out for incorrect answers, to notify before deposits are lost rather than after

Seer proxy contracts on Base and Optimism received minor low-risk updates.

Proof of Humanity V2

PoH V2 continued operating post-airdrop. A ledger compatibility issue surfaced: hardware wallets do not currently support EIP7702 on Gnosis Chain, which is required for the standard airdrop claim flow. A manual claiming and staking guide was put together for affected users.

PoH V2 pending submission notifications are in development in Atlas.

Join the Kleros Community!

• Join our Discord
• Follow us on Twitter
• Join the community on Telegram
• Explore our documentation