mirror of
https://github.com/tlsnotary/website.git
synced 2026-01-06 20:53:56 -05:00
fix
This commit is contained in:
@@ -71,7 +71,7 @@ Talks will take place in the main stage room from **10:00 to 17:00**.
|
||||
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- |
|
||||
| 09:30–10:00 | Doors open | |
|
||||
| 10:00–10:10 | Welcome | |
|
||||
| 10:10–10:50 | [zkTLS fundamentals](#zktls-fundamentals-sinu-tlsnotary) (Thomas, TLSNotary) | |
|
||||
| 10:10–10:50 | [zkTLS fundamentals](#zktls-fundamentals-thomas-tlsnotary) (Thomas, TLSNotary) | |
|
||||
| 10:50–11:00 | Workshops pitch | Workshop teams pitch |
|
||||
| 11:00–11:35 | [Building Online Trust, On-Chain](#building-online-trust-on-chain-maciek-kalka-vlayer) (Maciek Kalka, vlayer) | Workshops open |
|
||||
| 11:35–12:10 | [Cryptography of zkTLS](#cryptography-of-zktls-xiang-xie-primus-labs) (Xiang Xie, Primus Labs) | Workshops continue |
|
||||
@@ -84,7 +84,7 @@ Talks will take place in the main stage room from **10:00 to 17:00**.
|
||||
|
||||
## Talk details
|
||||
|
||||
### zkTLS fundamentals (Sinu, TLSNotary)
|
||||
### zkTLS fundamentals (Thomas, TLSNotary)
|
||||
Start your zkTLS journey with a foundational session led by Thomas, a key contributor to EF's TLSNotary project.
|
||||
This talk traces the evolution of zkTLS and breaks down its core concepts, from proofs vs. attestations to the trade-offs between TEE-, proxy-, and MPC-based approaches.
|
||||
You’ll learn how different trust models, privacy techniques, and verification methods shape the landscape of zkTLS, and gain a clear understanding of the performance and security considerations behind each design.
|
||||
|
||||
Reference in New Issue
Block a user