21st May 25
Last updated
Last updated
Meeting Recording:
Attendance:
Nicolas
Biri
TSC Member (IOG)
Y
Duncan
Coutts
TSC Member (WellTyped)
Y
Neil
Davies
TSC Member (PN Solutions)
Y
Matt
Davis
Intersect - Tech Ops Lead
N
Adam
Dean
TSC Vice Chair
Y
Markus
Gufler
TSC Member (Cardano Foundation)
Y
Kevin
Hammond
TSC Chair
Y
Benjamin
Hart
TSC Member (MLabs)
Y
Jonathan
Kelly
TSC Member
Y
Pedro
Lucas
Observer
N
Ricky
Rand IOHK
IOE General Manager - Observer
N
Duncan
Soutar
TSC Secretary
N
Christian
Taylor
Intersect - Opensource Head
N
Abbie
Yeates
Intersect - Delivery Assurance Lead
N
Minutes:
1. Apologies
Apologies from Alex Moser & Sebastian Nagel
2. Actions from previous week
- Adam & Duncan C to complete write up of Intersect Taking on Repository for KES agent - Kevin Hammond to present Parameter Committee proposal to increase memory limits - TSC Members to share their thoughts on TSC Remit
- Adam & Duncan C to complete write up of Intersect Taking on Repository for KES agent - Kevin Hammond to present Parameter Committee proposal to increase memory limits - TSC Members to share their thoughts on TSC Remit
3. Update from ISC a) Intersect budget action is on chain - May be split if initially unsuccessful b) Unclear how treasury actions will be submitted - May need to be split into 2025/2026 c) TSC will play a delivery assurance role - May need additional technical reviewer resources to do this
KH: Exec making contingency plan to splat budget into smaller items should initial budget info-action be unsuccessful. Unclear on how treasury withdrawals will work at this stage. Most likely they will be grouped to avoid 39 separate treasury actions. KH: Delivery Assurance - stressed need for additional technical reviewers for Milestone sign off beyond the 10 members of TSC is demand for Milestone Reviews is great. ND: Who will right Milestone items? MD: This is partially answered by the comms from Jack to ISC. Acknowledges there are proposals where no milestones have been given. If project has been submitted with Milestones and approved by DReps then these will be put into contract. ND: Conflicts between projects not yet understood how to be handled. KH: Concern over quality of milestones submitted as part of budget. DS: Explained that ISC is now open to all TSC members to sit as observers
4. Presentation on Smart Contracts for Delivery Sign Off
MD: Presentation on Smart contracts. Work ongoing on by Pi Langham, TxPipe, being checked by MLabs. Walked through high level process for Smart Contract creation: Identified need for funds from budget to be held in Smart Contracts to make it transparent and visible publicly. There is a request in the constitution for funds to be held in Smart contracts where possible, to hold Treasury Money that is locked. Within Treasury action, several addresses can be stipulated as to where the money is sent. Parallel process going on to create a legal contract as a counterpart to Smart Contract. A review process will occur at each Milestone similar to last year, with an Oversight Committee responsibility for managing Milestones and Payments for each contract. Two types of contract: Treasury Withdrawal contract and Vendor Contract. Highlighted 4 routes for Treasury withdrawal contract. Highlights the different themes for splitting out contracts and rules around keys for managing Smart Contract. Q&A AD: Queried ability to return funds to treasury MD: This is one of the key routes for moving funds when needed for each contract MD: Modifying contracts is possible where sufficient people with permission to edit agree - highlights for most of these the Vendor would need to agree to the change MD: Highlights that there are timeouts that can be built in to return these to treasury. MD: Smart contract is effectively a payment mechanism with a legal contract created to back it up. MD: Discussion on who has keys, how many are there, how are they managed that are still being worked out. MD: The first version of Smart Contracts can only be milestone payments. T&M will need to be broken up into a milestone format. KH: Concern over timing of Net change limit being defined at time withdrawal takes place. So need to make sure Treasury withdrawals are properly timed. MD: Demonstrated dashboards that are being created to visibly display the management of this process. Inc Sundae Labs & Zerberous. MD: Clarified that it is expected that Contracts will be under UK Law MD: Highlighted that discussion on management of USD or use of stablecoins is still underway. May not be something that is offered initially but plan is to find a solution to enable this. ND: Interest in whether ALL companies that Intersect does business with, even non-technical companies such as cater companies will have to go through the same process as major vendors. JK: Could partial payments be made though dispersing or modifying and splitting milestones into 2 payments, one for work completed and one for work outstanding. RR: This is possible though modifying the payment MD: Notes that Pi & Jack are likely to be doing a zoom call on Friday [Action] Matt to share process presentation with the TSC & share link to Pi & Jack call on Friday JK: Could an elected member be a key holder on one of these contracts? BH: Motion: Recommend to ISC, Exec Board & other Intersect committees that: The majority of voters (signatures) should be to the relevant elected committee members or nominated persons (by the committee) ensure proper community oversight. Yes - Neil, Duncan, Adam, Johnny, Ben, Nicolas, Markus, - Kevin Abstains RR: Fears over terms of committee members being shorter than the duration of a number of contracts as contract would have to be re-created. NB: Suggestion to reuse CC Key Management System RR: Endorse this but would not be ready for initial contracts
Action: Matt to share process presentation with the TSC
Action: Matt to share link to Pi & Jack call on Friday
Decision: Recommend to ISC, Exec Board & other Intersect committees that: The majority of voters (signatures) should be to the relevant elected committee members or nominated persons (by the committee) ensure proper community oversight. Yes - Neil, Duncan, Adam, Johnny, Ben, Nicolas, Markus, - Kevin Abstains
5. Request from ICC: Feasibility of Amarau Proposal
"DS: Request for TSC perspective on technical feasibility of project, plus project costs and timeframes Looking for owner to draft response
Many: Concern over who else will consume this information. Where will it be shared to. AD: Has read proposal. Believes that it is constitutional.
Advice to ICC is that the proposal is constitutional. The TSC is happy to provide technical advice if the context for the query is understood. "
Action: Duncan to request from ICC the motivation behind the request