CCCrypto Crow · Cardano dRep

← The Ledger

Vote record

tx 229ac490c2435350fe74da0efd8aadcd5afe1799072a8cbbe1a3f711a3c7a989

One transaction — 4 vote certificates


YES

Replace Interim Constitutional Committee

Epoche573
Cast2025-07-31
Requested
OutcomeENACTED

This governance action proposes to replace the current Interim Constitutional Committee with the new committee selected by participating DReps during the Intersect-hosted election process from May 5th to July 6th, 2025.

Reasoning

Written after the vote was cast

What this asks for, and from whom

Replacing the Interim Constitutional Committee with the committee selected by participating Dreps in the Intersect-hosted election held May through July 2025.

What would have to be true for this to be a good use of treasury funds

No funds involved. The interim committee was always meant to be temporary, and honoring an election result is the minimum requirement for governance to mean anything.

What specifically concerns me

Election turnout and the concentration of the process in a single facilitating organization. Both are real, and both are symptoms of a governance system this ecosystem started operating before it was ready. But refusing to seat an elected committee because the election was imperfect would be worse than seating it.

What I am asking of the proposer if this passes

It was enacted. Publish committee votes and reasoning consistently. A Constitutional Committee whose reasoning is invisible will be assumed to be political, fairly or not, and this ecosystem has enough of that already.


YES

Withdraw ₳657,692 for Scalus - DApps Development Platform

Epoche573
Cast2025-07-31
Requested658K ₳
OutcomeENACTED

This treasury withdrawal funds **Scalus - DApps Development Platform** which will provide the following services: Developing DApps on Cardano shouldn't require juggling multiple languages, libraries and frameworks. Scalus changes this by bringing the power of Scala 3 to the Cardano ecosystem, letting you write smart contracts, build transactions, and application layers --- all with the same language and familiar tools. It supports the complete development flow - setup, development, testing, debugging and deployment, backed by an industry-grade toolset and professional development experience. Key benefits that make Scalus + Scala 3 stand out: - Productivity boost at scale with Scala 3 - Reduced time-to-market - from prototyping to production in less time - Deep pool of Scala/Java/Kotlin talent available on the market Scalus is a Cardano DApps development platform made for professionals and businesses who want to get things done. 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

657,692 ADA for Scalus, the JVM-native Cardano DApp development platform by Lantr Engineering, administered by Intersect.

What would have to be true for this to be a good use of treasury funds

JVM developers are another large pool Cardano does not reach by default. Scalus components are reused inside widely used Cardano tooling, so plenty of teams depend on it without knowing they do.

What specifically concerns me

Nothing at this size. Worth noting for the record: I supported Scalus here at roughly 658,000 ADA, and later voted yes again on their reduced 2,464,844 ADA resubmission at epoch 644 after refusing to reward the oversized 8.5 million version. Consistent support for a team with a delivery record, at a size proportionate to the work.

What I am asking of the proposer if this passes

It was enacted. Keep publishing the delivery record. Three years of milestones met on time is Lantr's strongest argument, and it is why their name carries weight with me now.


NO

Cardano GovTool Budget - 12 months full active maintenance and development

Epoche573
Cast2025-07-31
Requested
OutcomeDROPPED

Following 4 weeks of active community consultation, the newly formed Cardano Govtool Consortium, made of all the community builders who actively develop the applications that make Govtool (ByronNetwork, WeDeliver, LidoNation and DQquadrant), those who use its code and APIs and individual contributors, proposes this Info Action to continue active maintenance and development of every application that makes GovTool itself, as the open-source community-owned set of tools built for public good, functioning as Cardano’s core interface for low-barrier participation in on-chain governance. As current funding concludes in June 2025, the new proposal outlines a leaner, more inclusive funding structure built to reflect community priorities. Over the past four weeks, substantial feedback was collected, through open forums, working groups, and direct contributions, by the community members participating in the Consortium. This feedback was carefully analyzed and embedded into a tiered proposal that balances operational stability, cost efficiency, and ecosystem-wide participation. The overall direction suggested by the community, considering the clear streamlined costs and the many options to contribute in its development, is to continue for the next 12 months to actively develop and evolve these tools, expanding further its open-source structure. With this Info Action, the Cardano Govtool Consortium aims to transparently share a revised direction and gauge broad community support. If positively received, it will enable the submission of a follow-up Treasury Withdrawal governance action to fund GovTool active development for the next 12 months.

