Withdraw ₳99,600 for BloxBean Java Tools Maintenance and Enhancement
158 DReps voted · 46 with a rationale · 2 changed their vote
Open a row to read the rationale.
- Yes763.4K ₳No rationale
- Yes759K ₳No 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 consider individual requests from the treasury for less that 100,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 guardrail at this time. Requests below that threshold are better suited for Catalyst funding.
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. - No605.7K ₳No rationale
- Yes589.7K ₳No rationale
- Yes587.6K ₳Rationale
I support this proposal. BloxBean is essential for Java-based development on Cardano. Funding it enables wider adoption by Web2 developers, ensures ongoing maintenance, and supports projects like GovCircle that rely on it. The requested amount is modest for its impact.
A PDF version of this rationale is also made available.
As a software engineer with over a decade of experience in the Java ecosystem—particularly in developing enterprise applications using Java and the Spring framework—I strongly recognize the strategic importance of BloxBean in the Cardano ecosystem.
In our GovCircle project, we actively use several of BloxBean's tools, especially Yaci and related libraries. Our hands-on experience has shown us that BloxBean has created one of the most practical, developer-friendly, and open-source SDKs available for building on Cardano. It significantly reduces the complexity for Java developers entering the ecosystem and covers many of the essential components needed to interact with Cardano infrastructure.
However, as it currently stands, BloxBean is being maintained by a small team. The tools need further development, improved documentation, and broader support to meet the growing needs of the community. The requested funding will allow the team to onboard another full-time developer, which is essential for scaling the tools, addressing developer feedback, and engaging the wider Java community.
Supporting this proposal is not just a matter of maintaining existing tools—it’s a strategic investment in onboarding Java developers from Web2 into Web3, especially into the Cardano ecosystem. Considering the massive Java developer base globally, enhancing BloxBean could play a critical role in Cardano adoption.
I also want to highlight that the requested amount (₳99,600) is modest when compared to similar SDK/library initiatives in other programming languages. It's a cost-effective proposal with a high impact-to-cost ratio.
Lastly, I encourage my fellow DReps to vote in favor of this proposal. Not supporting BloxBean risks breaking the development pipelines of projects that rely on it—including ours. Strengthening this foundation will benefit the entire Cardano ecosystem by enabling broader, enterprise-level developer engagement.
Let’s invest wisely in the tools that can bring more builders to Cardano.
- Yes479.9K ₳No rationale
- Yes466.2K ₳No rationale
- Yes442.9K ₳No rationale
- Abstain385.2K ₳Rationale
As DRep for Krypto Labs I abstain from voting on the BloxBean Java Tools proposal requesting ₳99,600 for maintenance and enhancements. While these open source tools like CCL and Yaci are vital for Java developers and ecosystem growth, uncertainties in funding allocation and ROI prevent a clear stance.
Similarly, I abstain on Anzens' Stablecoin Expansion , seeking ₳4,000,000 for custody, liquidity, and fiat ramps. The initiative promises DeFi and real-world utility via USDA, backed by experienced teams, but budget details and sustainability concerns warrant neutrality and need votes by experts on this.
- No383K ₳No rationale
- No381.1K ₳No rationale
- Yes370.3K ₳No rationale
- Yes365.7K ₳No rationale
- Abstain314.4K ₳Rationale
In alignment with my voting during the 2025 Cardano Budget Reconciliation process on the Ekklesia platform, I abstain from this vote.
In alignment with my voting during the 2025 Cardano Budget Reconciliation process on the Ekklesia platform, I abstain from this vote.
- 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
After a thorough review of the “Withdraw ₳99,600 for BloxBean Java Tools Maintenance and Enhancement” proposal, I am confident this is a strategically important initiative that directly supports the stability, usability, and growth of the Cardano ecosystem.
BloxBean’s Java tooling is a critical part of the developer infrastructure, widely used by Cardano developers, explorers, and enterprise integrations. Maintaining and enhancing these tools ensures Cardano has a robust, production-ready set of Java libraries and developer kits that improve integration, adoption, and interoperability.
Key reasons to support this proposal include:
Alignment with Cardano Roadmap:
This maintenance work supports ongoing ecosystem development goals by improving tool reliability and compatibility with the evolving Cardano protocol and node upgrades.Ecosystem Impact:
Reliable Java tooling reduces barriers for developers and enterprises building on Cardano, facilitating faster development cycles and enabling more sophisticated applications.Demonstrated Track Record:
BloxBean has a proven history of commitment and contributions to Cardano’s development stack, indicating competence and reliability.Reasonable Funding:
The requested amount (~₳99,600) is proportionate for the scope of ongoing maintenance and targeted enhancements, representing good value for sustaining essential infrastructure.Transparent Oversight:
The proposal includes milestone-based funding releases with delivery assurance and public reporting, ensuring accountability and effective use of funds.Overall, this proposal is a sound investment in Cardano’s developer ecosystem, promoting a robust and accessible toolchain that benefits developers, projects, and the wider adoption of the platform. I vote YES to approve the disbursement.
- Yes262.6K ₳No rationale
- Abstain261K ₳No rationale
- Yes252.9K ₳No rationale
- No245.5K ₳No rationale
- Yes238.8K ₳Rationale
The BloxBean Java Tools proposal offers excellent ROI due to its low cost (99,000 ADA ≈ $44,550) and high potential to enhance Cardano’s developer ecosystem. The tools (CCL, Yaci, Yaci Store, Yaci DevKit) are critical for Java, Scala, and Kotlin developers, directly supporting Android DApp development by enabling transaction handling, blockchain data retrieval, indexing, and local testing. These capabilities make it easier to build mobile wallets, DeFi apps, or NFT platforms on Android, tapping into a vast developer community. The proposal’s alignment with Cardano’s goals, BloxBean’s credibility, and robust governance via Intersect justify a “yay” vote. My hope is that this proposal provides cost-effective, high-impact support for developers, particularly for Android DApps, fostering ecosystem growth and innovation.
- No238.6K ₳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
- No147.5K ₳No rationale
- Yes138.4K ₳No rationale
- 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
- No69.4K ₳No rationale
- Yes68.8K ₳Rationale
- Yes65.7K ₳No rationale
- Yes58.6K ₳No rationale
- Yes55.9K ₳No rationale
- No50.5K ₳No rationale
- No48.6K ₳No rationale
- Yes46.5K ₳Rationale
I voted YES on all 39 Governance Actions — 39 times, 39 votes.
Since I supported these during Ekklesia and saw no major changes or conflicts of interest, I stand by those decisions now. For proposals with large budgets, I paid extra attention to the justification and scope. Voting isn’t just a click — it’s a responsibility. I own mine, for myself and for our CASIA community.
- No45.2K ₳No rationale
- Yes36.3K ₳Rationale
✅ BloxBean Java Tools Maintenance & Enhancement (₳99.6K)
• Supports CCL, Yaci, Yaci Store, and DevKit — foundational Java tools for interacting with Cardano.
• Adds a full-time developer to maintain compatibility with network upgrades, fix bugs, and deliver new features.
• Enhances developer documentation, tooling, and community support, making Cardano more accessible to JVM developers.
• Maintains a robust Java stack as open-source infrastructure, accelerating ecosystem growth beyond Plutus/Haskell.🧩 My take: BloxBean plays a vital role in broadening Cardano’s developer reach. Their tools are mature, battle-tested, and needed. YES to sustained support.
- No14.3K ₳No rationale
- Yes6.7K ₳No rationale
- Yes4.8K ₳No rationale