Withdraw ₳220,914 for Dolos: Sustaining a Lightweight Cardano Data Node

System1y ago1 post

On-chain changes

  • 220,914 ₳paid tostake17xz...6ghh5qjr

Abstract

This treasury withdrawal funds Dolos: Sustaining a Lightweight Cardano Data Node which will provide the following services:

This request for support focuses on Dolos https://dolos.txpipe.io/ a lightweight Cardano data node, designed as a backend for dApps. It is fine-tuned to solve a very narrow scope: keeping an updated copy of the ledger and replying to queries from trusted clients. Unlike a full Cardano node, Dolos is optimized for minimal resource usage while maintaining high data integrity and responsiveness. As an open-source project, Dolos has been steadily growing in adoption, with 366 commits, 367 pull requests, and contributions from 21 developers. It is becoming a key tool for projects seeking efficient blockchain data access without the overhead of full-node infrastructure. To ensure Dolos continues to evolve alongside Cardano's ecosystem, we are requesting funding for the following roles: 0.5 FTE Blockchain Developer and 0.125 FTE Tech Lead.

This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.

This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.

Motivation & rationale

This proposal aims to solve the following problem:

Dolos is a specialized Cardano data node designed to maintain an updated copy of the ledger and respond efficiently to queries. Optimized for data integrity and speed, it provides developers with reliable blockchain data access while requiring a fraction of the resources of a full node. Over the past year, Dolos has gained adoption within the Cardano ecosystem, with an active open-source community contributing to its growth. To continue improving its efficiency, maintaining compatibility with Cardano upgrades, and expanding its capabilities, ongoing development and maintenance are necessary. This proposal seeks funding to ensure Dolos remains actively supported, optimized, and available for the growing number of projects relying on it.

Project Solution

Securing funding for Dolos will ensure its continued maintenance, optimization, and feature expansion, directly benefiting projects that rely on fast and lightweight access to Cardano ledger data. Continued improvements will enhance performance, reduce infrastructure overhead, and support a broader range of use cases. By keeping Dolos actively maintained, the Cardano developer community gains a robust and efficient alternative to traditional node setups, lowering operational costs and improving blockchain data accessibility.

Vendor Profile

TxPipe is an active member of the Cardano ecosystem

TxPipe has been developing open-source tools for the Cardano ecosystem for over 3 years and we're not going anywhere. Evidence of our commitment can be found by evaluating the continuous activity of our public code repositories.

Experience developing in the Cardano ecosystem

TxPipe has helped developed several dApps for the Cardano ecosystem. This experience allows us to evaluate the feasibility of the project and its potential benefit from a developer's perspective. We've also participated in development of chains using the released version of the IOG's Partnerchain SDK.

Successful Catalyst proposals

We have successfully completed several Catalyst proposals. This may serve as evidence that our team has the required capabilities to fulfill these type of projects.

Development process will be public and open-source

Both the output and the development process will be public and open-source. This approach provides an easy way for the Catalyst team and the Cardano community to evaluate the progress at each step of the process.

Contract Management

A written off-chain Legal Contract will be created between the Vendor and the Cardano Development Holdings (CDH), as mandated by the constitution, and will be administered by Intersect. This will include details of the project delivery schedule and dispute resolution.

Project Delivery

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, of which the necessary information will be made public via the budget management platform via transaction metadata.

Defined by the milestones within a Legal Contract, the vendor will submit and attest milestone acceptance to the community, Intersect or 3rd Party Assurer.

Project progress will be monitored via Intersect's delivery assurance function which will be communicated to the community.

Acceptance of the above work is expected to be supported by a 3rd Party Assurer, who will be responsible for reviewing and signing off the work completed at each project milestone against the corresponding milestone deliverables detailed within the Legal Contract. This work is funded from a portion of this treasury withdrawal.

Budget Management Tooling

To administrate treasury funds on-chain, Intersect will utilize the treasury management smart contract framework developed by Sundae Labs. The smart contracts have been extensively tested including audits from TxPipe and MLabs. Examples of the usage of these contracts can be seen across mainnet described across Intersect authored Blog 1, Blog 2 and Blog 3.

Final mainnet validation test can be seen via the Disburse action within transaction: 0f591dc544ae14102dbb4a74d5311a6acffc1772b163d8b7a9656b9525950b17

With the confirmed treasury reserve contract address being: stake17xzc8pt7fgf0lc0x7eq6z7z6puhsxmzktna7dluahrj6g6ghh5qjr

Specifics

Intersect will utilize a single Treasury Reserve Smart Contract (TRSC), with many Project-Specific Smart Contracts (PSSC), managed by Intersect. Intersect's management consists of three 'admin' and two Intersect 'leadership' roles. An Oversight Committee consisting of five external, independent third-party entities will provide checks and balances on Intersect, and safeguard against errors and unilateral control. The administration of both TRSC and PSSCs will be managed by Intersect, with external oversight on certain actions from the Oversight Committee.

The Oversight Committee consists of Sundae Labs, Cardano Foundation, Dquadrant, Xerberus and NMKR. Their role is to independently verify key administrative actions using on-chain logic, ensuring accuracy and consistency without exercising discretion over governance decisions.

For all details on Intersect's configuration please see the Smart Contract Guide on the knowledgebase.

