Author: Jeremy Rubin 2022-02-02 20:04:59
Published on: 2022-02-02T20:04:59+00:00
On January 25th, 2022, a meeting was held and the logs are available for review. The agenda was discussed in conjunction with the notes which were made available. The next meeting is scheduled for next Tuesday at 12:00 PT, and a pre-meeting agenda draft will be circulated shortly. The Bug Bounty program update has set basic rules and is working to formalize the program. A multi-stakeholder organization requires more formality, and the 501c3 status/tax deductibility is available. The rules are subject to change, but issues found under the current descriptions will be awarded in good faith by Jeremy/Ariel for now. Feedback review from Luke, James, Peter, Sapio, Vaults, Congestion Control, and Payment Pools were discussed. There were various sentiments expressed about activation/CTV and having clear-cut use cases. The main feedback from Peter was wanting more use cases to be more clear. Vaults had a very strong positive sentiment, and CTV eliminates toxic waste from the setup of vaults with pre-signed txns/requirement for an RNG. CTV/Sapio composability makes vaults somewhat "BIP Resistant" because vaults could be customized heavily per user, depending on needs. CTV Pools particularly seem suited for participant privacy compared to other proposals that require all parties knowing all balances for all other parties to be secure. Congestion Control had shared sentiments that no one really cares about this issue, and it's bad marketing. Anecdotally, exchanges seem less interested in congestion control, mining pools, and Lightning Channel openers seem more into it. There were some questions asked about wallet complexity, space usage, and block space being cheap right now. Still, planning for the future outcome is essential. Users can request payouts into their own CTV-trees without exchanges knowing. Exchanges do stand to benefit from this, so they might. Payment Pools were discussed, and it was stated that they are basically a Congestion Control + Cooperative Close, compose with Channels as leaf nodes. CoinJoins can be done into payment pools. There are some high-level design questions to ask of any payment pool design, and CTV seems to have OK tradeoffs. General discussion included the cost of template covenants via APO and how they can be made similar cost to CTV with the addition of OP_GENERATOR (pushes G to the stack) and OP_CAT via ` OP_G OP_CAT 0x01 OP_G OP_CAT CHECKSIG`, or without CAT by allowing checksig to read R and S separately and getting rid of APO 0x01 prefix tags.
Updated on: 2023-05-22T17:15:36.903044+00:00