Intersect - Knowledge Base
Intersect WebsiteBecome a member
  • INTERSECT OVERVIEW
    • What is Intersect?
    • Intersect's structure
      • Intersect values
      • Intersect governance
      • Intersect funding
    • Intersect membership
      • Membership tiers and benefits
    • Working on Cardano
      • Intersect support for Cardano's Governance
      • Intersect support for Cardano Product
      • Intersect support for Cardano Budget
    • Intersect committees
      • Intersect Steering committee
      • Civics committee
      • Membership and Community committee (MCC)
      • Growth & Marketing Committee (GMC)
      • Technical Steering committee (TSC)
        • Parameter committee (PC)
      • Open Source committee (OSC)
      • Budget committee
      • Product committee
    • Intersect groups (working & special interest)
    • Intersect development updates
    • Support and contacts
    • Jump in - key member initiatives
  • Cardano
    • Cardano Budget Submission
      • Intersect as an Administrator
      • Budget Info Action FAQs
      • Budget Glossary
      • Cardano's treasury governance
      • FAQs
    • Cardano governance
      • Governance Overview
      • Cardano Constitution
        • Read the Cardano Constitution
          • Hash
          • Translations
          • Previous versions of the Cardano Constitution
            • Interim Cardano Constitution
              • Translated Interim Constitution
        • 2025 Constitutional Committee elections
          • Guide for Applicants
          • Multi-Stage Task for Constitutional Committee Applicants
          • Guidelines for Participation in a Constitutional Committee Election
      • Governance roles
        • General ada holders
        • Delegated Representatives (DReps)
        • Stake Pool Operators (SPOs)
        • Constitutional Committee
          • Interim Constitution Committee (ICC)
            • Intersect Constitutional Council
            • Interim CC elections
            • Interim CC FAQs
      • Governance tools
        • Voltaire GovTool
        • Constitutional Committee Portal
      • Governance process
        • Off-chain proposal submission and discussion
        • On-chain governance action submission
          • How to submit a governance action through the CLI
        • On-chain DRep registration
        • On-chain DRep delegation
        • On-chain voting
          • Governance action ratification
          • Governance action enactment
        • Off-chain governance action outcome socialisation
      • DRep Pioneering Program
      • SanchoNet
      • Key terms
        • Governance Action
          • GA - Motion of no-confidence
          • GA - New constitutional committee or Quorum size
          • GA - Updates to Constitution
          • GA - Hard-Fork Initiation
          • GA - Protocol Parameter Changes
          • GA - Treasury Withdrawals
          • GA - Info
        • Ratification
        • Enactment
        • Threshold
        • Metadata
        • Chang upgrade
        • CIP-30
        • CIP-95
        • CIP-1694
        • Constitutional Committee
        • Constitution
        • SanchoNet
      • Weekly governance bulletin
    • Cardano hardforks and upgrades
      • Chang & Plomin upgrades
      • Major release process
      • Quality and feedback
    • Cardano economy
      • Cardano treasury
  • Annual member meetings
    • Annual member meetings (AMM)
    • 2024 Annual Member Meetings
  • Intersect voting events
    • 2025 - Intersect elections
      • April 2025 - Committee elections
        • Committees key info
          • Intersect Committee Elections X-Space Events
          • Application Form - Translations
            • Spanish
            • French
            • Japanese
            • Portuguese
            • Sinhala
        • Committee elections FAQs
        • April 2025 - Committee Election Results
          • Voting Results - audit info
      • Onboarding Page
    • 2024 - Intersect elections
      • October 2024 election results
  • Intersect Operational Services
    • Intersect Operational Services Overview
      • Procurement Management
      • Budget Process
    • 2025 Request For Proposal (RFP)
      • Open RFPs
        • Technical Steering Commitee
        • Product Committee
        • Open Source Committee
        • Civics Committee
          • Intersect Stake-Based Voting Tool
            • Requirements
            • Considerations
            • Application Process
        • Membership and Community Committee
        • Budget Committee
      • Eligibility criteria
      • Proposal evaluation criteria
      • Key terms
        • Cardano Improvement Proposal (CIP)
        • CIP-1694
        • CIP-30
        • CIP-95
        • Voltaire GovTool
        • Governance Action (GA)
        • Anchor
        • Metadata (from Anchor)
        • Proposal
        • Proposal ID
        • Metadata Anchor
      • If your project is delayed
    • 2025 Delivery assurance contract updates
      • Delivery Assurance quarterly reports
      • Technical steering committee contracts
        • Tweag - Ouroborus Peras protocol
      • Membership & Community committee contracts
        • Japan Community Hub Interim Contract
        • LATAM Community Hub Interim Contract
        • Sri Lanka Community Hub Interim Contract
        • Africa Community Hub Interim Contract
        • North America Community Hub Interim Contract
        • Europe Community Hub Interim Contract
      • Civics Committee
      • Product committee
        • Dquadrant - GovTool Maintenance - Integrated Testing
        • We Deliver IT - GovTool Maintenance - Proposal Discussion pillar
        • Byron Network - GovTool maintenance - voting & delegation pillars
        • Bloxico Group - DevOps support for governance tooling
        • Bloxico Group - CC Portal Maintenance
        • DQuadrant - GovTool Maintenance
        • Byron Network - Constitutional Committee Voting Tool
        • Lido Nation - GovTool Maintenance - Governance Action outcomes pillar
      • Budget committee
      • Growth & Marketing committee
      • Open source committee
        • Bitergia - Analytics Subscription
    • 2025 Template Contracts
    • 2024 Cardano Continuity contracts
      • Cardano continuity suppliers
        • Cardano continuity progress
          • 2024 Milestone completion reports
            • Milestone report Q1 2024
            • Milestone report Q2 2024
            • Milestone report Q3 2024
            • Open Source Developer Maturity Report May 2024
        • Change management process
    • 2024 Intersect, CDH and Grant Contracts
      • 2024 Intersect Contracts
      • 2024 CDH Contracts
      • 2024 CDH Grants
        • Closed grants
          • Proposal discussion forum
            • Functional requirements
            • Non-functional requirements
            • Optional functions
            • Considerations
            • Key Terms and resources
          • DRep campaign platform
            • Functional requirements
            • Non-functional requirements
            • Optional features
            • Considerations
            • Key Terms and resources
          • Constitutional committee portal
            • Functional requirements
            • Non-functional requirements
            • Optional features
            • Considerations
            • Key terms and resources
          • Education - multimedia content
            • Non-functional requirements
              • Content creation: non-functional requirements
              • Software development: non-functional requirements
              • Open-source requirements
            • Optional features
            • Considerations
            • Key Terms and resources
          • Open category for Cardano governance
            • Functional requirements
            • Non-functional requirements
            • Considerations
            • Key Terms and resources
          • DRep Pioneering Program
          • Inclusion and Accessibility phase 1
            • Functional requirements
            • Non-functional requirements
            • Considerations
            • Key Terms and resources
          • DevOps for Governance Tools
            • Functional Requirements
            • How to apply
          • Constitutional workshops
            • Constitutional workshop guidelines
            • FAQs
            • Key terms and Resources
            • Your commitment as a host
            • Apply to become a constitutional workshop host
          • Local face-to-face events and meet-ups
          • GovTool Governance Action Outcome
            • Application
            • Functional Requirements
            • Non Functional Requirements
            • Considerations
            • Expected cost range
          • Constitutional Convention Voting Tool
            • Application
            • Functional Requirements
            • Non Functional Requirements
            • Expectations
          • Community hubs
          • Inclusion and Accessibility phase 2
            • A Grant to implement the translation tool
            • Grants to translate GovTool and the Constitutional Committee Portal
            • Grants to translate the Interim Constitution
  • Intersect Website and Member area
    • Roadmaps
      • Intersect website roadmap
      • Intersect member area roadmap
    • Releases
      • May 15th
      • May 29th
      • June 12th
      • August 6th
      • August 23rd
      • Recent updates
  • Intersect Team
    • Open positions
      • Finance Lead
      • Social media and content manager
    • Closed positions
      • Grant Analysis & Support
      • Financial Controller
      • Community Engagement Manager - Cardano constitution consultation
      • Senior Project Manager - Cardano Governance Tools
      • Design System Lead
      • Platform/DevOps Engineer
      • Programme Support
  • LEGAL
    • Intersect's bylaws
    • Policies and conditions
      • Cookie Policy
      • Terms of Use
      • Privacy Policy
      • Code of Conduct
      • Intellectual Property Rights Policy
      • Intersect Open-Source Antitrust Statement
      • Intersect Open-Source Glossary
      • Roberts Rules of Order – Simplified
      • Conflict of Interest
      • Transparent Dealings Policy
      • Data Access and Confidentiality Policy
    • Intersect Membership Agreements
      • Intersect Membership Agreement V1
  • Glossary
    • General Glossary
      • A
        • ada
      • C
        • Cardano Ballot
        • Cardano Civics Committee
        • Cardano Improvement Proposal
        • Cardano institutions
        • Cardano Problem Statement
        • Cardano repositories
        • Chang upgrade
        • CIP-30
        • CIP-95
        • CIP-1694
        • Constitution
        • Constitutional Committee
        • Constitutional Convention
      • D
        • Delegated Representatives (DReps)
      • G
        • Governance action
        • Governance tools
      • I
        • Interim Constitution
        • Intersect
        • Intersect Grants
      • M
        • Members-based organization
        • Minimum Viable On-Chain Governance
      • P
        • Parameter Committee
        • Project Catalyst
      • R
        • Ratification
      • S
        • SanchoNet
        • Stake Pool Operator
      • T
        • Technical Steering Committee
      • V
        • Voltaire
      • W
        • Working groups
