> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/meeting-minutes/2026-tsc-meeting-minutes/meeting-minutes-march-18-2026.md). # Meeting Minutes March 18, 2026 ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | Term | | ----------------- | ---------- | --------------- | ----------------- | ------------ | | Kevin Hammond | Yes | Chair | Y | October 2026 | | TBC | No | Vice Chair | Y | October 2025 | | Bosko Majdanac | Yes | Secretary | N | N/A | | Tex McCutcheon | Yes | Alt - Secretary | N | N/A | | Nicolas Biri | Yes | Member/Seat | Y | April 2026 | | Duncan Coutts | No | Member/Seat | Y | April 2026 | | Sebastian Nagel | Yes | Member/Seat | Y | April 2026 | | Neil Davies | Yes | Member/Seat | Y | April 2026 | | Alexander Moser | Yes | Member/Seat | Y | April 2026 | | Ryan Wiley | Yes | Member/Seat | Y | October 2026 | | Udai Solanki | Yes | Member/Seat | Y | October 2026 | | Leandros Holleman | Yes | Member/Seat | Y | October 2026 | | Seungheon Oh | No | Member/Seat | Y | October 2026 | Community/Other Attendees * Ken-Erik Ølmheim \ Recording: [Technical Steering Committee - 2026/03/18 - Recording](https://drive.google.com/file/d/1CWnrDWEyPCBuaWRlok8CsszgAA2tZtqJ/view?usp=drive_link) Transcript: [Technical Steering Committee - 2026/03/18 - Transcript](https://docs.google.com/document/d/1Y5lUBKfqWCvnocQA6NEm1odGhpAKGqFLjBMwE1tolKc/edit?usp=sharing) Chat Transcript: [Technical Steering Committee - 2026/03/18 - Chat Transcript](https://drive.google.com/file/d/1Nd3Wg2j7xKO0JqbFQh6EKAr4FYGbM-lj/view?usp=drive_link) ## Agenda 18th March 2026 * Actions from the Last Meeting * TSC Budget Proposal * Completed Template * Discuss Items * Open discussion with ISC/Board on Monday 3.23 * Hard Fork Status * Node 10.7.0 Status * Readiness Tracking * From CIP to Hard Fork * CIP-179 is active and available on Mainnet * Net Change Limit Gov Actions * CIP-173 * 2030 Vision KPI's * Follow-on meeting with Product Committee today * US SEC Clarifies position of Federal Securities Laws * ADA is classified as a digital commodity, not a security * BuidlerFest 2026, Argentina Mar 24-25 * Node Diversity Workshop - Co-Located * Discussion of ccMinSize with Civics Committee * Thursday 3.19 1300 UTC (Civics Committee Meeting) * Committee Elections * Cycle starts 3.30 for April 2026 Elections, 5 vacancies * Committee X spaces/Virtual Hub * Committee Rewards * Available for claim from Intersect Member Area * AOB ## Decisions/Actions **Decisions** * **Budget Strategy:** Kevin will integrate Udai’s suggestion for commissioned technical reports and Nicolas’s "remote-first" workshop preference into the final budget template. * **Constitution Review:** The committee agreed to wait for Neil’s final summary before submitting the formal technical concern statement on v2.4 to the Civics Committee. **Actions** * **Kevin & Bosko:** Meet privately before Monday to finalize the mapping of TSC work packages into the Intersect budget template. * **Bosko:** Coordinate a Doodle poll to schedule the private "Linear Leios Risk Management" deep dive with Sebastian. * **Leandros:** Finalize the 2030 KPI document with the Product Committee during today's follow-up meeting. * **Kevin:** Attend the Civics Committee meeting tomorrow (March 19) to discuss the Parameter Committee’s recommendation on CC minimum size reduction. * **Terence & Bosko:** Finalize and share the available time slots for the TSC election X-Spaces and Virtual Hub events via Slack and Doodle poll * **All Members:** Review the latest budget draft in Slack and provide final comments before the Monday deadline. | Topic | Discussion | Notes | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | | Welcome & Quorum | Kevin opened the meeting, confirming six TSC members present. Quorum was met for decision-making purposes. | Neil and Duncan sent apologies; Ryan participated via chat due to travel. | | TSC Budget Template | The Budget Committee issued a new template for 2026. Kevin noted the shift to milestone-based deliverables with a tight 9-day completion window. | Discussion on the oddity of fitting a committee support function into a template designed for development projects. | | In-Person Meetings | Kevin proposed reducing the frequency of in-person TSC meetings from quarterly to twice a year to trim the $40,000 travel budget. | Udai suggested three meetings, noting that $1,000 per person is conservative given international travel costs. | | Technical Workshops | A proposal for 10–15 technical workshops (e.g., Node Diversity, Layer 2, Partner Chains) was discussed. | Nicolas recommended a "remote-first" approach to maximize attendance and reduce costs, while Udai favored a hybrid model. | | Commissioned Reports | Udai suggested the TSC should budget for commissioning high-level technical studies on best practices and future roadmaps. | Kevin agreed to include a provision for future-looking reports that align with the 2030 Vision. | | Plutus Cost Models | Parameter Committee accepted the revised Plutus cost models for the Van Rossom hard fork, correcting previous inaccuracies. | Enactment on SanchoNet is complete; Preview and Pre-prod testnets are the next targets. | | DRep Deposit (5 ADA) | Mike presented benchmarking data suggesting the ledger can safely support 5,000+ DReps if the deposit is lowered from 500 to 5 ADA. | Existing DReps would currently need to de-register and re-register to reclaim the 495 ADA difference. | | Hard Fork Timeline | Node v10.7.0 pre-release is expected by the end of the week. Full Node v11 is required for the Preview hard fork. | Current "realistic" forecast for Mainnet hard fork enactment is early June 2026. | | KPI Finalization | Leandros and Kevin met with the Product Committee. A "fixed point" is near for defining 2030 metrics (Revenue, TVL, Chain Quality). | The Product Committee noted that Cardano’s security is its primary Unique Selling Point (USP). | | Discord Gatekeeping | Sebastian (via previous notes) and Terence discussed the friction caused by requiring Intersect membership to access technical Discord channels. | Terence clarified the "Associate" tier is free; a simplified "How-to" guide will be distributed to reduce friction. | | SEC/Cardano Status | Kevin noted a positive clarification from the US SEC explicitly classifying ADA as a digital commodity rather than a security. | This is viewed as a major milestone for regulatory clarity for the community. | | Committee Elections | Intersect will host X Spaces and Virtual Hub events between March 30 and April 17 to highlight TSC roles. | Slots are currently open for TSC members to sign up as lead participants. | | Technical Comms | Discussion on the need to increase budget for technical communication staff to better disseminate working group outcomes. | This is a core pillar of the 2026 budget proposal to improve transparency. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/meeting-minutes/2026-tsc-meeting-minutes/meeting-minutes-march-18-2026.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.