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.
- No 1.1M ₳ No rationale
- No 1M ₳ Rationale
Dolos aims to provide a lightweight Cardano data node optimized for dApps, but the proposal lacks clear differentiation from existing solutions and fails to justify the ₳220k budget given its narrow scope. Without evidence of unique strategic value or critical ecosystem need, funding this risks duplicating efforts and misallocating treasury resources. Governance processes are sound, but substance is lacking.
For these reasons, I vote NO! Cardano’s treasury should focus on higher-impact, scalable solutions aligned with our long-term vision.
- Yes 1M ₳ No rationale
- Yes 955.2K ₳ No rationale
- Yes 947.9K ₳ No rationale
- Yes 922.9K ₳ No rationale
- Yes 860.4K ₳ No rationale
- Yes 819K ₳ No rationale
- Yes 818K ₳ No rationale
- Yes 810K ₳ No rationale
- Yes 793K ₳ No rationale
- Yes 785.2K ₳ No rationale
- Yes 733.1K ₳ No rationale
- Yes 717.1K ₳ No rationale
- Yes 716.6K ₳ No rationale
- Yes 655K ₳ No rationale
- Yes 654.5K ₳ No rationale
- Yes 624.8K ₳ 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. - Yes 589.2K ₳ No rationale
- Yes 587.1K ₳ Rationale
Access to reliable, low-latency blockchain data is critical for the success of decentralized applications in Cardano. Dolos fills a key infrastructure gap by offering a lightweight, resource-efficient Cardano data node purpose-built for developers who need to query the ledger without running full-node infrastructure. By reducing cost and complexity, Dolos democratizes backend access for small teams and experimental projects — helping dApps scale without overloading core network resources.
The proposal shows strong technical maturity and ecosystem alignment. Dolos is already open-source, actively maintained, and used in production by projects that value both speed and data integrity. With hundreds of commits and a growing contributor base, it represents a high-leverage, low-cost investment. Continued funding ensures it remains compatible with future protocol changes, and supports the ecosystem's push toward modular, decentralized infrastructure. I vote YES to support the continued evolution of this essential tool for dApp developers in the Cardano ecosystem.
- No 502K ₳ Rationale
TxPipe builds quality tools, but we already have a confusing array of node options. Developers regularly ask "which node should I use for what?" Adding another specialized implementation doesn't help that confusion, it makes it worse.
Focus on making the existing tools better and more accessible instead of proliferating options. - Yes 473.6K ₳ No rationale
- Yes 466.2K ₳ No rationale
- Yes 445.1K ₳ No rationale
- Yes 443.5K ₳ No rationale
- Yes 385.6K ₳ Rationale
Krypto Labs have taken part in the budget debates and agree with proposer that this is something the Cardano blockchain ecosystem need.
I started with making a rationale and arguement for each proposal, but to save time i need to do bulk voting to speed this prosess up. - No 382.6K ₳ No rationale
- Yes 377.3K ₳ No rationale
- Yes 328.9K ₳ No rationale
- Yes 321.1K ₳ No rationale
- Yes 314.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.
- Yes 313.1K ₳ Rationale
I’m voting YES to fund Dolos. This lightweight data node is important infrastructure for dApps, providing efficient access to Cardano ledger data with minimal resource requirements.
Supporting this proposal aligns with my DRep principles of sustaining essential tooling, enabling long-term ecosystem growth, and ensuring developers have reliable, optimized infrastructure to build scalable applications on Cardano.
- Yes 298.6K ₳ 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.
- Yes 295.2K ₳ No rationale
- Yes 271.5K ₳ No rationale
- Yes 262.3K ₳ No rationale
- Abstain 258.6K ₳ Rationale
📋 Evaluation Checklist
1️⃣ Ecosystem Essentiality → 🟡 Partial
Does the proposal address a critical function or unique capability within Cardano?
📌 Evidence:
“Dolos is a specialized Cardano data node designed to maintain an updated copy of the ledger and respond efficiently to queries.”
“Unlike a full Cardano node, Dolos is optimized for minimal resource usage while maintaining high data integrity and responsiveness.”📌 Analysis:
Dolos provides a technically valid solution that enables efficient, lightweight access to Cardano ledger data without requiring the full infrastructure of a full node. This capability is relevant for dApps and developers operating with constrained resources.
❗Critical note: While Dolos fills a valid technical niche as a lightweight data node, the proposal fails to provide any direct comparison or positioning relative to existing ecosystem solutions such as Ogmios, Kupo, UTxO-RPC, Koios, or Blockfrost.
This omission weakens the case for Dolos as a strategically essential or unique infrastructure component and makes it harder to assess the relative impact or necessity of funding this particular initiative at this time.
This omission of a comparative analysis of technical differentiators, architectural advantages, or user adoption suggests a lack of argumentative effort on the part of the proposer reduces clarity around the distinct value this proposal brings to the ecosystem and weakens the strategic justification for funding.
2️⃣ Budget Structure and Detail
✅ Yes
“0.5 FTE Blockchain Developer for 12 months = $99,412 = ₳165,686”
“0.125 FTE Tech Lead for 12 months = $33,137 = ₳55,228”The proposal provides a clear labor-based cost breakdown using daily rates and FTE percentages. The rate of $825/day for the developer and $1,100/day for the tech lead are slightly above market averages, but within reason for experienced Rust-based infrastructure work in the Web3 space.
No other cost categories (infrastructure, security, support, etc.) are included — all work is expected to be delivered via internal labor. There is no per-task hour allocation, but the transparency in rate calculations offsets this gap for a proposal of limited complexity.
3️⃣ KPIs or Impact Identifiers → 🟡 Partial
Are there QUANTIFIABLE impact metrics?
📌 Evidence:
“Dolos remains fully compatible with the latest Cardano releases.”
“Identified issues and bugs are addressed in a timely manner.”
“Performance and resource optimizations are implemented.”📌 Analysis:
The definition of success is based on qualitative criteria (compatibility, bug resolution, optimization), but there are no concrete numerical targets such as number of users, commit frequency, test coverage, or average node response time.
4️⃣ Milestones and Deliverables → 🟡 Partial
Does the proposal present a clear timeline with essential milestones and well-defined, verifiable deliverables?
📌 Evidence:
“All milestones, acceptance criteria, payment amounts and expected delivery dates will be agreed between the Vendor and Intersect, acting on behalf of the CDH.”
“The vendor will deliver according to the agreed-upon project schedule within the Legal Contract…”
“Acceptance of the above work is expected to be supported by a 3rd Party Assurer…”From the original proposal:
- Key Deliverables include maintenance, protocol updates, performance optimizations, and documentation.
- Definition of Done describes general conditions: continued compatibility with Cardano, timely bug fixes, consistent documentation and engagement.
📌 Analysis:
While the proposal outlines a delivery framework that includes a legal contract with milestones, acceptance criteria, and third-party review, it fails to provide this information at the time of voting.
There is no public timeline, no phased breakdown of deliverables, and no explicit conditions for milestone acceptance. The provided "Definition of Done" is entirely qualitative and lacks measurable targets or deadlines.This reliance on post-approval structuring undermines transparency and verifiability during the governance decision process, even if the formal infrastructure for delivery is described.
5️⃣ Internal Consistency
✅ Yes
All details (amount requested, metadata, description) are internally consistent and match the budget Info Action from which this withdrawal is sourced.
6️⃣ Team Visibility & Track Record
🟡 Partial
“TxPipe has helped develop several dApps… successfully completed several Catalyst proposals… participated in Partnerchain SDK…”
TxPipe has a strong technical reputation in Cardano. However, they are currently managing 8 active Catalyst proposals, most of which are delayed by weeks to months. This indicates possible overextension and unacknowledged bandwidth risk. The proposal does not disclose these commitments, nor does it offer any mitigation plan or delivery prioritization.
7️⃣ Conflict of Interest
✅ No Conflict
No material or financial conflict identified. I have no professional or financial ties to TxPipe or Intersect.
🧠 Critical Summary
The proposal requests ₳220,914 to sustain development and maintenance of Dolos, a lightweight Cardano data node designed to provide efficient, low-resource access to ledger data. Its core function is relevant, and its low-infrastructure footprint offers a valuable option for developers and dApps seeking alternatives to full node setups or centralized APIs.
However, the proposal fails to articulate how Dolos meaningfully differentiates itself from existing ecosystem tools such as Ogmios, Kupo, UTxO-RPC, Koios, or Blockfrost. This lack of comparative analysis undermines the case for strategic necessity and leaves its ecosystem impact uncertain.
While the cost structure is reasonable and clearly calculated, the absence of concrete KPIs, public milestones, and explicit acceptance criteria reduces overall transparency. The proposal leans heavily on post-approval contractual structuring, which limits pre-vote accountability.
Additionally, the team’s current delivery capacity is in question: TxPipe is managing multiple ongoing Catalyst-funded projects, most of which are delayed. This operational risk is not addressed in the proposal.
🗳 Final Recommendation: 🟡 ABSTAIN
While Dolos may provide technical value, the proposal lacks critical comparative positioning, measurable impact indicators, and delivery assurances.
The absence of clear differentiators and the team’s current delivery load introduce too much uncertainty for a confident YES, while the legal structure and open-source history mitigate grounds for a firm NO.
I am abstaining due to insufficient evidence of urgency or uniqueness to justify this Treasury Withdrawal at this time. - Yes 257K ₳ Rationale
I vote YES on the Dolos Treasury Withdrawal proposal.
Dolos fulfills a critical need by providing efficient, lightweight ledger data access essential for Cardano dApps’ scalability and ecosystem usability. TxPipe has a robust track record with open governance, transparent milestone reporting, and community contributions. The proposal complies with all constitutional guardrails regarding budget size, administration, and transparency, with multi-sig oversight and public audits. The requested funding aligns with deliverables and supports Cardano’s long-term developer infrastructure. This investment is both prudent and strategically aligned with Cardano’s growth objectives.
- Yes 252.6K ₳ No rationale
- Yes 245K ₳ No rationale
- Yes 238.6K ₳ No rationale
- Yes 208.6K ₳ Rationale
I vote in favor of the Dolos proposal, despite viewing it as a niche use case, as it addresses a critical need for lightweight ledger access among Cardano dApp developers. While its specialized focus on efficient data queries may not benefit all projects, Dolos’s open-source model and growing adoption (366 commits, 21 contributors) align with Cardano’s push for developer accessibility and scalability. TxPipe’s proven track record and the modest funding request for 0.625 FTE roles mitigate concerns about its narrow scope. Supporting Dolos ensures a robust tool for dApps, but clearer adoption metrics would strengthen its case for broader ecosystem impact.
- Yes 206.4K ₳ No rationale
- Yes 190.2K ₳ No rationale
- Yes 184.4K ₳ 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.
- Yes 180.9K ₳ No rationale
- No 177.6K ₳ No rationale
- Yes 143.9K ₳ No rationale
- Yes 137.3K ₳ No rationale
- Yes 131.6K ₳ No rationale