Powered by GitBook
On this page

Was this helpful?

  1. Cardano
  2. Cardano Budget Submission

Budget Info Action FAQs

PreviousIntersect as an AdministratorNextBudget Glossary

Last updated 10 days ago

Was this helpful?

Important note: Greater than 50% of active delegated DRep stake is required to pass a Budget Info Action. This does not result in the movement of any funds from the Cardano Treasury. If approved, it marks the next step toward funding, with Treasury Withdrawal governance actions required to be passed and enacted. These withdrawals require a higher threshold of over 67% DRep approval to release funds from the Cardano Treasury.

The Budget Info Action is a formal on-chain governance step that allows DReps and the Constitutional Committee to review and ratify an aggregate budget before any Treasury funds can be released. In Intersect’s case, our budget info action reflects the outcome of a community-driven process, where proposals were submitted, refined, and signaled on by DReps using the Ekklesia platform.

This action does not release funds - it authorizes the proposed allocation as a whole. Once approved, individual Treasury Withdrawal Actions must be submitted to release funds, subject to further approval and within the limits of the active Net Change Limit (NCL).

Why do we have an omnibus budget proposal instead of individual requests?

This Budget Info Action takes an omnibus approach, combining 39 proposals into a single submission for on-chain approval. It reflects the outcome of a coordinated, community-led budget process facilitated by Intersect and validated through DRep signaling on the Ekklesia platform, where over ₳3.8 billion in live stake participated.

