deploy: b9db85c

faq.html

@@ -191,6 +191,7 @@ <h1 id="faq"><a class="header" href="#faq">FAQ</a></h1>
 <li><a href="#faq9">Why does my session time out?</a></li>
 <li><a href="#faq10">How to run TLSNotary with extra logging?</a></li>
 <li><a href="#faq11">How do I troubleshoot connection issues?</a></li>
+<li><a href="#faq12">Does TLSNotary Solve the Oracle Problem?</a></li>
 </ul>
 <h3 id="faq1"><a class="header" href="#faq1">Doesn't TLS allow a third party to verify data authenticity?</a></h3>
 <p>No, it does not. TLS is designed to guarantee the authenticity of data <strong>only to the participants</strong> of the TLS connection. TLS does not have a mechanism to enable the server to "sign" the data.</p>
@@ -235,6 +236,9 @@ <h3 id="faq11"><a class="header" href="#faq11">How do I troubleshoot connection
 </ul>
 <p>If the issue persists, <a href="#faq10">enable extra logging</a> with <code>RUST_LOG=debug</code> or <code>RUST_LOG=trace</code> for deeper insights into what TLSNotary is doing.</p>
 <p>If you are connecting through a WebSocket proxy (e.g., in the browser extension), double-check that the WebSocket proxy connects to the intended domain. Note that PSE's public WebSocket proxy only supports a limited <a href="https://docs.tlsnotary.org/developers/notary_server.html#websocket-proxy-server">whitelist</a>. If you use a local proxy, make sure the domain is correct.</p>
+<h3 id="faq12"><a class="header" href="#faq12">Does TLSNotary Solve the Oracle Problem?</a></h3>
+<p>No, the TLSNotary protocol does not solve the "Oracle Problem." The Oracle Problem refers to the challenge of ensuring that off-chain data used in blockchain smart contracts is trustworthy and tamper-proof. While TLSNotary allows a Prover to cryptographically authenticate TLS data to a designated Verifier, trust is still required in the designated Verifier when it attests to the verified data on-chain. Therefore, this is not a trustless, decentralized solution to the Oracle Problem.</p>
+<p>TLSNotary can be used to bring data on-chain, but when the stakes are high, it is recommended to combine TLSNotary with a dedicated oracle protocol to mitigate these risks. Multiple projects are currently exploring the best solutions.</p>
 
                     </main>
 

print.html

@@ -261,6 +261,7 @@ <h1 id="faq"><a class="header" href="#faq">FAQ</a></h1>
 <li><a href="faq.html#faq9">Why does my session time out?</a></li>
 <li><a href="faq.html#faq10">How to run TLSNotary with extra logging?</a></li>
 <li><a href="faq.html#faq11">How do I troubleshoot connection issues?</a></li>
+<li><a href="faq.html#faq12">Does TLSNotary Solve the Oracle Problem?</a></li>
 </ul>
 <h3 id="faq1"><a class="header" href="#faq1">Doesn't TLS allow a third party to verify data authenticity?</a></h3>
 <p>No, it does not. TLS is designed to guarantee the authenticity of data <strong>only to the participants</strong> of the TLS connection. TLS does not have a mechanism to enable the server to "sign" the data.</p>
@@ -305,6 +306,9 @@ <h3 id="faq11"><a class="header" href="#faq11">How do I troubleshoot connection
 </ul>
 <p>If the issue persists, <a href="faq.html#faq10">enable extra logging</a> with <code>RUST_LOG=debug</code> or <code>RUST_LOG=trace</code> for deeper insights into what TLSNotary is doing.</p>
 <p>If you are connecting through a WebSocket proxy (e.g., in the browser extension), double-check that the WebSocket proxy connects to the intended domain. Note that PSE's public WebSocket proxy only supports a limited <a href="https://docs.tlsnotary.org/developers/notary_server.html#websocket-proxy-server">whitelist</a>. If you use a local proxy, make sure the domain is correct.</p>
+<h3 id="faq12"><a class="header" href="#faq12">Does TLSNotary Solve the Oracle Problem?</a></h3>
+<p>No, the TLSNotary protocol does not solve the "Oracle Problem." The Oracle Problem refers to the challenge of ensuring that off-chain data used in blockchain smart contracts is trustworthy and tamper-proof. While TLSNotary allows a Prover to cryptographically authenticate TLS data to a designated Verifier, trust is still required in the designated Verifier when it attests to the verified data on-chain. Therefore, this is not a trustless, decentralized solution to the Oracle Problem.</p>
+<p>TLSNotary can be used to bring data on-chain, but when the stakes are high, it is recommended to combine TLSNotary with a dedicated oracle protocol to mitigate these risks. Multiple projects are currently exploring the best solutions.</p>
 <div style="break-before: page; page-break-before: always;"></div><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/dist/katex.min.css">
 <h1 id="quick-start"><a class="header" href="#quick-start">Quick Start</a></h1>
 <p>This quick start will help you get started with TLSNotary, both in native <a href="quick_start/rust.html">Rust</a> and in the <a href="quick_start/browser_extension.html">browser</a>.</p>