Intersect Committees
Intersect Knowledge BaseIntersect Website
Intersect - Technical Steering Committee
Intersect - Technical Steering Committee
  • ABOUT
    • Technical Steering Committee (TSC)
    • Committee members
    • Technical Working Groups
    • Security Council
    • How to Join or Contact Us?
    • 2025 TSC Meeting Minutes
      • 2025 TSC Decision Log
      • 6th June 25
      • 28th May 25
      • 21st May 25
      • 14th May 25
      • 7th May 25
      • 30th April 25
      • 23rd April 25
      • 17th April 25
      • 2nd April 25
      • 25th Mar 25
      • 19th Mar 25
      • 12th March 25
      • 26th Feb 25
      • 19th Feb 25
      • 12th Feb 25
      • 5th Feb 25
      • 22nd Jan 25
      • 15th Jan 25
      • 8th Jan 25
    • 2024 TSC Meeting Minutes
      • TSC - Decisions Log
      • 4th Dec 24
      • 27th Nov 24
      • 20th Nov 24
      • 13th Nov 24
      • 6th Nov 24
      • 30th Oct 24
      • 23rd October
      • 2nd Oct 24
      • 25th Sept 24
      • 28th August 24
      • 31st July 24
      • 17th July
      • 19th June
      • 5th June
      • 22 May 24
      • 8 May 2024
      • 24 April 24
      • 10 April 24
      • 27 Mar 24
    • Page
  • Technical Roadmap
    • How to Participate in Shaping the Technical Roadmap
    • Project Cards Explained
      • Software Readiness Level
    • Potential Roadmap Projects
    • Maintenance Items
Powered by GitBook
On this page
  1. ABOUT
  2. 2025 TSC Meeting Minutes

28th May 25

Previous6th June 25Next21st May 25

Last updated 3 days ago

Meeting Recording:

Attendance:

First name
Last name
Position
Voting Member

Nicolas

Biri

TSC Member (IOG)

Y

Duncan

Coutts

TSC Member (WellTyped)

Y

Neil

Davies

TSC Member (PN Solutions)

Y

Alexander

Moser

TSC Member Cardano Foundation

Y

Markus

Gufler

TSC Member (Cardano Foundation)

Y

Benjamin

Hart

TSC Member (MLabs)

Y

Jonathan

Kelly

TSC Member

Y

Sebastian

Nagel

TSC Member - IOG

Y

Duncan

Soutar

TSC Secretary

N

Christian

Taylor

Intersect - Opensource Head

N

Samuel

Leathers

IOG - Engineering

N

Minutes:

Agenda Item
Discussion
Actions / Decisions

1. Apologies

Apologies from Ricky Rand, Matt Davies, Kevin, Marcus Gufler - Neil Davies voted interim Chair

2. Actions from last week

Ran through actions from last week including KES Agent Repo adoption & reqquest for Amaru alternative node proposal review from CC.

Action: Duncan to share with ISC & the Intersect Board, the TSC’s view on its role in sign off of deliverables. Action: Duncan C to share Slack details with secretary Action Duncan C & Adam Dean to share paragraphs on taking on KES Agent Repository

3. Proposal to Open Up Release Meetings

SL: Currently release meeting is attended by team leads within IOG so looking to start a working group under TSC. Adam Dean having gone through Maintainer Retainer was recommended. 15:00 UTC on Tuesday ND: This meeting is the short term roadmap of the node (Tail end of delivery process). This meeting going public would reveal short term plans. SL: Output from this meeting is node releases and notes with them. Proposal would move this under Intersect ownership. JK: Encourages this step and happy with the move. SN: Would like for this group to share with (Insert other group) DC: Endorse proposal ND: Believes meeting shouldn’t be recorded due to potential sensitivity

Decision - Release meetings to be opened to TSC and Intersect, minutes to be public, but not the invite Action - Intersect to take over meeting invite, Sam to send through

4. Alex’s question about “L” parameter - How to include this in the workplan?

AM: Rivetpool Request how they could push an L parameter L Parameter is the linear or exponential change in saturation depending on pledge. So is a factor within the rewards formula giving different outcomes. Usually request the this goes through PCP process however this is a new parameter and Scope of Parameter is outwith the scope of the Parameter committee. ND: This parameter assumes that we will change the saturation mechanism. This will need a HardFork. AM: Question is how can this idea be progressed into an alliance that results in a fork which includes this proposal? Multiple node teams need to agree. Clarification on what the process is for this? DC: Need to clarify process behind ledger-state changes. AM: Organising specs and requests such as this would be good to sit within the TSC remit. ND: Problem Statement process would be a good start for this to explain advantages and disadvantages, enabling community opinions to be gathered. JK: CIP50 already exists for this from back in 2022. ND: How is this shared with the community to gain feedback? JK: Are there proposals that were approved in the budget that covers this? NB: References CIP & CPS on Peras, and highlights that this is a good approach. DC: Feels that it is within scope of TSC to ensure proper steps are taken in process and that proper analysis is done. BH: Community validation is one of Intersect’s biggest problems. Queries if validation is within remit of TSC beyond that of the DREPs. Does not think it is TSC responsibility to be reaching out to each of the community groups for every proposal. Highlights importance of engaging SPOs due to need for Hard Fork and that this alters rewards mechanism SNG: Highlights CIP84 which is similar. Points out that this should contain analysis for parameter change. Endorses that TSC needs to define good practice. DC: Reminds TSC that Rewards scheme is for benefit of ADA holders not exclusively SPOs so a wider view is needed. ND: Highlights that getting rewards wrong could have significant impacts on Cardano ecosystem. JK: CIP50 has introduction of L parameter. Revised stakepool incentive scheme is part of IOE proposal. ND: TSC has two roles: 1. to see the analysis that is to be performed ahead of time to comment on this. 2 to see the output of this analysis. AM: When is the trigger point for this work? ND: This work was approved as part of the budget. AM: how to go from CIP to Ledger Change? JK: This would currently fall under the approved work by IOE DS: This needs to be considered in whether this is in scope in TSC AM: Believes this this would be valuable to be within TSC’s scope. JK: Believes that changes like this should form part of a roadmap

Action: DS to add this example to query on TSC scope] Action: Duncan S to approach IOE to comment on Agenda Item, confirm if this is within the scope of their work, what is the process for managing?

5. Follow-up on increasing Plutus mem limit settings

Security Council sees no issues - to be confirmed this PM AM: Kevin has prepared meta data for change to increase Plutus Memory Limits. Security council sees no issues. CT: Security Council have queries over block production and Forging times but are happy that this proposal is suitably conservative. SN: Query over how Parameter committee and Security council is evaluating this ND: [Check Recording] Microbenchmarking. Security Council were consulted and approved. ND: Explained the Microbenchmarking and regression testing completed as part of this analysis.

Action: TSC to review proposal once released. The to vote to approve and action submission of governance action.

6. Decreasing committeeMinSize

JK: Highlights the risk of deadlock that this proposal is looking to avoid. ND: Queries the motivation for this proposal JK: Believes that so far this has progressed well JK: Highlighting the guardrails that exist for this parameter including 3 month discussion period. Thomas invited to Parameter Committee to discuss proposa

Action: DS to share feedback collated so far from TSC also query is this proposal is still relevant

7. TSC Remit

DS: Looking for next week's session to be focussed on the the remit of the TSC

https://www.youtube.com/watch?v=uNzEimQXF18