This structure helped ensure strategic alignment with the Cardano Vision and Roadmap, reduced the risk of decision fatigue for DReps, and allowed for a clearer, more unified picture of the ecosystem’s priorities. Each included proposal was transparently published, timestamped, and stored via IPFS, and disbursements will still require individual governance actions and compliance with due diligence requirements.

That said, the omnibus format has trade-offs. It reduces voting granularity at the final approval stage, requiring DReps to accept or reject the entire bundle rather than each proposal individually. It also introduces greater coordination complexity, especially when managing different timelines and delivery models across the included proposals.

We recognize this may not be the ideal long-term model for Cardano. However, this proposal reflects verified DRep support and upholds the integrity of the signaling process. Not submitting it on-chain would mean acting on sentiment rather than signal - and would risk losing momentum at a pivotal time.

If DReps decide this format isn't suitable, we are ready to explore more modular approaches in future cycles. For now, this submission represents the most accurate and accountable expression of the community’s budget preferences.

Will this move all ₳275 million at once?

No. This Budget Info Action does not result in the immediate movement of any ADA. It represents the aggregate total of proposals that received over 50% support from participating DReps during the Ekklesia signaling process. Actual disbursement of funds will only occur through separate Treasury Withdrawal governance actions, each of which must be submitted and approved individually. These withdrawals must:

  • Receive over 67% support from active voting DReps,

  • Remain within the active Net Change Limit (NCL),

  • Pass due diligence checks, including KYC/KYB and AML where required, and

  • Be supported by a formal agreement between the delivery organization and either Intersect or Cardano Development Holdings.

