Bitcoin Developers, The 2nd instance of the recurring meeting is scheduled for Tuesday January 25th at 12:00 PT in channel ##ctv-bip-review in libera.chat IRC server. The meeting should take approximately 2 hours. The topics proposed to be discussed are agendized below. Please review the agenda in advance of the meeting to make the best use of everyone's time. If you have any feedback or proposed content changes to the agenda please let me know. See you Tuesday, Jeremy - Update on Bounty Program & Feedback (10 Min) - Feedback Recap (20 Min) - In this section we'll review any recent feedback or review of CTV. To expedite the meeting, a summary is provided below of the main feedback received since the last meeting and responses to them so that the time allotted may be devoted to follow up questions. - Luke Dashjr's feedback - thread: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019776.html - summary: Dashjr notes that while CTV is not done, it may be nearly done. Dashjr requests that some applications be made BIP-quality before proceeding, amongst other smaller feedbacks. Dashjr also expresses his concerns about activation logic. Respondents debated the activation logic, and there was a general sentiment to keep the discussion of CTV and activation logic somewhat separate, as Activation is a general concern pertaining to all upgrades and not CTV in particular. Rubin responded asking if BIP-quality is required or if examples like those in rubin.io/advent21 suffice. - James O'Beirne's feedback - Github Link: https://github.com/bitcoin/bitcoin/pull/21702#pullrequestreview-859718084 - summary: O'Beirne tests the reindexing performance with the CTV patches and finds a minor performance regression due to the cache precomputations. Rubin responds with patches for an improved caching strategy that precomputes the CTV hashes only when they are used, but it is a little more complex to review. Rubin also points out that the tested range is not representative of "current" blocks which have a higher proportion of segwit. - Peter Todd's Feedback - thread: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019738.html - response: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019739.html - summary: Todd reviewed the BIP and an (outdated) implementation and was disappointed to find that the testing was insufficient, the analysis of validation resources was insufficient, and the quality of proof of concept applications was insufficient. Rubin responded by pointing Todd to the most up to date implementation which has more tests, updated the link in the BIP to the PR, updated the BIP to describe resource usage, and asked what the bar is expected to be for applications. Rubin further responded with an analysis of current congested mempool behavior here: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019756.html . Todd is yet to respond. - What is Sapio / How to think about Programming with CTV (15 Min) - Resources to review - https://learn.sapio-lang.org/ch02-00-bip-119.html - https://rubin.io/bitcoin/2021/12/06/advent-9/ - https://rubin.io/bitcoin/2021/12/15/advent-18/ - Composability - What's all this "Non-Interactivity" Business? - Vaults (20 Min) - Resources: https://rubin.io/bitcoin/2021/12/07/advent-10/ https://rubin.io/bitcoin/2021/12/08/advent-11/ https://github.com/kanzure/python-vaults - Congestion Control (20 Mins) - Resources: https://rubin.io/bitcoin/2021/12/09/advent-12/ https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-January/019756.html https://utxos.org/analysis/batching_sim/ https://utxos.org/analysis/bip_simulation/ - Payment Pools (20 Mins) - Resources: https://rubin.io/bitcoin/2021/12/10/advent-13/ https://rubin.io/bitcoin/2021/12/15/advent-18/ https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-September/019419.html https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-June/017964.html - General Q&A (15 Mins) -- @JeremyRubin