Skip to main content

Auditing

This section documents Tessera's implementation of JAM's auditing and judgment system for off-chain work-report validation.

Overview​

The auditing system ensures that work-reports are validated by a distributed set of validators through:

  • Audit engine: Core logic for managing the audit lifecycle
  • Judgment system: Publication and aggregation of audit verdicts
  • Tranche management: Time-based assignment and scheduling of audits
  • Finality prerequisites: Ensuring sufficient positive judgments before finalization

Topics in this section​

6.1 Audit Engine & Lifecycle​

The audit engine manages the complete validation flow:

  • Work-report selection for auditing
  • Auditor assignment per tranche
  • Audit execution and validation
  • No-show detection and handling

References: Gray Paper Section 17 (Auditing)

6.2 Judgments & Tranches​

Time-based audit scheduling and verdict collection:

  • 8-second tranche intervals
  • Announcement and judgment publication (CE 144, CE 145)
  • Positive, negative, and no-show tracking
  • Finality threshold (>682 positive votes per report)

References: Gray Paper auditing section, JAMNP-S CE 144-145

Implementation notes​

Core implementation is in tessera/jam/audit/ with:

  • audit_engine.py: Main engine and tranche management
  • auditor.py: Individual audit execution
  • Network protocols in tessera/jam/network/protocols/ce_144.py and ce_145.py

📘 Next: Read the detailed Audit and Judgments implementation guide