Skip to content

Commit

Permalink
Deployed c2f8779 with MkDocs version: 1.6.1
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Mar 3, 2025
1 parent d7d748c commit ff487eb
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion concepts/hyle-vs-vintage-blockchains/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1191,7 +1191,7 @@ <h2 id="minimal-onchain-state">Minimal onchain state</h2>
<p>Transactions on Hylé verify and settle transitions without storing full intermediary states onchain.</p>
<p>This architecture reduces storage overhead and promotes scalability while maintaining trustlessness.</p>
<h2 id="no-wallets">No wallets</h2>
<p>Stop asking yourself, «Which wallet do I use? How do I bridge? ». With Hylé, there are no wallets and no bridges − any identity source that can be attested with a zero-knowledge proof is a valid identity.</p>
<p>Stop asking yourself, "Which wallet do I use? How do I bridge?". With Hylé, there are no wallets and no bridges − any identity source that can be attested with a zero-knowledge proof is a valid identity.</p>
<h2 id="every-app-is-a-rollup">Every app is a rollup</h2>
<p>On Hylé, there is one general-purpose blockchain, and every app is its own based ZK-rollup, removing the problems associated with fragmentation.</p>
<p>An app’s transactions are sequenced directly on the Hylé base layer. They are split into a blob transaction, which allows for <a href="https://docs.hyle.eu/developers/general-doc/pipelined-proving/">pipelined proving</a>, and a proof transaction to store the state commitment onchain.</p>
Expand Down
2 changes: 1 addition & 1 deletion concepts/proof-composability/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1243,7 +1243,7 @@ <h2 id="the-problem-clunky-interactions">The problem: clunky interactions</h2>
<h2 id="the-solution-proof-composition">The solution: proof composition</h2>
<h3 id="cross-contract-calls-with-proof-composition">Cross-contract calls with proof composition</h3>
<p><strong>Proof composability</strong> means that Hylé enables these interactions while keeping each proof independent; <strong>proof composition</strong> is the action enabled by composability.</p>
<p>Hylé gets rid of recursion by allowing Program A to specify: «This only applies if all blobs in this operation are valid ». At settlement, both proofs are included in the same proof transaction. Hylé verifies them together, and the entire operation fails if any proof fails.</p>
<p>Hylé gets rid of recursion by allowing Program A to specify: "This only applies if all blobs in this operation are valid". At settlement, both proofs are included in the same proof transaction. Hylé verifies them together, and the entire operation fails if any proof fails.</p>
<p>This solution improves developer experience, lowers gas costs, and shortens proving time.</p>
<h3 id="proofs-using-different-schemes">Proofs using different schemes</h3>
<p>Since proofs in Hylé remain independent, you can batch multiple proofs within a single transaction, each using its optimal proving scheme.</p>
Expand Down
2 changes: 1 addition & 1 deletion quickstart/example/proof-composition/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1564,7 +1564,7 @@ <h3 id="simple-identity-preparation">Simple-identity preparation</h3>
<p>Let's verify it quickly with:</p>
<div class="language-sh highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a>cargo<span class="w"> </span>run<span class="w"> </span>--<span class="w"> </span>--contract-name<span class="w"> </span>id<span class="w"> </span>verify<span class="w"> </span>bob.id<span class="w"> </span>pass<span class="w"> </span><span class="m">0</span>
</span></code></pre></div>
<p>0 is a nonce: every time we verify successfully bob's identity, it increments. Now if we want to verify it again, we should use 1 as nonce. (We also use « pass » as our default password.)</p>
<p>0 is a nonce: every time we verify successfully bob's identity, it increments. Now if we want to verify it again, we should use 1 as nonce. (We also use "pass" as our default password.)</p>
<p>We now do the same for alice:</p>
<div class="language-sh highlight"><pre><span></span><code><span id="__span-3-1"><a id="__codelineno-3-1" name="__codelineno-3-1" href="#__codelineno-3-1"></a>cargo<span class="w"> </span>run<span class="w"> </span>--<span class="w"> </span>--contract-name<span class="w"> </span>id<span class="w"> </span>verify<span class="w"> </span>alice.id<span class="w"> </span>pass<span class="w"> </span><span class="m">0</span>
</span></code></pre></div>
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json

Large diffs are not rendered by default.

0 comments on commit ff487eb

Please sign in to comment.