Where VEST Sits Next to Trillian, CT, and a Blockchain

What this means for you

The category VEST is in already exists. Google has been running a verifiable log called Certificate Transparency since 2013, and the open-source backend that powers it is called Trillian. Binary Transparency, a sibling effort, logs Android firmware so a phone can verify it before it boots. None of these were built for real-time collaboration on documents and automated decisions. VEST adds three things on top of Trillian: dual-signature attestations, causal ordering of operations, and per-event proofs that can carry confidential payloads.

The pitch

Do not compete with Certificate Transparency or Trillian. Stand on them. The research positions VEST explicitly as a Trillian “personality”, a domain-specific layer that reuses the backend used by every major browser to verify HTTPS certificates, and adds the three capabilities the existing logs do not have.

Who it’s for

The technical buyer or partner who has heard “verifiable log” before, and wants to know what VEST adds that the existing systems do not already give them.

Proof points

• Trillian and Tessera are Google open-source projects with public benchmarks: 10 million entries per day handled in production CT deployments, sub-second proofs at planetary scale
• VEST adds three capabilities the research documents call out as absent in CT, Binary Transparency, and Key Transparency: real-time append at under 70 milliseconds, dual-signature or threshold-signature attestation, and Lamport-clock causal ordering between operations
• The “not a blockchain” frame is concrete: blockchains burn energy on consensus to order transactions globally; VEST orders operations per document and finalises them with named witnesses, the same model used for HTTPS certificate logs
• Competitive table in the source research compares VEST line-by-line against Trillian, Certificate Transparency, Key Transparency, and Binary Transparency, and only VEST has all four boxes ticked: real-time, threshold sigs, causal ordering, confidential payloads

quadrantChart
  title Verifiable log systems by use case and feature surface
  x-axis "Batch and offline" --> "Real time and live"
  y-axis "Single signer" --> "Threshold or dual signers"
  quadrant-1 "VEST sits here"
  quadrant-2 "Threshold but batch (research only)"
  quadrant-3 "Trillian, Certificate Transparency, Binary Transparency"
  quadrant-4 "Real-time but single-signer (collab tools)"
  VEST: [0.85, 0.85]
  Certificate Transparency: [0.25, 0.3]
  Trillian backend: [0.3, 0.25]
  Binary Transparency (Pixel): [0.25, 0.35]
  Key Transparency: [0.35, 0.4]
  Google Docs history: [0.8, 0.2]