Skip to content

Commit bf7b23f

Browse files
l-br1gitbook-bot
l-br1
authored and
gitbook-bot
committed
GITBOOK-1274: Intersect 2026 Budget Proposal
1 parent 45e755b commit bf7b23f

3 files changed

Lines changed: 158 additions & 0 deletions

File tree

‎SUMMARY.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,7 @@
108108
* [FAQs - Budget Process](https://budgetcommittee.docs.intersectmbo.org/cardano-budget-process/cardano-2026-budget-process-faqs)
109109
* [2026 Budget Process - timeline](cardano-facilitation-services/cardano-budget-2026/2026-budget-process-timeline.md)
110110
* [Intersect Hydra Voting - Tool](https://hydra-voting.intersectmbo.org/)
111+
* [Intersect 2026 Budget Proposal](cardano-facilitation-services/cardano-budget-2026/intersect-2026-budget-proposal.md)
111112

112113
## Updates
113114

‎cardano-facilitation-services/cardano-budget-2026/intersect-2026-budget-proposal.md‎

Lines changed: 142 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,142 @@
1+
---
2+
description: This page provides an overview of the 2026 Intersect Budget Proposal and FAQs
3+
---
4+
5+
# Intersect 2026 Budget Proposal
6+
7+
{% hint style="info" %}
8+
## Where to read the full proposal
9+
10+
You can review and comment the latest version of the Intersect Budget proposal on the Intersect Hydra-Voting tool
11+
12+
<a href="https://hydra-voting.intersectmbo.org/votes/cardano-budget-2026/69e7a834d6a29288536b1200" class="button primary">Read the full proposal</a>
13+
{% endhint %}
14+
15+
## Proposal overview
16+
17+
This proposal funds Intersect’s core operating model for June 2026 to June 2027: the Member Based Organization that supports open ecosystem coordination, a reserved capacity to address critical unowned processes, and critically technical stewardship, incident response, and release coordination required to help keep Cardano secure, reliable, and operationally resilient.
18+
19+
This proposal reflects how Intersect has evolved to better match the needs of the ecosystem. Over the past two years, Intersect has matured from a new coordination body into a more focused operational layer for Cardano. That includes supporting committees and working groups, stewarding the core Haskell repositories, coordinating upgrades and incident response, and administering community-approved initiatives through a distinct and more scalable model.
20+
21+
Our proposal is more focused than last year’s. Compared to last year, the overall ask has reduced from $7.875M to $6.35M, while preserving the functions that are most critical to Cardano’s continuity and maturity.
22+
23+
That technical remit should not be underestimated. Intersect has already coordinated two network upgrades, is preparing for a third, and led ecosystem coordination during the November 2025 chain partition incident. As Cardano moves further into decentralized governance, a multi-client future, and the advancements of AI models this function becomes more important, not less.
24+
25+
Funding this proposal means Cardano retains an open coordination layer for governance participation, a mechanism to respond to critical unowned issues, and a technical stewardship function covering release coordination, incident response, repository management, and security initiatives such as bug bounties. Together, these functions provide the operational backbone that helps Cardano evolve with resilience, accountability, and confidence.
26+
27+
## FAQs
28+
29+
<details>
30+
31+
<summary><strong>What is this proposal trying to achieve?</strong></summary>
32+
33+
This proposal funds Intersect as a **coordination and technical stewardship layer** for Cardano, ensuring governance works effectively and the network remains stable, secure, and operational over the next 12 months.
34+
35+
</details>
36+
37+
<details>
38+
39+
<summary><strong>Why does Cardano need this?</strong></summary>
40+
41+
In a decentralized ecosystem, many critical functions (coordination, incident response, upgrades) **don’t have a single owner**. Without a coordination layer, these become fragmented and risky.
42+
43+
</details>
44+
45+
<details>
46+
47+
<summary><strong>What are the main components of the proposal?</strong></summary>
48+
49+
The proposal is structured into **three work packages**:
50+
51+
* Governance & ecosystem coordination (MBO operations)
52+
* Technical stewardship & incident response
53+
* Coordination of critical unowned processes
54+
55+
</details>
56+
57+
<details>
58+
59+
<summary><strong>What is actually being funded?</strong></summary>
60+
61+
Funding covers:
62+
63+
* Operational infrastructure (legal, finance, governance ops)
64+
* Committee and governance support
65+
* Technical coordination (repos, upgrades, incident response)
66+
* Security (bug bounties, response teams)
67+
* Ecosystem coordination tools and processes
68+
69+
</details>
70+
71+
<details>
72+
73+
<summary><strong>How much is being requested?</strong></summary>
74+
75+
The total ask is **\~$6.35M (down from \~$7.875M last year)**, with detailed breakdowns across work packages and cost categories.
76+
77+
</details>
78+
79+
<details>
80+
81+
<summary><strong>What value should DReps expect?</strong></summary>
82+
83+
Expected outcomes include:
84+
85+
* Better coordination across ecosystem actors
86+
* More reliable upgrades and incident response
87+
* Higher-quality governance proposals
88+
* Increased participation and ecosystem alignment
89+
90+
</details>
91+
92+
<details>
93+
94+
<summary><strong>How will success be measured?</strong></summary>
95+
96+
Key metrics include:
97+
98+
* Participation in governance (committees, working groups)
99+
* Successful upgrades and incident response
100+
* Output quality (proposals, reports, initiatives)
101+
* Ecosystem trust and feedback
102+
103+
</details>
104+
105+
<details>
106+
107+
<summary><strong>What has Intersect delivered so far?</strong></summary>
108+
109+
Track record includes:
110+
111+
* Coordinating multiple network upgrades
112+
* Managing the 2025 chain partition incident
113+
* Supporting governance structures (committees, constitution, budget process)
114+
* Maintaining 100+ repositories
115+
116+
</details>
117+
118+
<details>
119+
120+
<summary><strong>What are the risks if this is NOT funded?</strong></summary>
121+
122+
Potential risks:
123+
124+
* Fragmented coordination
125+
* Slower or ineffective incident response
126+
* Poorly aligned upgrades
127+
* Reduced governance effectiveness and participation
128+
129+
</details>
130+
131+
<details>
132+
133+
<summary><strong>Are there safeguards or accountability mechanisms?</strong></summary>
134+
135+
Yes:
136+
137+
* Milestone-based delivery and reporting
138+
* Public updates each quarter
139+
* Measurable KPIs and outputs
140+
* Unused funds can be returned to the treasury in specific cases
141+
142+
</details>

‎intersect-overview/jump-in-key-member-initiatives.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,21 @@ Check the full timeline [here](../cardano-facilitation-services/cardano-budget-2
5454

5555
</details>
5656

57+
<details>
58+
59+
<summary><strong>Intersect Budget Proposal</strong></summary>
60+
61+
This proposal funds Intersect’s core operating model for June 2026 to June 2027: the Member Based Organization that supports open ecosystem coordination, a reserved capacity to address critical unowned processes, and critically technical stewardship, incident response, and release coordination required to help keep Cardano secure, reliable, and operationally resilient.
62+
63+
{% hint style="info" icon="link" %}
64+
**Useful Links**
65+
66+
* Intersect Budget Proposal on Hydra-Voting tool
67+
* [FAQs](../cardano-facilitation-services/cardano-budget-2026/intersect-2026-budget-proposal.md#faqs)
68+
{% endhint %}
69+
70+
</details>
71+
5772
## Happening Next
5873

5974
<details open>

0 commit comments

Comments
 (0)