Skip to main content
Public verifiability is a core principle of the Kwala network. All core activity logs and proofs are stored immutably on the Kalp Chain, enabling complete transparency and auditability of workflow executions. Kwala ensures that every workflow execution can be independently verified by anyone. This transparency creates trust without requiring users to rely on any single party, including Kwala itself.
Kwala Public Verifiability Architecture

​
Verifiability features

FeatureExplanation
Intent hashingEach user’s workflow intent is hashed and logged with their signature
Execution logsActions, inputs, results, and metadata are logged in Merkle-tree-based structures
Verifier reportsVerifier nodes post zero-knowledge proofs or full logs to validate action correctness
AuditabilityAny third party or regulator can replay and verify historical workflow executions

​
Intent hashing

When a user submits a workflow, the complete YAML definition is cryptographically hashed and stored on Kalp Chain alongside the user’s signature. 
┌─────────────────────────────────────────────────────────┐
│                    User Workflow                        │
│  ┌─────────────────┐    ┌─────────────────────────────┐ │
│  │   YAML Intent   │───▶│   Keccak-256 Hash           │ │
│  └─────────────────┘    └─────────────────────────────┘ │
│           │                          │                  │
│           ▼                          ▼                  │
│  ┌─────────────────┐    ┌─────────────────────────────┐ │
│  │  User Signature │    │   On-Chain Record           │ │
│  └─────────────────┘    │   - Intent Hash             │ │
│                         │   - Signature               │ │
│                         │   - Timestamp               │ │
│                         └─────────────────────────────┘ │
└─────────────────────────────────────────────────────────┘
This creates a non-repudiable record that:
  • Proves the user authorized the specific workflow
  • Cannot be altered after submission
  • Serves as the reference for all verification

​
Execution logs

All workflow executions generate detailed logs stored in Merkle-tree-based structures on Kalp Chain.

​
Logged data

Data typeDescription
Trigger dataThe event or condition that activated the workflow
Input parametersAll values passed to workflow actions
Action resultsOutputs and return values from each action
State transitionsChanges to on-chain state caused by the workflow
TimestampsPrecise timing of each execution step
Node identityWhich execution node processed the workflow

​
Merkle tree structure

Execution logs are organized in Merkle trees, enabling:
  • Efficient verification: Verify specific log entries without downloading entire history
  • Tamper detection: Any modification invalidates the Merkle root
  • Compact proofs: Generate small proofs for specific execution claims

​
Verifier reports

Verifier nodes submit reports to Kalp Chain that attest to execution correctness.

​
Report types

Zero-knowledge proofs

Cryptographic proofs that verify execution without revealing sensitive data

Full execution logs

Complete step-by-step records of workflow re-computation

​
Report contents

Each verifier report includes:
  • Reference to the original intent hash
  • Execution proof from the executor node
  • Verifier’s independent computation result
  • Attestation or dispute status
  • Verifier node signature

​
Auditability

Any third party or regulator can replay and verify historical workflow executions using the public records on Kalp Chain.

​
Audit process

1

Retrieve intent

Fetch the original workflow definition and user signature from Kalp Chain using the intent hash.
2

Retrieve execution logs

Download the Merkle-proofed execution logs for the specific workflow execution.
3

Replay execution

Using the logged trigger data and inputs, independently re-execute the workflow logic.
4

Compare results

Verify that the replayed execution matches the logged results and verifier attestations.

​
Audit use cases

Use caseDescription
Regulatory complianceDemonstrate automated actions followed approved policies
Dispute resolutionProvide evidence in case of contested transactions
Security auditsVerify no unauthorized actions were executed
Operational reviewAnalyze workflow performance and behavior

​
Benefits of public verifiability

​
For users

  • Transparency: See exactly what actions were taken on your behalf
  • Accountability: Hold execution nodes responsible for their actions
  • Trust: Verify without relying on any single party

​
For enterprises

  • Compliance: Meet regulatory requirements for audit trails
  • Risk management: Independently verify automated operations
  • Due diligence: Audit third-party workflow providers

​
For the network

  • Integrity: Ensure all participants follow the rules
  • Decentralization: Remove reliance on trusted intermediaries
  • Security: Detect and penalize malicious behavior

​
Accessing verification data

​
Kwala Explorer

The Kwala Explorer provides a user-friendly interface to:
  • View workflow execution history
  • Inspect execution logs and proofs
  • Verify specific transactions
  • Download audit reports

​
Kalp Chain direct access

Developers can query Kalp Chain directly to:
  • Retrieve raw execution proofs
  • Verify Merkle proofs programmatically
  • Build custom audit tools
  • Integrate verification into applications

​
Next steps

Verifier nodes

Learn how verifiers validate executions

Kwala Explorer

Explore workflow executions