Pisco Studio / proof

FROM BUILD TO BROWSER

Follow the proof.

This second page is part of the same signed deployment. Next.js navigation payloads and exported HTML are included in its manifest.

A

A domain authorizes a publisher

The domain binding identifies an owner wallet. That wallet delegates publication to a separate deployment key.

B

The build becomes a signed record

The CLI hashes the final files, fingerprints the pages, references a canonical manifest, and publishes a signed attestation.

C

The extension checks the evidence

Chrome should show “Refetched content matches — advisory.” Its check establishes a match for a separate fetch, rather than proving the bytes originally delivered to the tab.

D

A changed response fails verification

A response that differs from the signed deployment produces a content mismatch. The extension reports its own result from the publication and the retrieved page.

← Back to the demo

Integrity and publication identity do not establish a site’s legitimacy.