> 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-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/07-09-2026-meeting-minutes.md). # (07/09/2026) Meeting Minutes ## Attendees:
NameAttendanceRoleVoting Seat (Y/N)Term
Sebastian PabonYesChairYOctober 2025
Kambale Mechack ElieYesVice ChairYApril 2026 (2y)
Terence ‘Tex’ McCutcheonYesSecretaryNN/A
Bernard SibandaYesMemberYOctober 2025
Jordan HillYesMemberYOctober 2025
Udai SolankiYesMemberYOctober 2025
Reshma MohanYesMemberYOctober 2025
Pawel JakubasYesMemberYApril 2026 (2y)
Olivier MwatsimulamoYesMemberYApril 2026 (2y)
Bora ObenYesMemberYApril 2026 (2y)
Dominik HinklemanYesMemberYApril 2026 (2y)
Community/Other Attendees * Benjamin Hart * Cullah * Emmanuel Titi * Harun Mwangi * Luke Mahoney * Mathieu Montin * Mike Hornan **Recording:** [Open Source Committee (Intersect) - 2026/07/09 - Recording](https://drive.google.com/file/d/1mfjFEYBk33eJ9x7zb9RGSs_JDUwt6Gjr/view?usp=sharing) **Transcript:** [Open Source Committee (Intersect) - 2026/07/09 - Transcript](https://docs.google.com/document/d/1nQ2ZQYlNap1B_xSezy2Id0n-kw4zCK1fhkTZgIb_8dc/edit?usp=sharing) **Chat Transcript:** [Open Source Committee Meeting – 2026/07/09 – Chat Transcript](https://drive.google.com/file/d/1ijhhNNjtbRzQ4VC8HvMT7c1kdDKO-aXM/view?usp=drive_link) **Polls:** [Open Source Committee (Intersect) - 2026/07/09 - Polls](https://docs.google.com/spreadsheets/d/14C6Q8C2V8duI9Tua_Pgvn7xMc_mCCMMHdkNPCOkW94w/edit?usp=sharing) ## Intros **Bora:** TBD\ **Bernard:** OSC - voting member\ **Dominik:** Open Source Committee Member, part of Inferara.\ **Jordan:** TBD\ **Kambale:** OSC Vice chair\ **Olivier:** Goma Hub Member, Milestone Reviewer-Project Catalyst, MCC and OSC\ **Pawel:** Member OSC, CF\ **Reshma:** OSC voting member\ **Sebastian:** OSC chair. Andamio co-founder.\ **Tex:** Open Source Program Manager, Intersect, OSC Secretary, Committee Member Advocate\ **Udai:** Member OSC, AIQUANT Technologies ## Agenda 7.09.26 * Developer Advocate Check In(Optional) * Reminder: Check DA Milestones * CryptoEQ Brief (will attend next meeting) * Tooling Proposal Verdicts * Tooling Proposal: Cella (Guest: Cullah) * BBP Repo Exclusion: PSE * Tooling Proposal: CNE * LambdaBuffers SoW Approval * Q3 Planning Expansion - Topic Assignment? (Not covered, moved to async discussion. * Open Forum ## Decisions/Actions **Decisions** * Approved the removal of */plutus-script-evaluation* from the public bug bounty program (7 Yes, 2 Abstain). * Approved a request for a *Statement of Work (SOW)* from the Cella project team (6 Yes, 1 Abstain). * Approved a request for a *Statement of Work (SOW)* from the Cardano Node Emulator project team (8 Yes, 1 No, 1 Abstain). * Approved the submitted *Statement of Work (SOW)* and funding release for Lambda Buffers (5 Yes, 1 Abstain). * **Mesh AI:** Approved (7 Yes, 1 Abstain). Moving to Statement of Work (SOW). * **Midnight Setup:** Denied (5 No, 2 Abstain). * ```
``` Actions * **Committee Members:** Review the final Q2 developer advocate milestones on GitHub (Open Source Office, Project 71) and leave feedback/comments. * **Committee Members:** Post any pre-questions for Spencer (CryptoEQ) in the Discord channel prior to the next meeting. * **Terence:** Send the official decision details to Mesh AI so they can begin drafting their Statement of Work. * **Terence:** Notify the Midnight Setup team regarding the poll decision to deny funding. * **Cullah (Cella):** Book time with Terence using his calendar link to record a deeper demo and submit an official Statement of Work. * **Mathieu (Cardano Node Emulator):** Work on and submit a formal Statement of Work to the Committee. * **Benjamin & Luke (MLabs):** Provide GitHub insights and user adoption metrics for Lambda Buffers and CTL via text/Discord to the Committee. * **Terence:** Coordinate the formalized CTL Statement of Work and initiate the funding process for Lambda Buffers. * **Terence:** Schedule separate, dedicated Committee sessions to begin planning for Q3 strategy. | Topic | Discussion | Notes | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Welcome & Agenda Review | Terence opened the meeting for the Open Source Committee and noted a packed agenda. Sebastian stepped in to provide an introduction due to the initial absence of developer advocates. | It was noted that no developer advocates were present right at the start of the call. | | Developer Advocate Milestones | Terence reminded the committee that developer advocates are technically no longer on contract as of last week. They may still submit Q2 milestones that need reviewing. | Terence requested comments/feedback from at least 1 or 2 committee members on each milestone (50–60 total) via GitHub (Open Source Office, Project 71). | | CryptoEQ Briefing & Report Curation | Terence provided an update from a meeting with the CryptoEQ co-founder. The proposal involves a customized, research-backed "Vantage" report rather than a standard radar report. | The report will allow the committee to curate exact metrics, tying directly into current DevX and GovX ecosystem discussions. | | CryptoEQ Budget & Pricing | Terence detailed the shifting cost structure for the CryptoEQ engagement, noting that details can be confusing until seen in writing. | Initial quote was $9,000 + $3,000 social expansion. Revised to \~$6,000 + $1,500, with a further partner discount bringing initial spend to $5k–$6k (50/50 upfront/completion split). | | CryptoEQ Web Traffic Clarification | Terence clarified a past concern regarding CryptoEQ's 120k–130k active users, explaining that this represents total historical web application traffic through partners, not unique monthly users. | Spencer will join the next meeting to answer remaining questions. Committee members are asked to post pre-questions in Discord. | | Historical Reporting Metrics Comparison | Dominik and Bora asked about what metrics would be tracked and how to avoid the delivery delays seen previously with Bitergia (which took 16–20 weeks instead of 8–12 before closing down). | CryptoEQ promised a draft within 4 weeks. Terence suggested a core theme of "Why Haskell" to bridge the gap for outside developers regarding Cardano node accessibility. | | Tooling Proposal Poll Results | Terence reviewed recent Discord votes for outstanding tooling proposals. Both polls met the required voting quorum. | Mesh AI: Approved (7 Yes, 1 Abstain). Moving to Statement of Work (SOW).Midnight Setup: Denied (5 No, 2 Abstain). | | Chella Tooling Presentation | Cullah presented "Cella," an open-source, self-hostable infrastructure tool built to help Cardano Constitutional Committees deliberate and vote internally on complex governance actions. | The tool is currently used internally by Cardano Curia. It acts as a ledger for internal votes and rationale building before pushing the final payload on-chain. | | Chella Funding & Multi-Sig Evaluation | Bora and Dominik asked about Cella's traction, production readiness, and security (hot vs. cold wallets). Terence inquired about the funding band request. | Cullah noted Cella targeted Band 0/1 ($35k–$50k max). The tool uses hot wallets for internal chat/auth but cold wallet integration for the final payload is being finalized. Terence shared a calendar link to sync offline. | | Bug Bounty Program Amendment | Terence and Mike requested the removal of Plutus script evaluations from the public bug bounty program. | Mike explained that this repository is an internal testing tool and local vulnerabilities do not impact the public chain, making a public bounty inefficient. | | Cardano Node Emulator Presentation | Mathieu presented a proposal to update and maintain the Cardano Node Emulator (originally extracted from Plutus Apps). The tool runs actual ledger rules for 100% on-chain compliance. | Mathieu highlighted it provides a fast feedback loop for testing smart contracts in Haskell. Funding is needed to update it to upcoming hard fork standards to prevent it from going stale. | | Emulator Ecosystem Context | Bora and Bernard asked how this tool differentiates from other existing emulators (like Scalus or Yaci) and why the committee should fund it if it was previously left unmaintained. | Mathieu clarified that it was left unmaintained due to Intersect team constraints, not utility. It integrates natively with Haskell. Bernard noted its strong purpose if developers are properly trained on it. | | Lambda Buffers Statement of Work | Bernard raised concerns about a vague statement in the SOW regarding "current versions" and questioned the cross-language user adoption of Lambda Buffers outside of MLabs. | Benjamin and Luke explained that the project was previously approved by the OSC due to its cross-language benefits. They will send GitHub insight metrics and noted adoption by Unbox, Tweag, and Chad Labs. | | Official Voting Verdicts | Terence called for final votes on the active polls before concluding the meeting. | \* Plutus Bug Bounty Removal: Approved (7 Yes, 2 Abstain).\* Cella SOW Request: Approved (6 Yes, 1 Abstain).\* Cardano Node Emulator SOW Request: Approved (8 Yes, 1 No, 1 Abstain).\* Lambda Buffers SOW Approval: Approved (5 Yes, 1 Abstain). | | Next Steps & Q3 Planning | Terence noted that CTL was approved in the last meeting and its SOW is being formalized. Future breakout meetings will be scheduled to handle Q3 planning. | The meeting adjourned with a note that the committee will reconvene in two weeks. | --- # 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, and the optional `goal` query parameter: ``` GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/osc-meeting-minutes/open-source-committee-meeting-minutes/2026-meeting-minutes/07-09-2026-meeting-minutes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.