Repository navigation
build(ceremony)!: notary 0.7.0, on tlsn v0.1.0-beta.1 - #183
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ceremony's browser prover moves to notary v0.7.0, which builds
tlsnfrom the release tagv0.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, sha2564fd772f6…e473, cache pathtlsn/v0.7.0.e2e/compose.yamlandapps/dev/compose.yaml: notary →ghcr.io/libid-org/notaryindex digestsha256:66c04302…dd026(0.7.0).docs/distribution.md(the example) anddocs/qualification.md(the notary row) name v0.7.0.Verified
pnpm -C ts build,typecheck,lint,fmt:check,test:packages: pass.build:ccdp-artifactsdownloads the archive and checks it against the pin;test:distribution: 35 passed, 7 skipped (unset SWS variables).--project=chromium, against the notary 0.7.0 image: 32 passed. That includesreal x notary: 1 session(s),2 session(s)andreal github notary: 2 session(s) alongside proving.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 logsprover 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.Not verified / known issues
@libid/ceremonyminor and the CCDP image ship together with the notary deploy.