Protocol Separation: AnchorWorks and ForgeRun
AnchorWorks is infrastructure built on the ForgeRun protocol. ForgeRun is a neutral, open transparency ledger. AnchorWorks constructs Merkle trees and publishes evidence. Verifiers need not trust AnchorWorks.
ForgeRun: The Protocol
ForgeRun is a neutral, open transparency protocol providing an append-only ledger for time-anchored commitments. It does not evaluate, interpret, or validate what is committed.
AnchorWorks: The Infrastructure
AnchorWorks builds runtime infrastructure that uses ForgeRun as its transparency substrate. It constructs Merkle trees, manages batches, and publishes commitments.
Trust Implications
Verifiers need not trust AnchorWorks. They can independently verify evidence using ForgeRun's public ledger and standard cryptographic tools.
Understanding the distinction between ForgeRun (the protocol) and AnchorWorks (the infrastructure provider) is essential for evaluating trust boundaries.
ForgeRun: The Protocol
ForgeRun is a neutral, open transparency protocol. It provides an append-only ledger for time-anchored commitments. ForgeRun does not evaluate, interpret, or validate what is committed.
- Open transparency protocol
- Append-only ledger
- Time-anchored commitments
- No content evaluation
AnchorWorks: The Infrastructure
AnchorWorks builds runtime infrastructure that uses ForgeRun as its transparency substrate. AnchorWorks constructs Merkle trees, manages batches, and publishes commitments.
- Runtime adapter infrastructure
- Merkle tree construction
- Batch management
- Evidence locker storage
Trust Implications
This separation means verifiers need not trust AnchorWorks. They can independently verify evidence using ForgeRun's public ledger and standard cryptographic tools.