This commit is contained in:
Hendrik Eeckhaut
2023-11-07 16:44:44 +01:00
parent dcc92f1164
commit 3a0955b890
2 changed files with 22 additions and 4 deletions

View File

@@ -1,5 +1,14 @@
cargo run --release --example simple_notary
cargo run --release --example simple_prover
cargo run --release --example simple_verifier
<figure>
<img src="tlsn-banner.png" alt="tlsn-banner">
</figure>
https://tlsnotary.github.io/proof_viz/
# Progcrypto 2023: TLSNotary workshop
Open the [workshop instructions](./workshop.md) to follow along.
Links:
* https://tlsnotary.org
* https://docs.tlsnotary.org/
* https://discord.gg/9XwESXtcN7
* https://tlsnotary.github.io/tlsn/tlsn_prover/
* https://tlsnotary.github.io/proof_viz/

View File

@@ -176,10 +176,19 @@ The Notary server should log:
2023-11-03T15:53:51.147074Z INFO tokio-runtime-worker ThreadId(10) notary_server::service::tcp: Successful notarization using tcp! session_id="006b3293-8fba-44ac-8692-41daa47e4a9a"
```
If the transcript was too long, you may encounter the following error. This occurs because there is a default limit of notarization size to 16kB:
```log
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: IOError(Custom { kind: InvalidData, error: BackendError(DecryptionError("Other: KOSReceiverActor is not setup")) })', /Users/heeckhau/tlsnotary/tlsn/tlsn/tlsn-prover/src/lib.rs:173:50
```
The Discord example code redacts the `auth_token`, but feel free to change the redacted regions.
The proof is written to `discord_dm_proof.json`
#### Verify
Verify the proof by dropping the json file into <https://tlsnotary.github.io/proof_viz/> or by running: