tlsnotary/docs-mdbook
1
0
Fork 0
mirror of https://github.com/tlsnotary/docs-mdbook.git synced 2026-01-09 04:37:55 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update blogs/202408/zktls.md

Browse Source 
Co-authored-by: sinu.eth <65924192+sinui0@users.noreply.github.com>
This commit is contained in:
Hendrik Eeckhaut
2024-09-19 15:00:43 +02:00
committed by GitHub
parent f437317af6
commit a4ce80bcbf
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blogs/202408/zktls.md
View File

@@ -31,7 +31,7 @@ In the case of MPC-TLS, the Verifier knows the TLS session was authentic, so it
## Onchain Attestations
The Verifier cannot operate onchain, as it must be online simultaneously with both the Prover and the Server. However, the TLSNotary result can still be utilized onchain if the Verifier signs the output as an attestation. This attestation, however, is not a publicly verifiable proof. Since a Verifier could potentially sign anything, consumers of this information must trust the Verifier. While TLSNotary can be used to build oracles, it does not solve the **oracle problem**.
The Verifier cannot operate onchain, as it must be online simultaneously with both the Prover and the Server. However, an attestation can still be utilized onchain. Since a Notary could potentially sign anything, consumers of this information must trust the Notary. While TLSNotary can be used to build blockchain oracles, it does not solve the **oracle problem**.
## Conclusion