|
32 | 32 | <a href="https://github.com/TABConf/6.tabconf.com/issues/45">https://github.com/TABConf/6.tabconf.com/issues/45</a></p></description></item><item><title>Shielded CSV Private & Efficient Client Side Validation</title><link>https://btctranscripts.com/tabconf/2024/shielded-csv-private-and-efficient-client-side-validation/</link><pubDate>Wed, 27 Nov 2024 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/tabconf/2024/shielded-csv-private-and-efficient-client-side-validation/</guid><description><p>The client-side validation approach removes transaction verification from the consensus rules. Instead, transaction data posted to the blockchain is only interpreted on each individual node (&ldquo;client-side&rdquo;). This approach allows building protocols with very low on-chain size and verification cost, while providing strong privacy.</p> |
33 | 33 | <p>This talk proposes the client-side validation protocol &ldquo;zkCSV&rdquo; (working title) that, in contrast to existing client-side validation protocols, only requires 64 bytes of on-chain space regardless of the size of the transaction and is fully private. The protocol&rsquo;s communication cost between transaction sender and receiver is independent of the transaction history. Furthermore, zkCSV can be instantiated with existing cryptographic zk-SNARK primitives.</p> |
34 | 34 | <p>With a trust-minimized mechanism like BitVM2 to bridge between the blockchain and the client-side validation protocol, zkCSV adds strong privacy to Bitcoin and scales Bitcoin to 100 transactions per second. It has been described as &ldquo;the most useful thing you can do with BitVM2&rdquo;.</p> |
35 | | -<p>Even without a bridge, zkCSV can be used to create a private cryptocurrency pegged to bitcoin (for example via the one-way peg) that offers substantial advantage over existing private cryptocurrencies. These currencies require users to validate all transactions, which contain relatively large and computationally expensive Zero-Knowledge proofs. zkCSV, however, only requires the recipient of a transaction to download the full transaction data, which results in significant reductions in computational and bandwidth costs. Furthermore, zkCSV derives its resistance to double-spending from Bitcoin, eliminating the need for its own consensus mechanism. Moreover, private cryptocurrencies are not able to hide the transaction graph better than zkCSV.</p> |
36 | | -<p>What would an attendee learn from this talk?</p> |
37 | | -<ul> |
38 | | -<li>What client-side validation is and what its advantages and limitations are.</li> |
39 | | -<li>How it is possible to achieve only 64 bytes on-chain cost using sign-to-contract and signature half-aggregation.</li> |
40 | | -<li>How zk-SNARKs and in particular proof-carrying data schemes are applied to provide strong privacy.</li> |
41 | | -<li>That private &amp; efficient client-side validation is a largely unexplored framework that has a vast design space and potential for innovation, in particular for designs that allow efficient layer 2&rsquo;s.</li> |
42 | | -</ul> |
43 | | -<p>Is there anything folks should read up on before they attend this talk?</p> |
44 | | -<p>no</p> |
45 | | -<p>About the Speaker</p> |
46 | | -<p>Social Links</p> |
47 | | -<ul> |
48 | | -<li>Github: https://github.com/jonasnick</li> |
49 | | -<li>Twitter: https://x.com/n1ckler</li> |
50 | | -<li>Website: <a href="https://nickler.ninja/">https://nickler.ninja</a></li> |
51 | | -</ul> |
52 | | -<p>TABCONF 6, GitHub link |
53 | | -<a href="https://github.com/TABConf/6.tabconf.com/issues/90">https://github.com/TABConf/6.tabconf.com/issues/90</a></p></description></item><item><title>FROST, The Production Impact and Why It Matters</title><link>https://btctranscripts.com/tabconf/2024/frost-the-production-impact-and-why-it-matters/</link><pubDate>Tue, 26 Nov 2024 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/tabconf/2024/frost-the-production-impact-and-why-it-matters/</guid><description><p>Requirements for Bitcoin key management are ever more demanding, and many off-chain tools require user dependence on hot keys instead of (safer) cold keys. Breakthroughs in cryptography like Flexible Round-Optimized Schnorr Threshold Signatures (FROST) and the Taproot upgrade are helping developers and users re-think their approaches to private key security. FROST is a protocol that minimizes the number of rounds of communication between participants in Schnorr signature schemes to reduce network bandwidth, time, and probability of errors. Cryptographers, protocol developers, and other Bitcoin builders will discuss the state of FROST, its use by Bitcoin companies, and its potential for reshaping Bitcoin security.</p> |
| 35 | +<p>Even without a bridge, zkCSV can be used to create a private cryptocurrency pegged to bitcoin (for example via the one-way peg) that offers substantial advantage over existing private cryptocurrencies. These currencies require users to validate all transactions, which contain relatively large and computationally expensive Zero-Knowledge proofs. zkCSV, however, only requires the recipient of a transaction to download the full transaction data, which results in significant reductions in computational and bandwidth costs. Furthermore, zkCSV derives its resistance to double-spending from Bitcoin, eliminating the need for its own consensus mechanism. Moreover, private cryptocurrencies are not able to hide the transaction graph better than zkCSV.</p></description></item><item><title>FROST, The Production Impact and Why It Matters</title><link>https://btctranscripts.com/tabconf/2024/frost-the-production-impact-and-why-it-matters/</link><pubDate>Tue, 26 Nov 2024 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/tabconf/2024/frost-the-production-impact-and-why-it-matters/</guid><description><p>Requirements for Bitcoin key management are ever more demanding, and many off-chain tools require user dependence on hot keys instead of (safer) cold keys. Breakthroughs in cryptography like Flexible Round-Optimized Schnorr Threshold Signatures (FROST) and the Taproot upgrade are helping developers and users re-think their approaches to private key security. FROST is a protocol that minimizes the number of rounds of communication between participants in Schnorr signature schemes to reduce network bandwidth, time, and probability of errors. Cryptographers, protocol developers, and other Bitcoin builders will discuss the state of FROST, its use by Bitcoin companies, and its potential for reshaping Bitcoin security.</p> |
54 | 36 | <p>What would an attendee learn from this talk?</p> |
55 | 37 | <p>The Basics: “What is F.R.O.S.T.?”</p> |
56 | 38 | <p>Comparing offchain and onchain multisig tools</p> |
|
0 commit comments