Composability and Reuse

One of the most powerful properties of atomic claims is their composability—the ability to combine verified claims into more complex verifications and reuse claims across multiple applications. This composability creates network effects where each verification adds value to the ecosystem beyond its immediate use case.

Claim Composition

Applications can compose multiple atomic claims into compound verifications that prove complex statements. For example, a lending protocol might require verification of multiple claims: identity verification, income verification, employment verification, and credit history verification. Each of these can be verified independently as atomic claims, with the lending protocol checking that all required claims are verified before approving a loan.

Claim composition enables modular verification where applications specify required claims without needing to understand verification details. The protocol handles routing claims to appropriate validators, generating proofs, and providing results in a format that applications can easily consume. This abstraction simplifies application development and enables rapid innovation.

Cross-Application Reuse

Verified atomic claims can be reused across multiple applications without requiring re-verification. Once a user has verified their identity, income, or other attributes, these verifications remain valid for a specified time period and can be referenced by any application the user authorizes. This reuse reduces verification costs, improves user experience by eliminating redundant verification processes, and creates network effects where the value of the verification network increases as more claims are verified.

The protocol implements access control mechanisms that enable users to selectively share verified claims with specific applications. Users maintain control over their verification data, granting or revoking access as needed. Applications receive only the proofs they need, with privacy specifications ensuring that sensitive information remains confidential.

Claim Dependencies

Some atomic claims depend on other claims being verified first. For example, verifying a specific financial transaction might require first verifying the authenticity of account statements that document the transaction. The protocol supports claim dependency graphs that specify these relationships, automatically verifying prerequisite claims before attempting dependent claims.

Dependency management enables efficient verification of complex claim structures while maintaining correctness. The protocol optimizes verification ordering to minimize latency, processing independent claims in parallel while respecting dependency constraints. Dependency information also helps applications understand verification requirements and estimate completion times.