Withdraw ₳657,692 for Scalus - DApps Development Platform
152 DReps voted · 47 with a rationale · 5 changed their vote
Open a row to read the rationale.
- Yes717.5K ₳No rationale
- Yes705.1K ₳No rationale
- Yes625.9K ₳Rationale
I have voted in favor of this action to demonstrates my intention to execute without delays and move the treasury expenditure process forward. I also want to note that I will not seriously consider individual requests from the treasury for less that 1,500,000 ADA moving forward. I reserve the right this round because I feel the process was not properly explained to proposers and DRep and it would be unfair to implement this personal guardrail at this time. Requests below that threshold are better suited for Catalyst funding or bundled together in MBO, DAO, or conglomerate entities. TWA (Treasury Withdrawal Actions) need be comprehensive and not ad hoc as that makes oversight more costly and inefficient.
A budget and all included line items has already been approved, and now is the time to disperse funding and enable further development of the Cardano network. The proposal was selected through a well-defined process, and I will fully support it out of respect for the will of the broader Cardano community and a belief in respecting the consensus we achieved together under the Intersect-administered budget process. The process reflects a coordinated, strategic approach to funding Cardano’s ecosystem-critical infrastructure. The community has thoroughly reviewed the proposal. I was actively involved in the entire process and the proposal presented represents development that provides a tangible benefit to our ecosystem. It would be a mistake to underfund our ecosystem’s development when we can sustainably provide the required funding with our available treasury reserves.
Furthermore there are exceptional oversight mechanisms in place to ensure a minimum amount of wast, fraud, and abuse of treasury expenditures, such as Intersect’s smart contract framework (audited by TxPipe and MLabs), Multi-party oversight (including Cardano Foundation, Sundae Labs, NMKR, etc.), A clear milestone-driven disbursement model, and full transparency via TRSC/PSSC dashboards.
These governance and assurance systems meet the constitutional standards for accountability and risk management and provide confidence in efficiency and execution. - Yes605.7K ₳No rationale
- Yes589.7K ₳No rationale
- Yes587.6K ₳Rationale
This proposal for Scalus — a Scala 3 based DApps development platform — offers a significant step forward in simplifying Cardano smart contract and DApp development. By enabling developers to use a single, powerful language and ecosystem, it lowers the technical barriers and accelerates time-to-market. This is especially important for onboarding Web2 developers proficient in Scala, Java, and Kotlin, a large talent pool that can now more easily transition to Cardano development.
Importantly, Scalus aligns closely with existing efforts like the Bloxbean Java library, creating synergies that benefit both projects and the wider Java/Scala developer community in Cardano. This alignment fosters interoperability and shared growth of tooling that improves developer experience and ecosystem maturity.
Supporting Scalus means investing in a practical, scalable, and professional-grade toolset that will drive broader adoption, improve code quality, and reduce training costs for businesses. Given the vendor’s strong background and expertise in functional programming and Cardano’s core technologies, this project is well-positioned to deliver long-term value to the community.
For these reasons, I support this proposal as a critical enabler of Cardano’s developer ecosystem expansion and innovation. - Yes466.2K ₳No rationale
- Yes442.9K ₳No rationale
- No383K ₳No rationale
- Yes381.1K ₳No rationale
- Yes328.9K ₳No rationale
- Yes314.4K ₳Rationale
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
- Yes298.9K ₳Rationale
I'm defaulting to voting yes because there is some degree of consensus already achieved on each of these. So unless I have a significant issue with one of these proposals I will be voting yes on it.
- Yes271.8K ₳No rationale
- Yes270.1K ₳Rationale
I vote YES to the treasury withdrawal proposal for ₳657,692 in support of the Scalus DApps Development Platform.
This platform aims to streamline and unify the Cardano smart contract and DApp development experience through Scala 3, offering a consistent tooling ecosystem that covers the full development lifecycle—from setup to deployment.
Given the steep learning curve and fragmented toolsets currently discouraging developer onboarding, Scalus addresses a significant bottleneck by bridging traditional Scala/Java/Kotlin developer expertise with the Cardano ecosystem’s needs. Such unification has the potential to reduce time-to-market, improve code safety, and tap into a wider talent pool — all critical factors for Cardano's scaling and enterprise adoption goals.
The vendor brings relevant domain expertise as a former IOG engineer familiar with Cardano’s FP and blockchain ecosystem, enhancing confidence in delivery. The proposal includes a well-defined contractual plan with milestones, third-party milestone acceptance, and robust governance and treasury oversight, ensuring risk is managed and accountability ensured.
The budget aligns reasonably with the scope of work for betting on a scalable development platform aimed at improving ecosystem inclusivity and productivity. Transparency measures and governance compliance are fully in place.
Approval will support expanding Cardano’s developer base through a production-ready, unified development platform designed for professional and business teams, thus fostering innovation and adoption.
- Yes262.6K ₳No rationale
- Abstain261K ₳Rationale
This vote was submitted based on a completed checklist. A detailed rationale is available at:
👉 https://github.com/Agora-Cardano - Yes252.9K ₳No rationale
- No245.5K ₳No rationale
- No238.8K ₳Rationale
Respectfully, while the intent to streamline DApp development and attract Web2 developers is noted, I believe this initiative does not align with the Cardano ecosystem’s current priorities and represents an inefficient use of resources. The allocation of 650,000 ADA is substantial, particularly for a platform built on Scala, a niche programming language with limited adoption compared to more established alternatives like Haskell or even Python. Scala’s relatively small developer base and perceived complexity may not justify the investment, especially when Cardano’s existing tools, such as Plutus, already provide robust, battle-tested solutions for smart contract development. Lowering the technical barrier to attract web developers risks diluting the ecosystem’s focus on high-quality, secure, and specialized development practices, which are critical for Cardano’s mission-critical applications.
- Yes238.6K ₳No rationale
- Yes208.3K ₳No rationale
- Yes191.1K ₳No rationale
- Yes185.6K ₳Rationale
I am voting yes on all 39 Intersect Governance actions. The community has thoroughly reviewed the many proposals presented in the Intersect Budget Process for the 2025 budget. I was deeply involved in the entire process as an SME for the Budget Committee, and then as the Secretary for the Budget Committee.
The proposals presented represent an incredible amount of development for our ecosystem for the next year. The teams all received at least 50% on Ekklesia polling. The teams will face milestones in order to continue to receive funding. If a team fails to deliver, the process will stop them from enriching themselves without returning value.
If anything, we are spending too little on our community. We need to spend more to further develop our governance and our organized events. This is a liquid democracy. If you believe that all of these proposals deserve a chance to deliver, you can shift your delegation to my DRep ID.
- Yes178.9K ₳No rationale
- NoRevoted147.5K ₳History
Earlier votes
No11mo agoSuperseded
- Yes137.4K ₳No rationale
- Yes133.7K ₳No rationale
- Yes110.9K ₳No rationale
- Yes108.3K ₳Rationale
I am voting in favor of approving the treasury withdrawal for all 39 withdrawal actions that are part of the approved ecosystem budget administered by Intersect. I am voting this way for several reasons, as I will outline here. This rationale will be included in all 39 withdrawal votes.
First and foremost, I believe that we would be making a mistake in underfunding our community with our available treasury funds. The budget system as it currently stands has some flaws, as should be expected from a first version of any system. Of the current proposals, I voted to include several in the budget when it was being formed; however, I also did not vote in favor of several others. This is, of course, the case for most DReps. If I were to vote only for the proposals I initially favoured, and all other DReps did the same, we would likely approve only 2 or 3 proposals out of 39 due to the vote split. In my view, this is not an acceptable outcome for the community, and this is why I was also opposed to the idea of having 39 separate treasury withdrawal actions. I have reviewed all 39 requests, and they all have merit. Are they exactly in line with the priorities I wanted as part of the initial budget? No. Is that reason enough to vote no on several of these and end up approving only 2 or 3 proposals in the end? I certainly don't believe so.
In addition to this, the total amount of the intersect budget is roughly 10% higher than what I voted for, and I find that to be within an acceptable margin to approve all the withdrawals.
The individual proposals also all received at least 50% community approval to be included and will be subject to reviews and milestones to receive funds.
For these reasons, I am casting my vote to approve and am wishing the best of luck to all the teams waiting for funding through this process. - Yes103.1K ₳No rationale
- Yes92.6K ₳No rationale
- Yes68.8K ₳Rationale
- No65.7K ₳No rationale
- Yes58.6K ₳No rationale
- No55.9K ₳No rationale
- No50.5K ₳No rationale
- Yes48.6K ₳No rationale
- Yes46.5K ₳No rationale
- Yes45.2K ₳No rationale
- Yes36.3K ₳No rationale
- Yes36.3K ₳Rationale
✅ Voted YES on Scalus – Cardano DApp Development in Scala 3
🛠️ Why I support it:
• Lowers the barrier for developers by using Scala — a modern, safe, and powerful language
• Enables end-to-end DApp development (contracts, transactions, apps) all in one toolchain
• Unlocks access to a deep talent pool of Scala/Java/Kotlin developers
• Fast-tracks Cardano’s readiness for Web2 firms and fintech adoption
• Built by Oleksandr Nemish, former IOG engineer and Marlowe contributorScalus brings professional-grade tools, dev ergonomics, and a rich ecosystem to Cardano — paving the way for faster, safer, and more scalable DApp development.
Track all my votes 👉 https://tempo.vote/drep-profile
DRep: DeepStatecraft - No14.3K ₳No rationale
- Yes6.7K ₳No rationale
- Yes4.8K ₳No rationale
- Yes1.6K ₳No rationale
- Yes335.3 ₳No rationale
- Yes13.5 ₳No rationale
- No0 ₳No rationale
- Yes0 ₳No rationale