The high level permissions are as follows:

  • TRSC Fund and PSSC Modify

    • Two of the three Intersect admins, two of the five trusted entities and one of the two Intersect leadership sign-off must authorize
  • TRSC Disperse

    • Two of three Intersect admins, three of five trusted entities and two of two Intersect leadership sign-off must authorize
  • TRSC Pause and Resume

    • Two of three Intersect admins, and one of two Intersect leadership sign-off must authorize
  • TRSC Sweep

    • One of three Intersect admins, and one of two Intersect leadership sign-off must authorize
  • TRSC Reorganize

    • Two of three Intersect admins and three of five trusted entities must authorize

Processes

Upon enactment of this governance action, funding for this project will be directed into the TRSC's stake account. All instances of TRSC and PSSC can not be staked with a SPO and will be delegated to the auto-abstain predefined DRep. From here funds will be withdrawn into a UTxO remaining at the TRSC.

When the Legal contract is prepared and the vendor is ready, funding for this project will be transferred using the Fund action to a PSSC. All milestones will be outlined within the metadata.

A dashboard will be available for the community to audit the TRSC or PSSC and track metrics related to this withdrawn ada as well as being immutably verifiable on chain.

The subsections; Contract Management, Project Delivery, and Budget Management Tooling described above cover the constitutional requirements specified in Article IV section 4 and 5.

Rationale highlights

Why some of the largest DReps voted for and against, in their own words.

  • Yes435.8M ₳

    I will vote as necessary to help Cardano grow into a platform that supports the economic identities of billions of people. This proposal charges a fair price to achieve what is needed to achieve that. There are no significant matters that affect the...

    I will vote as necessary to help Cardano grow into a platform that supports the economic identities of billions of people. This proposal charges a fair price to achieve what is needed to achieve that.

    There are no significant matters that affect the neutrality of my decision-making.

    Detailed rationale and the improvements I would like to see made to the proposal are attached in the following spreadsheet "TW vote #01" or PDF.

    Specifically with regards to bundled proposals, next time I would request that one of the following be implemented:

    1. Bundled proposals should be subject to a temperature check vote for each item.
    2. I would like bundled proposals to be verified or created by entities, consortia, or individuals selected by the DRep.

    Spreadsheet:
    https://docs.google.com/spreadsheets/d/1M8JAuAntJOa7Z6j3GfC2hWFl4kbZLkzEel_cN4-kymw/edit?usp=sharing

    PDF:
    ipfs://bafkreianp5xhbo3ojlxqjjah4kyimr6u62uwnxd2t3lwwu3qmpn4jf4n5a

    私はCardanoが数十億人の経済アイデンティティを支えるプラットフォームへ成長していくために必要な投票を行います。この提案書は、それを達成するために必要な事項を実現するための正当なコストを請求しています。

    私の意思決定の中立性に影響を与える重大な事項はありません。

    根拠の詳細と、提案書について私が改善して欲しい点は、次のスプレッドシートの「TW vote #01」またはPDFに添付されています。

    特に、バンドル型提案書に関しては、次回は、次のいずれかが実施されることをリクエストします。

    1. バンドル型提案書は、内訳別の温度チェックの投票を行うこと。
2. バンドル型提案書は、DRepにより選出されるエンティティやコンソーシアムや個人により、検証または作成されるようにして欲しいと思います。

    Spreadsheet:
    https://docs.google.com/spreadsheets/d/1M8JAuAntJOa7Z6j3GfC2hWFl4kbZLkzEel_cN4-kymw/edit?usp=sharing

    PDF:
    ipfs://bafkreianp5xhbo3ojlxqjjah4kyimr6u62uwnxd2t3lwwu3qmpn4jf4n5a

  • Yes293M ₳

    Summary EMURGO, as a DRep, votes Yes of the “Dolos: Sustaining a Lightweight Cardano Data Node” proposal, based on the rationale provided below. Rationale Dolos represents a meaningful advancement in Cardano’s developer infrastructure. Designed as a...

    Summary
    EMURGO, as a DRep, votes Yes of the “Dolos: Sustaining a Lightweight Cardano Data Node” proposal, based on the rationale provided below.

    Rationale
    Dolos represents a meaningful advancement in Cardano’s developer infrastructure. Designed as a lightweight data node, it enables dApps to query blockchain data efficiently without the resource demands of a full node. The project is already live, open source, and actively maintained by TxPipe, an established and proven contributor to the Cardano ecosystem. With over 366 commits and 21 contributors, Dolos has gained traction among developers who rely on it for fast, reliable access to on-chain data.

    This proposal requests funding to ensure long-term compatibility with Cardano protocol updates, continued performance optimization, and improved developer support. Maintaining its stability is critical to the smooth functioning of other infrastructure projects built around it. By supporting this proposal, EMURGO affirms the value of tools that enhance scalability, developer experience, and decentralization across Cardano.

    Conclusion
    In conclusion, EMURGO supports this proposal as a strategic investment in Cardano’s backend infrastructure. We believe Dolos will play a key role in expanding accessibility and performance for developers and dApps, and we commend TxPipe’s continued commitment to open-source innovation.

  • No5.9M ₳

    Voting decision was made to be consistent with my reconciliation back in May 2025; https://2025budget.intersectmbo.org/voters/drep1yfdfs28uwafjgmrkatdektlzrvha2cmvqjhuz700e04mawq23rmrg Ready to move forward overall with the budgeting process and look forward...

    Voting decision was made to be consistent with my reconciliation back in May 2025;
    https://2025budget.intersectmbo.org/voters/drep1yfdfs28uwafjgmrkatdektlzrvha2cmvqjhuz700e04mawq23rmrg

    Ready 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

  • No1.8M ₳

    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...

    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.

See all 55 rationales