Kleros Development Update — November 2025

Welcome to the November 2025 development update! This month brought significant achievements including the completion of the Curate V2 Tailwind migration, the launch of Tenderly simulations for Governor V2, the finished trade wallet system for Futarchy UI, and continued progress across Atlas notifications, Scout improvements, and cross-chain infrastructure.

November was an eventful month for the Kleros ecosystem, marked by major product milestones and community engagement at Devconnect Buenos Aires.

Court V2

Infrastructure & Backend Enhancements

The Atlas infrastructure saw significant improvements this month with the implementation of aggregated stake notification functionality for Court V1. The team built a sophisticated notification system that batches stake updates for email delivery, designed to reduce notification fatigue while keeping jurors informed about their staking activities. This feature is currently undergoing final testing before production deployment.

Staking History API received important updates with contract-address based filtering capabilities, allowing users to track staking events for specific contracts. The voting history endpoints were enhanced to support court ID filtering, making it easier to analyze voting patterns across different courts.

Integration testing was a major focus, with comprehensive test suites added for the scheduler service and various Court V1 notification workflows. These tests ensure system reliability and help catch issues before they reach production.

Contract Development & Deployment

The V2 contracts reached an important milestone with successful deployment to devnet, including the court and university court contracts. Following the completion of internal Reviews Round 4, the contracts have been submitted to Certora for external audit.

Key developments:

• Devnet Deployment: V2 contracts deployed to devnet with release candidate published to NPM
• Leaderboard Offset Contract: New LeaderboardOffset contract completed and currently under review, with subgraph updates prepared
• Subgraph Updates: Subgraphs updated with latest contract changes and deployed on Alchemy (core 0.18.1, drt 0.14.0)
• Kleros SDK: Updated callAction to allow single return values

Frontend Updates

The Court V2 frontend received updates to support the latest contract changes:

• Frontend (web and web-devtools) updated with latest contract changes
• Staking History feature implemented in Court and Juror Profile pages
• Neo references removed from web and subgraph deployments
• Testnet preview deployment available at deploy-preview-2197--kleros-v2-testnet.netlify.app

Subgraph Infrastructure

The team addressed subgraph-related changes including handling the removal of _coreRoundID from events, replacement of _externalDisputeID with _arbitratorDisputeID, and removal of evidenceGroupID. Discussions continued about deploying subgraphs on Goldsky as Alchemy announced the shutdown of their subgraph services, they migrated existing subgraphs to Goldsky.

🌐 Experience next-generation decentralized justice! Court V2 approaches full production deployment.

Curate V2

Tailwind CSS Migration Completed

November marked the completion of a major frontend migration! The entire Curate V2 frontend has been modernized, moving from styled-components to Tailwind CSS. This migration brings improved performance, better maintainability, and a more consistent design system.

The migration touched virtually every component across the application:

• Registry displays and item cards
• Form inputs and modal dialogs
• Navigation and settings panels
• Submit item and submit list flows

User Experience Improvements

Several usability enhancements were implemented:

• Address Input Validation: Refined to provide clearer feedback and better handle edge cases
• Registries Grid Responsiveness: Improved with new SM_BREAKPOINT for better mobile support
• Accessibility: ARIA labels added for interactive elements like PlusMinusField buttons and AttachmentDisplay
• Code Quality: Standardized import paths and improved class name readability

Contract & Template Work

Work continues on Curate V2 contract and template updates to better handle evidence submission and standardize how arbitrables provide evidence. These changes will create a more consistent experience across different types of registries.

🕵️ Join the curation revolution! Explore Curate V2 and contribute to decentralized registry curation.

Scout V2

Timeline & Status Enhancements

The Scout V2 item timeline received substantial improvements:

• Proper handling of multiple requests for the same item
• Clear display of registration challenges vs. removal challenges
• Appeals now show which side filed
• More accurate dates throughout the timeline
• Track case button always visible if there was ever a case

Export & Submission Fixes

• Export functionality refined to handle column selection more reliably
• Duplicate submission detection improved with clearer error messages
• Modal behavior fixed: modals now properly close after submission and clear form data

🕵️♂️ Explore Scout V2 and contribute to decentralized token curation.

Governor V2

Tenderly Simulations

A significant feature addition this month was the integration of Tenderly simulations for transaction proposals. Users can now simulate their proposed transactions before submission, providing confidence that governance actions will execute as expected.

The implementation includes:

• API routes for contract information retrieval and simulation execution
• State encoding utilities for accurate simulation
• Enhanced UI with external links and Tenderly branding
• Integration with the transaction builder interface