Where applicable, funds will be distributed via smart contract-based escrow mechanisms, with multisig oversight involving Intersect, auditors, and other appointed parties. These contracts only become active if the corresponding Treasury Withdrawal is approved.

In short, this Budget Info Action enables a coordinated funding framework, but no funds move without a second round of on-chain approval.

Won’t withdrawing all this ada all at once have a negative effect on the price?

The Budget Info Action does not result in an immediate withdrawal of 275M ada from the Treasury. It simply authorizes an aggregate budget allocation.

Any actual withdrawal of funds happens gradually, through separate governance actions, and only after meeting agreed conditions such as delivery milestones and oversight checks. This process is designed to ensure responsible allocation over time - not sudden or uncontrolled releases.

How does Intersect manage funding and associated risks?

Intersect’s role as an Administrator is to provide oversight, coordination, and accountability for the proposals that have requested it. Intersect does not manage or hold Treasury funds directly - those are released through approved governance actions and, where applicable, distributed via smart contracts or authorized accounts.

To help manage associated risks and ensure responsible use of Treasury funds, Intersect applies the following safeguards:

  1. Due diligence before engagement: Proposals must pass due diligence - including KYC/KYB and other verification checks - before Intersect will enter into any contractual agreement or support a Treasury Withdrawal.

  2. Oversight of delivery, not custody of funds: Once Treasury funds are released (following approval), Intersect’s role is to monitor progress, ensure contractual terms are being followed, and coordinate with auditors, vendors, and the community.

  3. Escrow and control structures (where applicable): Some proposals may use smart contracts or multisig escrows to hold and release funds. Intersect may be a signer or observer in these setups, but it does not control disbursements unilaterally.

  4. Pause and recovery mechanisms: If a funded proposal breaches terms, Intersect can recommend pausing disbursements or initiating recovery actions. Undisbursed funds may be returned to the Treasury if issues remain unresolved.

  5. Public reporting and transparency: Intersect will publish regular delivery updates and reporting for all proposals under its oversight, giving the community visibility into how funds are being used.

In short, Intersect acts as a facilitator and enabler of accountability, not a fund manager - ensuring that proposals live up to their commitments and that Treasury funding is responsibly tracked and governed.

Why did every proposal name Intersect as Administrator? Isn’t this centralizing control and increasing the risk of capture?

Intersect was named as Administrator by these proposals because it offered a structured pathway to participate in a coordinated, community-led budget process. This process included open submission, committee feedback, DRep signaling, and alignment with the Cardano roadmap, all made possible through Intersect’s support infrastructure. Participation was entirely optional, and proposers were free to submit standalone on-chain budget actions independently.

This is not about centralizing control. It is about enabling coordination in the absence of other fully operational budget facilitation alternatives. Intersect does not control funds, and its role as Administrator is limited to oversight, coordination, and transparency, not execution or decision-making authority.

Crucially:

  • Intersect was requested by the proposers themselves, not assigned unilaterally

  • Other entities are free to play this role in future budget cycles

  • Intersect may refuse to act as Administrator if proposals do not meet due diligence or governance standards

  • On-chain governance remains the final authority, with DReps and the Constitutional Committee approving all Treasury withdrawals

As the ecosystem matures, we expect to see multiple Administrators, diversifying responsibility and reducing any perceived concentration. This first round simply reflects the practical need for facilitation during a transitional governance phase.

Who checks if milestones are real or realistic? What prevents teams from gaming the system?

A multi-sig oversight body including Intersect, auditors, and independent ecosystem actors will have authority to pause payouts, demand arbitration, and ultimately return unused funds to the treasury. Intersect is currently talking a number of proven and responsible ecosystem players to fulfil this role and more news will be shared on this soon. Delivery is made public through a new dashboard, with milestone documentation and outcomes openly tracked.

What if a project goes bust or fails to deliver? What happens to the funds?

If a funded project fails to meet its obligations or goes bust, several safeguards are in place to protect Treasury resources:

  1. Pause or stop disbursements: Intersect, working with oversight partners, can pause further payments if a project breaches its contract or misses key deliverables.

  2. Claw-back mechanisms: If funds remain undisbursed in a smart contract or designated account, they can be returned to the Treasury following a resolution process, including arbitration if needed.

  3. Milestone-based or conditional payments: Where applicable, funding is released in phases tied to verifiable progress. This limits exposure in the event of non-delivery.

  4. Oversight and reporting: Intersect and elected committees monitor delivery across proposals. Issues are flagged early to reduce risk and ensure transparency.

In short, funds are not handed over in full at once. If a project fails, any unspent or unearned funds can be recovered or withheld, helping safeguard the Treasury and community interests.

This was all decided off-chain. Can’t that be manipulated? Why not do everything on-chain?

This budget process was an attempt to coordinate a community-driven approach using the tools and structures currently available. While we acknowledge it was imperfect and at times haphazard, it resulted in strong participation and clear signal from active DReps using live stake through the Ekklesia platform. The Ekklesia vote results were also recorded on-chain to create an immutable record.

As an ecosystem, we need to take the lessons learned from this process and work together to rebuild it - making it clearer, more inclusive, and more resilient. Moving forward, the community may well choose to make greater use of on-chain governance directly, with fewer off-chain coordination steps.

What assurance is there that Intersect won't misuse its role or become too powerful?

Intersect’s authority comes from the community. It does not control funds, cannot approve Treasury withdrawals on its own, and is accountable to both DReps and the Constitutional Committee.

Here are the key safeguards:

  1. No unilateral power: Intersect cannot spend Treasury funds. Every withdrawal requires a separate on-chain vote by DReps and must comply with constitutional guardrails.

  2. Voluntary designation: Proposers chose Intersect as Administrator for this process. They are free to select other Administrators in the future or submit proposals directly on-chain without Intersect’s involvement.

  3. Transparent oversight, not control: Intersect provides coordination, due diligence, and reporting. It does not act as a gatekeeper or hold exclusive rights to administer funding.

  4. Subject to community checks: Intersect’s actions can be scrutinized, challenged, or overridden through Cardano’s governance mechanisms. Its ongoing role depends entirely on the trust and support of the community.

  5. Designed to be temporary and plural: This process reflects a transitional phase. In future budget cycles, more Administrators are expected to emerge, reducing reliance on any single actor.

Intersect’s legitimacy is earned through transparency, delivery, and accountability, not through control.

How does info action relate to the Net Change Limit (NCL)? What if the NCL is lower than the proposed budget info action?

The Budget Info Action proposes an aggregate allocation from the Treasury, but does not spend funds directly. Actual spending occurs later through Treasury Withdrawal Actions, which must comply with the active Net Change Limit (NCL) at the time they are submitted. The current NCL that is approved and active is set at 350m ada.

If the NCL is lower than the total budget approved in the Info Action, only withdrawals within the available NCL can proceed. The remaining proposals must wait until the NCL is increased or a future window opens. In this way, the NCL serves as a safeguard, ensuring that Treasury spending remains fiscally constrained, even if a larger budget has been approved.