Position history — changed votes are never hidden

ABSTAIN · epoch 571 · 2025-07-23 · tx 3a26781aa4dd180b

Written after the vote was cast

What this asks for, and from whom

The Cardano GovTool Budget for 12 months of active maintenance and development. This entry records an ABSTAIN that I later replaced with a NO.

What would have to be true for this to be a good use of treasury funds

GovTool would need usage numbers that justify a full year of active development funding. Governance tooling matters, and I do not dispute that ordinary holders need a working way to register, delegate, and vote.

What specifically concerns me

I abstained first because I did not want to be the Drep voting against governance tooling, which is an uncomfortable position to hold in public. Then I decided that abstaining to avoid discomfort is not a position, it is an evasion. Let's be real about it: if I think a proposal has not justified its size, the honest thing is to vote no and explain why, not to hide behind a neutral flag. Cardano's governance participation problem is not caused by missing features in the interface, and more development budget does not fix a demand problem.

What I am asking of the proposer if this passes

It was dropped, and I voted no again on the later withdrawal at epoch 584. What changes my vote is data: monthly active users, registrations completed, votes actually cast through the tool. Strong numbers and I will say so publicly and fund it.

Reasoning

Written after the vote was cast

What this asks for, and from whom

The Info Action for the Cardano GovTool Budget, 12 months of full active maintenance and development, from the newly formed GovTool Consortium.

What would have to be true for this to be a good use of treasury funds

The tooling that lets ordinary holders participate in governance has to work. I do not dispute that.

What specifically concerns me

Same objection as the withdrawal I voted no on at epoch 584, and I am consistent across both. A consortium assembling around a funding stream, asking for a full year of active development, without usage numbers that justify the scale. Cardano's governance participation problem is not a feature problem. Let's be real about it: people are not staying away from governance because the interface lacks polish, they are staying away because most of them do not believe their vote changes anything. More development budget does not touch that.

What I am asking of the proposer if this passes

It was dropped. Bring participation numbers. If GovTool usage is growing and the bottleneck is genuinely capacity, I will change my vote and say so publicly.


YES

Withdraw ₳199,911 for OpShin - Python Smart Contracts for Cardano

Epoche573
Cast2025-07-31
Requested200K ₳
OutcomeENACTED

This treasury withdrawal funds **OpShin - Python Smart Contracts for Cardano** which will provide the following services: This is OpShin: a toolchain that lets developers construct Cardano smart contracts in Python. The toolchain comprises several projects that aim to facilitate the development of Smart Contracts and dApps on Cardano. They are largely based on Python, or integrate well with it for maximal accessibility. On top of accessibility, OpShin ensures low transaction cost compared to PlutusTx. At the time of writing, Python is the second-most used language on GitHub, with 14.75% of the active userbase working with Python, and enjoys a 22.5% year-over-year increase in users; this is driven in part by its utility in data science and machine learning. Everyone who knows Python can leverage the toolstack available for Python development to build on Cardano; and that is a lot of people, with a lot of tools. OpShin enforces strict typing on the high-level programming: it implements a type system on top of Python type hints. However, all traces of typing are erased during compilation, for a maximum efficiency program. OpShin beats many programming languages when taken to the test for real use-cases. 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

199,911 ADA for OpShin, Python smart contracts for Cardano, administered by Intersect.

What would have to be true for this to be a good use of treasury funds

Python is one of the most widely known languages on earth. A working Python path onto Cardano lowers the barrier for an enormous pool of developers who will never learn Haskell.

What specifically concerns me

Very little at this size. Under 200,000 ADA to maintain a language on-ramp is the cheapest developer acquisition spending in the budget. My standing note applies: keep it maintained rather than letting it drift into abandonware after the grant ends.

What I am asking of the proposer if this passes

It was enacted. Report how many projects ship using OpShin. If a Python path brings teams who would otherwise have built elsewhere, that case makes itself every renewal.