Contract & Template Deployment

• Governor V2 contracts and templates updated and deployed
• Etherscan verification tooling updated for latest contract versions
• Frontend updated to support new template with lists view in Dispute Overview
• Governor contract successfully separated into its own repository

Dispute Resolver

Dynamic Script Integration

The Dispute Resolver now supports fetching data from dynamic scripts, enabling more flexible evidence display configurations. This allows arbitrables to specify custom interfaces for presenting dispute information.

Realitio Case Handling

The team addressed issues with how the Dispute Resolver handles Realitio cases:

• Fixed incorrect ruling options display where "Yes/No" was shown instead of actual ruling options from metaevidence
• Created PR to fetch correct ruling options from court dynamic scripts
• Removed faulty cross-chain dispute assumptions that caused incorrect behavior in certain scenarios

Technical Improvements

• Fixed chain ID encoding in iframes ensuring proper communication between main application and embedded evidence displays
• Standardized address casing in arbitrableWhitelist for consistency
• Updated dependencies addressing security concerns (js-yaml, min-document)

Futarchy UI

Trade Wallet System Complete

The Futarchy interface underwent major development with the completion of the trade wallet system. Users can now:

• Deposit and withdraw DAI
• Mint and merge prediction tokens
• Redeem tokens after market resolution
• View project balances in an integrated interface

Prediction Interface Redesign

The prediction popup was completely redesigned with a multi-step flow:

• Clear step indicators with visual progress
• Improved error display and handling
• Better button loading states
• Market price initialization on load
• Input values reset after transaction completion

Liquidity & Pricing Enhancements

New hooks were added for enhanced market analysis:

• Current market prices calculation
• Volume until target price calculation
• Tick data retrieval from liquidity pools
• Capped balance management for safer trading

Polish & Refinements

• Updated metadata and favicons for professional appearance
• Responsive design improvements
• Redeem button hidden until markets resolve
• Various UI text updates for clarity

📊 Predict with precision! Futarchy

Atlas & Notifications

Court V1 Notifications

The Atlas notification system expanded significantly with aggregated stake notifications for Court V1:

• Immediate email dispatch for stake-related events
• Sophisticated batching logic to reduce notification fatigue
• Critical documentation explaining aggregation behavior
• Comprehensive integration tests for notification workflows

Staking History API

New contract-address based filtering enables users to track staking events for specific contracts. The voting history endpoints were enhanced to support court ID filtering for better analysis of voting patterns.

Infrastructure Improvements

• Scheduler service integration tests added for system reliability
• GraphQL improvements with better contract event handling
• Type standardization for blockchain hashes across DTOs and entities
• DispatcherService made optional in event reaction services for deployment flexibility

VEA (Cross-Chain Bridge)

Secondary Validator Implementation

The VEA infrastructure continued advancing with secondary validator bot implementation underway. This provides additional redundancy for cross-chain message verification.

AWS Deployment

Migration and deployment to AWS infrastructure is in progress, improving reliability and scalability of the bridge services.

🌉 Bridge with confidence! Experience secure cross-chain messaging with VEA.

Reality & Cross-Chain

Proxy Updates

The proxy address list was expanded with new deployments:

• Precog Base proxy added
• SUKU proxies integrated

Bridging Documentation

Documentation for bridging was enhanced and L2 bridging scripts were updated to reflect current best practices.

Lemon Mini-App

Development continued on the Kleros-Lemon integration with experimentation on wallet provider integration. The team explored approaches using custom Wagmi/Reown connectors with the Lemon SDK to address high query loads in the mini-app frontend.

Proof of Humanity V2

zkPoH Progress

The zkPoH implementation advanced with end-to-end testing and scripting continuing throughout the month. This privacy-preserving humanity verification system represents a significant step forward for the protocol.

Looking Ahead

December priorities include:

Contract & Deployment

• Continue external audit preparations for Court V2
• Deploy refined contracts through testing environments
• Advance Curate V2 contract and template updates

Product Development

• Complete VEA secondary validator implementation and AWS deployment
• Continue Futarchy interface refinements
• Expand Scout V2 based on user feedback
• Progress Lemon Mini-App integration

Infrastructure

• Expand Atlas notification capabilities
• Complete subgraph migrations and optimizations
• Continue documentation reviews across products

Get Involved

Discord: Join our server for real-time discussions
Twitter/X: Follow us for latest updates
Telegram: Connect with our community
GitHub: Explore our repositories
Documentation: Comprehensive developer resources

Want to contribute? Check out our GitHub repositories and join the conversation!