Withdraw ₳220,914 for Dolos: Sustaining a Lightweight Cardano Data Node
177 DReps voted · 57 with a rationale · 1 changed their vote · 2 re-voted unchanged
Open a row to read the rationale.
Changed votes: 1 to yes, together voting with 9.4M ₳ of voting power.
- Abstain90.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. - Yes83.9K ₳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. - No77.2K ₳No rationale
- Yes65.9K ₳No rationale
- Yes63.1K ₳No rationale
- Yes58.7K ₳No rationale
- Yes56.1K ₳No rationale
- Yes51.8K ₳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.
- Yes48.7K ₳No rationale
- Yes48K ₳No rationale
- Abstain45.3K ₳No rationale
- Yes36.9K ₳No rationale
- Yes36.4K ₳Rationale
✅ Vote: YES on Dolos — Lightweight Cardano Data Node Maintenance
I’m voting YES to continue funding Dolos, an open-source lightweight Cardano data node developed by @txpipe.
🔍 What is Dolos?
A minimal-resource backend node that syncs the Cardano ledger and responds to trusted queries — ideal for dApps, dashboards, and services that don’t require a full node. It’s fast, reliable, and low-footprint.🛠️ Why it matters:
• Maintains an updated ledger copy with minimal infrastructure
• Used by devs who want fast access to on-chain data
• Avoids centralization by removing the need to depend on hosted full-node APIs
• Already seeing real adoption: [366 commits, 367 PRs, 21 contributors]💡 Sustained funding = continuous compatibility, optimization, and community support. This vote ensures:
• 0.5 FTE Blockchain Dev
• 0.125 FTE Tech Lead
• Open development with transparent milestones
• Delivery tracked via smart contracts with 3rd-party assurance🔗 Proposal on Ekklesia
🔗 TxPipe Dolos GitHub
🔗 GovTool Info Action📦 Funded via Intersect’s 2025 budget process using the new Treasury Smart Contract system for secure, auditable delivery.
#Cardano #OpenGov #Governance #Dolos #TxPipe #LightweightNode #VoteYES #Intersect #dAppInfra
- No26.7K ₳Rationale
Again, TxPipe has only like a 50% completion rate via Catalyst proposals. They should fix those things before doing something like this.
- No14.3K ₳No rationale
- Yes6.8K ₳No rationale
- Yes5.7K ₳No rationale
- No3.6K ₳No rationale
- Yes1.6K ₳No rationale
- Yes675.6 ₳No rationale
- Yes335.9 ₳No rationale
- Yes13.5 ₳No rationale
- Yes6.3 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale