← The LedgerVote record
tx 999f1149dc1a4c496c70e5841ce9d19ee0f8313c8d9cc945c545a8218ff5ffca
One transaction — 6 vote certificates
YES
Withdraw ₳750,000 for Cardano Product Committee: Community-driven 2030 Carda...
Epoche572
Cast2025-07-24
Requested750K ₳
OutcomeENACTED
This treasury withdrawal funds **Cardano Product Committee: Community-driven 2030 Cardano Vision and 2026 roadmap insights collection via workshops and structured product research** which will provide the following services:
One of the key community goals in 2025 is to create a shared long-term vision, transitioning from the roadmap created by Cardano's founders to a community-led dynamic vision and yearly roadmap.
To create the first community driven 2030 Cardano vision, and a following 2026 roadmap, the Cardano Product Committee of Intersect, via consultation, has drafted a strategy (which is already operational) which includes both broad consultation via workshops (remote and in-person) and focused insights collection via focus group calls, with key ecosystem stakeholders (like SPOs) and businesses (both in Cardano and outside Cardano), and incentivized structured user and market research with an initial set of broad questions divided by the broad Cardano goals. [https://productcommittee.docs.intersectmbo.org/committee-outcomes/2025-cardanos-roadmap/2025-proposed-cardano-goals](https://productcommittee.docs.intersectmbo.org/committee-outcomes/2025-cardanos-roadmap/2025-proposed-cardano-goals)
This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
750,000 ADA for the Cardano Product Committee and community coordination.
What would have to be true for this to be a good use of treasury funds
Product direction across a decentralized ecosystem is genuinely hard, and somebody thinking about coherence rather than individual features has value.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. Committees are where ecosystems quietly accumulate overhead, and Cardano already has a lot of committee surface relative to shipped product.
What I am asking of the proposer if this passes
It was enacted. Show decisions the committee shaped and outcomes that followed. If the output is meeting minutes, this is overhead. If it is a coherent roadmap the ecosystem actually follows, it is cheap.
YES
Withdraw ₳130,903 for Lucid Evolution Maintenance administered by Intersect
Epoche572
Cast2025-07-24
Requested131K ₳
OutcomeENACTED
This treasury withdrawal funds **Lucid Evolution Maintenance** which will provide the following services:
Lucid Evolution is an open-source library designed to simplify and enhance the development of off-chain smart contract interactions on Cardano. As the official maintainer of Lucid, Anastasia Labs is committed to evolving the library ensuring long-term support and usability for developers.
This proposal seeks funding to support ongoing development, maintenance, and ecosystem adoption efforts, including compatibility updates, feature enhancements, and developer documentation. By securing funding, Lucid Evolution will continue to serve as a critical tool for DApp developers, improving accessibility and efficiency within the Cardano ecosystem.
This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
130,903 ADA for Lucid Evolution maintenance, administered by Intersect.
What would have to be true for this to be a good use of treasury funds
Lucid Evolution is one of the most used transaction-building libraries in Cardano. A large share of DApps depend on it whether their teams think about it or not.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. At roughly 130,000 ADA for a library this widely depended on, my only real concern is bus factor: heavily used tooling with few maintainers is a systemic risk.
What I am asking of the proposer if this passes
It was enacted. Grow the contributor base beyond the current maintainers. The insurance policy for critical tooling is people, not budget.
YES
Withdraw ₳300,000 for Ledger App Rewrite administered by Intersect
Epoche572
Cast2025-07-24
Requested300K ₳
OutcomeENACTED
This treasury withdrawal funds **Ledger App Rewrite** which will provide the following services:
Vacuum Labs will work with Ledger team to design new UI according to the expectations. Implement new UI into the Cardano Ledger App. Pass the external audit process (costs for this shall be included in proposal). Support the Ledger team by the release process.
This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
300,000 ADA for the Ledger app rewrite, administered by Intersect.
What would have to be true for this to be a good use of treasury funds
Hardware wallet support is the security floor of this ecosystem. I tell people constantly to self-custody and use cold storage, and voting to keep that path working is the least I can do to back the advice.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. Nothing at this size. Hardware wallet work is closer to a seatbelt than a feature: you do not skip maintenance on it.
What I am asking of the proposer if this passes
It was enacted. Compatible releases ahead of every protocol change, without exception. A hard fork where Ledger users cannot sign would undo years of self-custody advocacy in a week.
YES
Withdraw ₳15,750,000 for a MBO for the Cardano ecosystem: Intersect
Epoche572
Cast2025-07-24
Requested15.8M ₳
OutcomeENACTED
This treasury withdrawal funds **A member-based organization for the Cardano ecosystem: Intersect** which will provide the following services:
Intersect exists to serve as a neutral, nonprofit coordination layer that bridges decentralized governance and decentralized infrastructure. Our mission is not to direct the network, but to enable it. By stewarding core systems, supporting community-led processes, and facilitating safe, transparent delivery.
Specifically, this proposal will fund Intersect to:
- Steward core infrastructure
- Execute the Administrator role
- Support participation and coordination
- Facilitate roadmap and budget processes
- Expand ecosystem capacity
Note: Intersect's original proposal submitted early in the off-chain process was updated after recent leadership changes. However, this proposal reflects the approved Budget Info Action and new strategic direction.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
15,750,000 ADA for a Member Based Organization for the Cardano ecosystem.
What would have to be true for this to be a good use of treasury funds
Somebody has to coordinate technical stewardship, hard fork coordination, and incident response. Those functions are not optional for a chain that wants to be taken seriously by institutions.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. On this item, size and concentration are the real issues. Fifteen million is a lot of coordination, and Cardano routes an uncomfortable amount of its governance machinery through a small number of organizations. I have voted yes on the MBO's later, reduced asks as well, and the direction I want is exactly what happened there: the ask shrinking while continuity functions stay intact.
What I am asking of the proposer if this passes
It was enacted. Keep publishing what the money buys, and keep the number trending down as the ecosystem matures. A coordination body whose budget grows every year is a coordination body that has stopped being coordination.
YES
Withdraw ₳424,800 for Hardware Wallets Maintenance administered by Intersect
Epoche572
Cast2025-07-24
Requested425K ₳
OutcomeENACTED
This treasury withdrawal funds **Hardware Wallets Maintenance** which will provide the following services:
- Update Ledger and Trezor firmware and integration libraries with new relevant Cardano features or breaking changes. Update also if there are any breaking changes in Ledger and Trezor core firmware code, testing suites, etc.
- Update cardano-hw-cli to reflect firmware changes and to reflect user needs
- Support Keystone developers while doing the changes above
- Provide general cardano hw wallets maintenance, development support and bugfixing.
- Order and manage external code audits for Ledger firmware code (Ledger requirement, has to be done by one of 2 certified auditors)
This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
424,800 ADA for hardware wallet maintenance, administered by Intersect.
What would have to be true for this to be a good use of treasury funds
Ledger and Trezor support has to survive every protocol change on our side and every firmware cycle on theirs. When that breaks, the most security-conscious holders in the ecosystem lose access to their own funds.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. Nothing specific to this item. Continuity funding for a security-critical access layer is cheaper than the breakage it prevents.
What I am asking of the proposer if this passes
It was enacted, and I have voted yes on hardware wallet maintenance again in later cycles. Same ask each time: compatible releases before mainnet hard forks, with enough lead for integrators to test.
YES
Withdraw ₳220,914 for UTxO RPC: Sustaining Cardano Blockchain Integration
Epoche572
Cast2025-07-24
Requested221K ₳
OutcomeENACTED
This treasury withdrawal funds **UTxO RPC: Sustaining Cardano Blockchain Integration** which will provide the following services:
This request for support focuses on UTxO RPC [https://utxorpc.org](https://utxorpc.org) an interface specification designed to simplify interactions with UTxO-based blockchains. U5C defines standardized methods, data structures, and communication patterns. By providing a range of SDKs, and offering thorough documentation, U5C enhances reusability, interoperability, and performance in blockchain integrations. Currently in its early stages, UTxO RPC is already being adopted by key projects in the Cardano ecosystem, including Lace, Mesh, Amaru, and many others. As an open-source initiative, it welcomes contributions from the community, fostering a collaborative approach to improving blockchain infrastructure. To support its ongoing development, maintenance, and enhancements, we are requesting funding for the following roles: 0.5 FTE blockchain developer and 0.125 FTE tech lead.
This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.
This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.
Reasoning
Written after the vote was cast
What this asks for, and from whom
220,914 ADA for UTxO RPC, the open interface standard for interacting with UTxO chains.
What would have to be true for this to be a good use of treasury funds
Standards that alternative node implementations and the reference node all speak are how an ecosystem avoids fragmenting into incompatible islands.
What specifically concerns me
This was part of the 2025 Intersect budget slate, which I voted as a slate. I am saying that plainly rather than pretending each line got its own week of deliberation. The slate came through a community budget process with a support threshold before it ever reached the chain, and my judgment was that the process outcome deserved backing in Cardano's first real treasury cycle. Nothing material here. I have voted yes on UTxO RPC maintenance again in later cycles, so this is consistent support for infrastructure that keeps proving itself.
What I am asking of the proposer if this passes
It was enacted. Keep the adopter list public. Standards justify their funding by who uses them, and that list is the whole argument.