Intersect Technical Steering Committee Support
Intersect Technical Steering Committee
ID: 69f38e85985067f4ae957a5e
Intersect's Technical Steering Committee (TSC) requests $298,250 (1,193,000 ADA) to support activities for 12 months, spanning community engagement, protocol governance, and independent technical review. Cardano's continued growth as a decentralised, mission-critical blockchain depends on robust technical governance infrastructure. The TSC exists to provide that infrastructure — ensuring the ecosystem's technical direction is guided by expertise, that community members and DReps have the information they need to make sound governance decisions, and that the processes governing protocol evolution are structured, transparent, and accountable. WP 1 funds attendance of technical experts at major ecosystem events and commissioning of technical reports. WP 2 funds three specialist groups: the Parameter Committee, CIP editors, and Hard Fork Working Group. WP 3 funds establishment of a pilot independent technical review programme launching in 2027. Three areas of TSC-related activity are funded separately through the main Intersect budget and are not included here: technical workshops (delivered under TSC technical leadership), the Security Council, and the Bug Bounty Programme. All expenditure will be fully accounted for and any unspent funds returned to the Cardano treasury. The work described is not discretionary — it represents the foundational technical governance capacity that Cardano needs to function effectively as a decentralised ecosystem. **Note:** The execution of the work packages outlined in the proposal is contingent on the IntersectMBO budget proposal's approval.
Scorecard
How this score works
Each criterion is worth between 1 and 4 points. The score is the points earned out of the points on criteria that have been answered — shown as a percentage. Green is 75% or higher, Amber is 50–74%, and Red is below 50%.
Some criteria are checked automatically against the proposal data (open source, doxxed team, treasury return clauses, etc.). Others are human-judgment calls — value for money, public good, whether the deliverables are realistic. Those stay blank until a DRep ticks them.
Criteria can also be marked Not applicablewhen they don't fit the proposal — for example, "open source" doesn't apply to a DAO governance proposal with no software output. Those are excluded from the score entirely, neither helping nor hurting.
Green requires 80% coverage. If less than 80% of the applicable criteria (by points) have been answered, the verdict stays at Amber — "pending review" — even when every answered criterion passes. This proposal's coverage is currently 68% (13 of 19 applicable criteria answered). The auto-calculated band would have been Green, but coverage is below the threshold so the verdict is shown as Amber to flag that judgment criteria are still pending.
Vote intent
Export & audit
↓ Download scorecard.mdRaw payload · Treasury (true) / Admin (self_with_oversight)
{
"_meta": {
"schema_version": "1.2.0",
"proposal_id": "69f38e85985067f4ae957a5e",
"proposal_title": "Intersect Technical Steering Committee Support",
"proposer": "Intersect Technical Steering Committee",
"filename": "hydra-intersect-tsc-support.json",
"processed_date": "2026-05-11",
"title": "Intersect Technical Steering Committee Support"
},
"ask": {
"ada_amount": 1193000,
"usd_amount": 298250,
"ada_usd_rate_assumed": 0.25,
"usd_peg_vs_market": "neutral",
"duration_months": 12,
"milestone_payments_disclosed": true,
"milestone_schedule_disclosed": "amounts_and_dates",
"milestone_notes": "Each WP has mid-year and year-end milestones with explicit acceptance criteria; WP3 has 8-week and 4-week pilot framework milestones."
},
"identity": {
"doxxed": true,
"doxxed_notes": "TSC is an elected Intersect committee with publicly identifiable members; track record cited via Chang/Plomin/van Rossem hard fork coordination."
},
"metadata": {
"open_source": "yes",
"has_prior_delivery": true,
"prior_delivery_notes": "TSC coordinated Chang and Plomin hard forks; Parameter Committee operates on 3-week cycle; Bug Bounty Programme launched late 2025; November 2025 chain partition incident response cited.",
"admin_model": "self_with_oversight",
"admin_notes": "Intersect administers (technical clarification — same controls as third-party admin); Appold provides independent assurance.",
"duplicate_of_existing_solution": {
"value": "no",
"confidence": "high",
"set_by": "ai"
}
},
"treasury_return": {
"has_return_clause": true,
"treasury_favourability": "moderate",
"return_notes": "All expenditure fully accounted for; any unspent funds returned to Treasury at end of 12-month period."
},
"relationships": {
"competes_with": []
},
"ecosystem_demand": {
"evidence_level": "strong",
"evidence_level_confidence": "high",
"evidence_level_set_by": "ai",
"active_users_known": true,
"active_users_examples": [
{
"name": "Cardano DReps",
"kind": "user"
},
{
"name": "Cardano SPOs",
"kind": "user"
},
{
"name": "CIP authors and editors",
"kind": "user"
},
{
"name": "Node implementation teams (IOG, TxPipe, etc.)",
"kind": "integrator"
}
],
"developer_demand_signals": [
"Active CIP pipeline requires editor capacity",
"Hard fork coordination is mandatory for any protocol upgrade",
"Parameter Committee already meets on 3-week cycle with documented outputs",
"DRep participation rate KPI in 2030 strategy depends on accessible technical reviews"
],
"adoption_risk_notes": "Core technical governance infrastructure — Parameter Committee, CIP editors, Hard Fork WG — has direct, demonstrable demand from existing protocol governance processes. Technical reports and event attendance are softer demand but the specialist groups address concrete unfunded work."
},
"incumbents": {
"has_existing_solution": "no",
"has_existing_solution_confidence": "high",
"has_existing_solution_set_by": "ai",
"existing_solutions": [],
"differentiation_claim": "TSC is the mandated body within Intersect governance for protocol-level technical stewardship; no other body combines technical depth with cross-ecosystem governance role.",
"differentiation_credibility": "high"
},
"risk_flags": {
"aggressive_peg": false,
"self_administered_no_oversight": false,
"incumbent_already_delivering": false,
"no_evidence_of_demand": false,
"competes_with_in_batch": false,
"concentration_risk": false
},
"id": "hydra-intersect-tsc-support",
"source": {
"hydra_id": "69f38e85985067f4ae957a5e",
"channels": [
"hydra"
]
}
}