FTA public verification lets auditors, customers, reviewers, and marketplace partners check evidence integrity without depending only on the application database or backend server.
The walkthrough summarizes the trust layers already implemented in the public verifier and CLI verification stack.
Verify that a public evidence record resolves to the expected Merkle root and signed root head. This runs in two places: in your browser on each record's verification page, and with FTA's independent command-line verifier.
For auditors and technical reviewers: FTA's independent command-line verifier checks an exported proof bundle's signed root-head metadata, transparency log binding, public key trust, and canonical payload integrity. This check runs outside the browser, not on the verification pages.
The verifier page recomputes the Merkle proof and checks the signed root-head signature in your browser, against a public key built into the verifier rather than one supplied by the API response.
Checks that a newer root extends an older one without rewriting history. Runs in your browser on the consistency verification page. Production has published one root so far, so for now you can see it run on a clearly labelled SAMPLE proof built from demonstration records.
When you open a proof such as the hosted-pilot record, your browser runs these checks itself. The page also lists checks reported by FTA's server, such as whether the checkpoint is finalized.
Evidence records can be verified directly when you know the public evidence record ID. The verifier route reconstructs the public proof view for that record.
/verify/[evidenceRecordId]This seeded hosted-pilot record demonstrates record-integrity verification. It is illustrative data, not a live claim about an operating restaurant or its current safety.
Open hosted-pilot proofFTA produces independently verifiable evidence artifacts, allowing external parties to validate critical claims through signed root heads, transparency logs, and Merkle proofs.