Secured Logs: Furthering Tech Enabled Fairness

Secured Logs: Furthering Tech Enabled Fairness

Authored by Saurabh Nambiar and Subbaiah KG

Sometime  ago, during a regular conversation, an individual raised a straightforward yet important question:
“Once I’ve submitted a claim or response on the ODR, how do I trust it wasn’t changed/tampered later?”

In a physical courtroom, seals, signatures, and case files offer that assurance. But in a digital environment, especially one dealing with legal evidence, claims, and counterclaims, the stakes are high, and integrity cannot rely on perception alone.

At CADRE ODR, we handle multiple communications/interactions every day. Our role is not only to provide a legally binding mechanism for resolving disputes online but also to ensure that every step of the process is conducted with full procedural fairness and trust. To build trust that goes beyond mere words, , we’ve incorporated a technologically sound system that enables parties to verify the authenticity of their submissions, independently and transparently.

Why Secured Logs Matters in ODR

Every dispute is a timeline of interactions: claims, defenses, and evidence. If even a single submission is altered, or suspected of being altered, it can undermine the entire proceeding.

ODR is built to be faster, more accessible, and more efficient than traditional methods for various types of cases. But it must also be verifiable. The ability to confirm that nothing has been modified after the fact is a foundational requirement for any digital legal system, as this ensures fairness and legal credibility of the proceedings. At CADRE, this starts with a simple principle: fairness must be embedded into every touchpoint, from submission to final award.

Exploration/ Mapping of systems for verifiability

To ensure that our users can trust what happens on the platform, we evaluated several methods for securing the integrity of interactions before implementing our current system. Here are the main approaches we explored:

  • Cryptographic Hashing (SHA-256)
    A hash is a fixed-size string of characters (like a fingerprint) that is generated by passing a document (e.g., a file, message, or password) through a hash function. Even a small change to the document alters the hash entirely. This technique allows tamper-proof evidence without exposing the actual content.
  • Public Anchoring
    Hashes can optionally be published to public repositories like GitHub or third-party registries. These time-stamped records serve as immutable proof points that can be accessed outside the platform if needed.
  • Merkle Trees for Batch Verification
    Where multiple messages are part of a single proceeding, Merkle Trees enable platforms to generate a single root hash while preserving the ability to verify each message individually.
  • Decentralized Anchoring
    Storing these hashes on blockchain networks (like Ethereum) or decentralized systems like IPFS. These systems offer increased durability and trustless transparency.
  • Verification Across Interfaces
    To ensure consistent trust across user dashboards, admin tools, and APIs, synchronizing verification status across the system was also considered as part of future expansion.

CADRE’s Promise: What features End Users can expect: Features for End Users

CADRE’s platform now integrates these integrity features directly into the workflow. Users can:

  • Verify Message Integrity
    Confirm whether a message matches the original submission, based on its hash.
  • Publish Fingerprints
    Opt to anchor message hashes in a public, time-stamped record.
  • Access a Submission History
    View all previous integrity records for reference, including those already published.

These features are accessible with no technical expertise required and are designed to support users, arbitrators, and even courts in verifying authenticity.

The Way Ahead

As ODR adoption grows, a key question emerges: Should India build  a neutral, shared infrastructure to verify digital legal records across platforms? Just as e-filing standardized court access, a public verification layer could allow independent confirmation of submissions—reducing reliance on individual platform systems and enhancing trust, consistency, and interoperability.

At CADRE, we believe fairness begins with process integrity. Securing and verifying every submission is central to that goal. As digital justice evolves, verifiability must remain a foundational standard.