Skip to content

build(ceremony)!: notary 0.7.0, on tlsn v0.1.0-beta.1 - #183

Merged
xgreenx merged 1 commit into
mainfrom
build/notary-0.7.0
Nov 20, 2026
Merged

xgreenx merged 1 commit into
mainfrom
build/notary-0.7.0

Conversation

@xgreenx

@xgreenx xgreenx commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

The ceremony's browser prover moves to notary v0.7.0, which builds tlsn from the release tag v0.1.0-beta.1 (40a0695) instead of main at 01fab038b. tlsn's version check refuses a peer on another version, so the bundle and the notary move together.

Changes

  • notary.assets.ts: the tlsn-wasm archive → notary/releases/download/v0.7.0/tlsn-wasm-0.7.0.tar.gz, sha256 4fd772f6…e473, cache path tlsn/v0.7.0.
  • e2e/compose.yaml and apps/dev/compose.yaml: notary → ghcr.io/libid-org/notary index digest sha256:66c04302…dd026 (0.7.0).
  • docs/distribution.md (the example) and docs/qualification.md (the notary row) name v0.7.0.

Verified

  • pnpm -C ts build, typecheck, lint, fmt:check, test:packages: pass.
  • build:ccdp-artifacts downloads the archive and checks it against the pin; test:distribution: 35 passed, 7 skipped (unset SWS variables).
  • Ceremony browser tests, --project=chromium, against the notary 0.7.0 image: 32 passed. That includes real x notary: 1 session(s), 2 session(s) and real github notary: 2 session(s) alongside proving.
  • Fail-to-pass: runtime.spec.ts "real x notary: 1 session(s)" against the 0.7.0 image fails with main's v0.6.0 bundle. The notary logs prover version does not match with verifier: 0.1.0-alpha.16-pre != 0.1.0-beta.1, and the browser gets "commitment protocol failed … unexpected end of file". With this bundle it passes.
  • Before the release, a bundle built from build(deps)!: tlsn from release tag v0.1.0-beta.1 notary#38 lock completed the same 32 tests against an image of that notary.

Not verified / known issues

  • Breaking for consumers: a ceremony on this bundle fails fast against a 0.6.0 notary, and the reverse. The @libid/ceremony minor and the CCDP image ship together with the notary deploy.
  • Firefox and WebKit: CI runs them.

The browser prover takes the tlsn-wasm bundle of notary v0.7.0, built from
tlsnotary/tlsn tag v0.1.0-beta.1 (40a0695), and both compose stacks run the
notary 0.7.0 image. tlsn's version check refuses a peer on another
version, so a ceremony on this bundle needs a 0.7.0 notary, and a 0.6.0
bundle fails at setup against it.

Signed-off-by: xgreenx <xgreenx9999@gmail.com>
@green-s-ai-agent
green-s-ai-agent Bot marked this pull request as ready for review November 20, 2026 15:18
@xgreenx
xgreenx merged commit c10aab0 into main Nov 20, 2026
15 checks passed
@xgreenx
xgreenx deleted the build/notary-0.7.0 branch November 20, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant