|
1 | 1 | <?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Education on ₿itcoin Transcripts</title><link>https://btctranscripts.com/categories/education/</link><description>Recent content in Education on ₿itcoin Transcripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 20 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://btctranscripts.com/categories/education/index.xml" rel="self" type="application/rss+xml"/><item><title>Cluster Mempool by Murch</title><link>https://btctranscripts.com/tabconf/2024/cluster-mempool-by-murch/</link><pubDate>Fri, 20 Dec 2024 00:00:00 +0000</pubDate><guid>https://btctranscripts.com/tabconf/2024/cluster-mempool-by-murch/</guid><description><p>Cluster Mempool is an effort to rearchitect how Bitcoin Core stores unconfirmed transactions, builds blocks, and evaluates replacement candidates. It is expected to drastically simplify package relay with bigger packages than two transactions, speed up block building, and generalize CPFP to descendants-pay-for-ancestors.</p> |
2 | | -<p>What would an attendee learn from this talk?</p> |
3 | 2 | <ul> |
4 | | -<li>What issues exist in the current mempool design?</li> |
5 | | -<li>How does the Cluster Mempool approach address those issues?</li> |
6 | | -<li>How does Cluster Mempool work?</li> |
7 | | -<li>How does this change affect users and other network participants?</li> |
8 | | -</ul> |
| 3 | +<li> |
| 4 | +<p>What would an attendee learn from this talk?</p> |
| 5 | +</li> |
| 6 | +<li> |
| 7 | +<p>What issues exist in the current mempool design?</p> |
| 8 | +</li> |
| 9 | +<li> |
| 10 | +<p>How does the Cluster Mempool approach address those issues?</p> |
| 11 | +</li> |
| 12 | +<li> |
| 13 | +<p>How does the Cluster Mempool work?</p> |
| 14 | +</li> |
| 15 | +<li> |
| 16 | +<p>How does this change affect users and other network participants?</p> |
| 17 | +</li> |
| 18 | +<li> |
9 | 19 | <p>Is there anything folks should read up on before they attend this talk?</p> |
10 | | -<ul> |
11 | | -<li>Basic knowledge about unconfirmed transactions and mempool is useful</li> |
12 | | -</ul> |
13 | | -<p>Relevant Links</p> |
14 | | -<ul> |
15 | | -<li><a href="https://github.com/bitcoin/bitcoin/issues/27677">Proposal for a new mempool design bitcoin/bitcoin#27677</a></li> |
16 | | -<li><a href="https://delvingbitcoin.org/t/cluster-mempool-definitions-theory/202">https://delvingbitcoin.org/t/cluster-mempool-definitions-theory/202</a></li> |
17 | | -<li><a href="https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156">https://delvingbitcoin.org/t/cluster-mempool-rbf-thoughts/156</a></li> |
18 | | -<li><a href="https://delvingbitcoin.org/t/how-to-linearize-your-cluster/303">https://delvingbitcoin.org/t/how-to-linearize-your-cluster/303</a></li> |
| 20 | +</li> |
| 21 | +<li> |
| 22 | +<p>Basic knowledge about unconfirmed transactions and mempool is useful</p> |
| 23 | +</li> |
19 | 24 | </ul> |
20 | 25 | <p>About the Speaker</p> |
21 | 26 | <p>Murch is an engineer at Chaincode Labs. He contributes to Bitcoin Core, Bitcoin Optech, and Bitcoin Stack Exchange. He is a co-host of NYC BitDevs and the Bitcoin Optech Recap.</p> |
22 | 27 | <p>Social Links</p> |
23 | | -<p>!https://github.githubassets.com/images/icons/emoji/octocat.png</p> |
| 28 | +<p><a href="https://github.githubassets.com/images/icons/emoji/octocat.png">https://github.githubassets.com/images/icons/emoji/octocat.png</a></p> |
24 | 29 | <p><a href="https://github.com/murchandamus/">https://github.com/murchandamus/</a></p> |
25 | 30 | <p>🐦 <a href="https://twitter.com/murchandamus">https://twitter.com/murchandamus</a></p> |
26 | | -<p>TABConf 6 GitHub link |
| 31 | +<p>TABConf-6-GitHub |
27 | 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> |
28 | 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> |
29 | 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> |
|
0 commit comments