From a4ce80bcbf072f8abeb4135fd382a421c48b0cf0 Mon Sep 17 00:00:00 2001 From: Hendrik Eeckhaut Date: Thu, 19 Sep 2024 15:00:43 +0200 Subject: [PATCH] Update blogs/202408/zktls.md Co-authored-by: sinu.eth <65924192+sinui0@users.noreply.github.com> --- blogs/202408/zktls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blogs/202408/zktls.md b/blogs/202408/zktls.md index c115d88..b97ad2a 100644 --- a/blogs/202408/zktls.md +++ b/blogs/202408/zktls.md @@ -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