Withdraw ₳220,914 for Dolos: Sustaining a Lightweight Cardano Data Node
177 DReps voted · 50 with a rationale
Open a row to read the rationale.
- Yes 8.8M ₳ Rationale
「275M ADA Administered by Intersect」に含まれるすべての個別提案に対して、エクレシア投票の段階では必ずしもすべてに賛成していたわけではありませんが、最終的には本ガバナンスアクションに賛成票を投じました。Cardanoエコシステム全体への貢献を高く評価し、その前進を後押しする立場から、今回提出された39件すべての提案に賛成票を投じる判断をいたしました。\n\nWhile I did not necessarily support every individual proposal included in "275M ADA Administered by Intersect" during the Ekklesia vote, I ultimately voted Yes on this governance action. Recognizing its overall contribution to the Cardano ecosystem and in support of continued progress, I cast a Yes vote on all 39 proposals submitted under this initiative.
- Yes 8.1M ₳ No rationale
- Yes 7.8M ₳ No rationale
- Yes 7.3M ₳ No rationale
- Yes 7.1M ₳ Rationale
I voted YES for this proposal in the Ekklesia temperature check. I have now come to a position where I think that this might not be the best way forward. Meaning that direct funding of smaller open source maintenance and enhancement proposals from the treasury might not be the best approach going forward.
As I have already indicated my support for this proposal in Ekklesia, I will not overcomplicate matters by changing my vote at this - the final treasury withdrawal stage. So my original vote indication remains in place and I vote YES. Note: if this were to be resubmitted in 2026, I would consider this carefully.
Why? I am more in favor of seeing proposals like this funded through an initiative such as the OSC Budget Proposal - Paid Open Source Model for Sustainable Development. I voted YES for the OSC Budget Proposal - Paid Open Source Model for Sustainable Development.
Such budgetary initiatives do not have to come from the OSC, it could be another umbrella group of open source advocates / body that will prioritize and correctly value certain critical packages of maintenance and enhancement work on open source tools that are important for the Cardano ecosystem.
This group or groups would ideally rank the importance / relevance of these open-source tools and software kits or platforms, as well as realistically estimate how much maintenance / enhancement is needed and when it is critical.
Multiple tiny contracts approved by the treasury complicate oversight, whereas larger open-source infrastructure umbrella programs can rank repos by impact and rotate funding annually. The more exceptions the Treasury grants, the harder it becomes to enforce future budget discipline.
I imagine the maintenance and improvement of open source tools or platforms as something that could be tentatively grouped. Of course, these larger maintenance and enhancement support groups (like the OSC) for open source tooling could start discriminating against certain tools. In those cases, if a proposer is dissatisfied with the ranking or grouping, they could always directly apply to the Treasury with a rationale why the proposal needs funding and why it cannot obtain it elsewhere - but only directly from the Treasury.
Note: some other similar open source maintenance and enhancement proposals might differ in their perceived importance - and my vote indication in Ekklesia. I am currently considering to mostly mirror my voting indications from Ekklesia - in order to not overcomplicate the process. Exceptions will be indicated. - Yes 6.2M ₳ No rationale
- No 6M ₳ Rationale
Voting decision was made to be consistent with my reconciliation back in May 2025;
https://2025budget.intersectmbo.org/voters/drep1yfdfs28uwafjgmrkatdektlzrvha2cmvqjhuz700e04mawq23rmrgReady to move forward overall with the budgeting process and look forward to a smoother process next year. I voted for a lower NCL overall (200M), however found in supporting things that we really ought to have funded to keep momentum in development and enhancements on-chain (supporting both open and non-open-sourced projects) I came a bit higher than that (250M+).
We will need to strike a balance in treasury withdrawels for projects that push development forward (and therefore the chains efficiency, performance, resiliancy, and security) -- and businsess that wish to participate, of any size, and extend the capabilities and real-world use cases of Cardano.
My votes, I hope, align with my overall goal as a DRep to see continuous improvement in the ecosystem. https://raw.githubusercontent.com/Tarrant64/mr_cata_gov/refs/heads/main/mr_cata_gov%20.txt
- Yes 5.5M ₳ No rationale
- Yes 5.3M ₳ No rationale
- Yes 5.3M ₳ Rationale
Dolos offers a lightweight and reliable alternative for accessing Cardano ledger data, solving a clear pain point for developers without requiring full-node infrastructure. TxPipe has proven capable of delivering and maintaining critical tooling, and the ask is reasonable for the defined FTEs. This proposal supports STORM Partners’ objective to enhance ecosystem efficiency and usability through well-maintained public goods, justifying a YES vote.
- Yes 4.8M ₳ Rationale
Light data only node implementation makes dapp development extremely light. This level of dev ex will drive the Cardano dapp ecosystem.
Light data only node implementation makes dapp development extremely light. This level of dev ex will drive the Cardano dapp ecosystem.
- Yes 4.8M ₳ No rationale
- Yes 4.6M ₳ No rationale
- Yes 4.6M ₳ No rationale
- Yes 4.5M ₳ No rationale
- Yes 4.4M ₳ No rationale
- Yes 4.2M ₳ No rationale
- Yes 4.2M ₳ Rationale
I vote YES as core engineering is a top priority of my DRep.
Strength and honor.
- Yes 4M ₳ No rationale
- Yes 3.8M ₳ Rationale
Voting Rationale for 2025-08 Treasury Withdrawals
The following outlines the general lenses and beliefs that guided my voting decisions on the 39 withdrawal proposals submitted under Cardano’s Voltaire governance. I am reusing this rationale for proposals that aligned with these principles and did not require additional explanation due to unique mitigating concerns.
⸻
Cardano: State of Play
The vision of the Cardano ecosystem—to create a fairer financial system, less subject to the whims of individuals, elites, nations, or cultures—remains worthy of support. In general, we are progressing toward that goal.
The bedrock tenet of any blockchain is trustworthiness. While Cardano’s base layer and transaction integrity are mature, the ecosystem has not yet reached the scale needed to fulfill its mission. Infrastructure that supports scaling—especially when open-sourced—should be prioritized for funding.
Because the ecosystem currently allows for anonymity and lacks effective mechanisms to penalize bad actors, it is vulnerable to abuse. Public funding is at risk from fraud, budget inflation, frivolous proposals, and well-intentioned but economically unviable ideas. Given that grift is currently viable, all funding requests must be critically reviewed—with a strong default bias toward skepticism.
However, in any new system, failure and error are expected. The many problems we’ve seen in this first funding cycle are normal and should be treated as feedback to help us improve, not as reasons to disengage.
⸻
Fiscal Philosophy
I view the Cardano treasury as a sovereign wealth fund—a public resource meant to grow over the long term. Spending should be closely aligned with income.
Most projects should ultimately sustain themselves by generating revenue commensurate with their value. But Cardano is still an immature economic system, and many valuable contributions will require public funding at this stage—analogous to early government support for foundational infrastructure.
⸻
Approach to the Budget Process
This first Voltaire budget cycle has experienced serious growing pains. I do not believe that builders should be asked to shoulder the full financial risk of an immature, unclear, and delayed funding process.
Many proposers have worked through most of 2025 without knowing whether their funding would come through. This has impaired their ability to allocate resources intelligently.
I believe the greater ecosystem risk lies in failing to fund projects that were already approved by the community—under the reasonable assumption that funding would follow—than in inadvertently funding a few proposals that should have been rejected. Accordingly, I adopted a bias toward optimism and benefit of the doubt.
However, in cases where proposals appeared excessively extractive, failed to demonstrate economic value in line with their requests, or raised too many concern flags, I voted “no” despite that bias.
⸻
Bias Toward Core Infrastructure and Open-Source
Cardano is first and foremost an infrastructure system. Public funding is best directed toward foundational layers and tooling, rather than toward products that should be able to find product-market fit and attract users or investors.
Public money should come with public return—either in the form of open-sourced outputs or equity-like participation in future value creation.
⸻
Additional Beliefs and Disclosures
I believe in the wisdom of crowds. My votes are based on independent reading of the proposals, personal communications with teams, and my own biases and interpretations. I assume some of my conclusions are incorrect—but trust that the collective judgment of voters will yield a generally sound outcome despite individual errors.
I voted in good faith and without compensation. I have no proposals of my own and no financial interest in any proposal beyond that of any other ADA holder.
- Yes 3.7M ₳ Rationale
This proposal offers a valuable open-source, lightweight data node developed by a skilled team, enabling diverse applications for developers within the Cardano ecosystem. I support it for its potential to enhance accessibility and efficiency.
- Yes 3.7M ₳ No rationale
- Yes 3.5M ₳ No rationale
- Yes 3M ₳ No rationale
- Yes 2.8M ₳ Rationale
I am following through with my YES vote from the Cardano Budget 2025 Ekklesia process. This proposal falls within my personal NCL of 250,000,000 ADA.
- Yes 2.7M ₳ No rationale
- Yes 2.7M ₳ Rationale
A couple of months ago, I supported the resolution to bundle all of the Intersect Budget Proposals into 1 or 2 formal on-chain governance votes.
Each of these proposals has already received 50% or greater support from the active DReps in the ecosystem, and I will honor that prior decision.
A PDF version of this rationale is also made available.
A couple of months ago, I supported the resolution to bundle all of the Intersect Budget Proposals into 1 or 2 formal on-chain governance votes.
Each of these proposals has already undergone extensive scrutiny and received 50% or greater support from the active DReps in the ecosystem, and I will honor that prior decision and the work these prospective developers have put in by voting yes on all the proposals from the Intersect Budget team.
- Yes 2.6M ₳ Rationale
I'm not sure I’ll end up using this, but competition is always a good thing for the end user in the long run, as it drives progress.
- Yes 2.5M ₳ No rationale
- Yes 2.5M ₳ Rationale
As a dev, I selfishly want this.
- Yes 2.5M ₳ Rationale
Dolosは、フルノードと比べて軽量かつ高速なデータ取得を可能にする専用ノードとして、dApp開発者にとって有用な代替手段を提供しています。実装済みのOSSプロジェクトとして実績があり、今後の保守・最適化・機能追加に対する支援として適切な金額規模であるため、賛成します。
Dolos offers a lightweight, efficient data node alternative for dApp backends in Cardano. It’s actively maintained, open-source, and has real-world usage. Supporting its continued development at this modest cost enhances developer tooling. I vote in favor.
- Yes 2.5M ₳ Rationale
I believe this proposal provides good value and makes sense from an FTE perspective.
- Yes 2.4M ₳ No rationale
- Yes 2.1M ₳ No rationale
- Yes 2.1M ₳ No rationale
- Yes 2.1M ₳ No rationale
- Yes 1.9M ₳ No rationale
- Yes 1.9M ₳ No rationale
- Yes 1.8M ₳ Rationale
Voting Yes to fund Dolos maintenance. TxPipe is a proven, active Cardano dev team delivering key tools. Dolos provides quick and efficient access to blockchain data, enabling dApps to operate without the resource demands of a full node. This funding keeps it reliable and optimised.
- No 1.8M ₳ Rationale
I am voting No. This proposal adds to an already fragmented landscape of node implementations without clearly articulating how it uniquely serves the ecosystem. Developers already face confusion about which node to use, and introducing another specialized option risks further fragmentation. The narrow scope and lack of clear differentiation do not justify the ₳220k ask, especially when this kind of focused development would be more appropriately funded through Project Catalyst. The Treasury should prioritize high-impact, scalable infrastructure with clear ecosystem alignment—this proposal does not meet that bar.
- Yes 1.7M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.7M ₳ No rationale
- Yes 1.5M ₳ No rationale
- Yes 1.4M ₳ No rationale
- Yes 1.4M ₳ No rationale
- Yes 1.2M ₳ No rationale
- Yes 1.2M ₳ Rationale
I decided to vote ✅ YES on 37 treasury withdrawals, ➖ ABSTAIN on none, and ❌ NO on 2 treasury withdrawals from the Intersect 2025 budget.
It’s obvious I consider all proposals I approved in the budget vote on Ekklesia beneficial for Cardano, so those all receive a ✅ YES vote.
I also vote ✅ YES for most proposals I initially abstained from or voted against in the Ekklesia vote. There are a few reasons for this:
- Some proposals gained strong community support after all, so I don’t want to be the one standing in the way, especially when the requested amount is negligible in the bigger picture.
- Some proposals I actually liked, but I found them more suitable for Catalyst. However, with all the delays, it now makes more sense to fund them as soon as possible.
- Some didn’t get my initial support because I thought the requested amount was too high. But I now believe it’s better for the ecosystem to fund them, despite the larger budget, than not fund them at all.
- I needed to vote for budget proposals with my own NCL in mind. Not all those I approved made it, however, so that leaves some room for other ones.
I won’t approve the treasury withdrawal for two proposals:
❌ Withdraw ₳3,000,000 for High-yield RWA Asset for Cardano: Tokenized Real Estate
This proposal won’t bring much value to our ecosystem, imho.❌ Withdraw ₳1,500,000 for Complement Catalyst: Extended Quadratic Funding---Zero Operational Costs
While the proposal includes some interesting ideas for a fairer voting mechanism, I now support Catalyst and don’t see the need for an additional funding system at this moment, especially considering total spending. The requested amount also seems too small to meaningfully fund multiple projects. While the model relies on donations, it’s unclear what the donor incentive is. Since voting power is tied to donation size, why wouldn’t donors just support specific fundraisers run directly by the projects they care about? That way, they can ensure their contribution goes straight to their preferred initiative without needing it to win a vote first.
I do appreciate the idea of a hybrid funding model where the treasury covers part of a project, but ideally, the remaining portion should come from investors rather than donations, imho.
Lastly, I don’t appreciate that the proposal’s title refers to Catalyst, even though it has no relationship to it. This seems intended to mislead people into thinking Catalyst would benefit from this proposal, which it doesn’t...I acknowledge there’s a metadata issue in the proposal “Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix”, but I approved it nonetheless, as the problem is minor and not worth obstructing the process.
- Yes 1.1M ₳ No rationale