Withdraw 540,750 ada for UTxO RPC by TxPipe: Maintaining Cardano’s Integratio...
Discussed in the Governance Review for epochs 642 to 646.
115 DReps voted · 37 with a rationale · 4 re-voted unchanged
Open a row to read the rationale.
- Yes5.1M ₳No rationale
- Yes4.9M ₳No rationale
- Yes4.5M ₳No rationale
- Yes4.2M ₳No rationale
- Yes4.1M ₳Rationale
I see this as a administrative vote which is to process a withdrawal that DRep's have previously approved. I do not believe in throwing monkey-wrenches into approved and planned for processes, and thus I vote yes so as not to obstruct progress and momentum, and to not undermine previous decisions.
- Yes2.7M ₳Rationale
私は本Treasury Withdrawalに賛成します。
UTxO RPCは、簡単に言えば、CardanoなどのUTxO型ブロックチェーンにアクセスするための共通API仕様です。Cardano node、Amaru、Dingo、Dolos、wallet、indexer、developer toolingなどがCardanoデータへアクセスするための共通インターフェース標準であり、特定dAppの私的開発ではなく、Cardano全体で再利用可能なOSS DevX基盤です。
さらに、UTxO RPCがCardano専用ではないことは弱点ではなく、むしろUTxO系エコシステムで共有できる標準としての波及効果を持ちます。Cardano node実装群で採用され、UTxO型ブロックチェーン間で共通化が進めば、Cardanoのdata access layer、developer experience、client diversityを強化し、CardanoがUTxO標準化の中心的な役割を担う可能性があります。
また、本提案はIntersect管理のSmart Contract Disbursement、TRSC/PSSC、milestone-based controls、oversight committee、dashboard透明性を備えており、Treasury資金管理としても評価できます。
I support this Treasury Withdrawal.
UTxO RPC is, simply put, a common API specification for accessing UTxO-based blockchains such as Cardano. It provides a shared interface for Cardano node, Amaru, Dingo, Dolos, wallets, indexers, and developer tooling to access Cardano data. This is not private development for a specific dApp, but reusable OSS DevX infrastructure for the broader Cardano ecosystem.
The fact that UTxO RPC is not Cardano-only is not a weakness. Rather, it gives the project broader value as a standard that can be shared across the UTxO ecosystem. If it continues to be adopted by Cardano node implementations and becomes more common across UTxO-based blockchains, it can strengthen Cardano’s data access layer, developer experience, and client diversity, while positioning Cardano as an important contributor to UTxO standardization.
I also value the funding design of this proposal. It uses Intersect-managed Smart Contract Disbursement, TRSC/PSSC, milestone-based controls, an oversight committee, and dashboard transparency. These are positive elements for responsible Treasury fund management.
- Yes2.6M ₳No rationale
- Abstain2.5M ₳No rationale
- Yes2.5M ₳Rationale
Due to rationales becoming stressful and the bear market vibes - I will not be providing rationale. I voted the way that I did bc we need a 'no stress' environment more than ever.
- Yes2.2M ₳No rationale
- Yes2.2M ₳No rationale
- Yes2.1M ₳Rationale
I am voting YES on the TxPipe UTxO RPC proposal.
UTxO RPC is important developer infrastructure for Cardano because it helps standardise how applications, tools, SDKs and services interact with UTxO-based blockchain data.
This is not the same as funding another hosted API provider like Blockfrost or Koios. UTxO RPC sits at a different layer. It is an open interface specification that can be implemented by different backends and used across multiple languages and developer environments.
That matters because Cardano needs more interoperability, less integration fragmentation, and better developer experience. A common interface for UTxO-based data access can make it easier for wallets, dApps, indexers, SDKs, infrastructure providers and future tooling to communicate in a consistent way.
In the current NCL environment, I believe DReps need to be selective. My priority is to support scoped proposals that maintain essential public goods, open-source infrastructure, developer tooling, protocol compatibility and the technical rails that Cardano builders rely on.
UTxO RPC fits that framework.
The proposal is modest in size compared with many other live treasury requests and is focused on maintenance, compatibility, SDK support, documentation, community support and continued improvement of a standard already used by several ecosystem workstreams.
I also view it positively that this proposal is structured through the 2026 treasury management framework, with Intersect administration, oversight controls, milestone-based disbursement and community auditability.
There is some overlap with other data access tools and providers in the ecosystem, but I do not see that as a reason to reject it. Cardano benefits from having open, interoperable, self-hostable and implementation-neutral standards that reduce reliance on any single provider or integration path.
For these reasons, I consider this a responsible and proportionate use of treasury funds.
I vote YES.
- Yes1.9M ₳No rationale
- Yes1.6M ₳No rationale
- Yes1.3M ₳No rationale
- No1.3M ₳No rationale
- Yes1.2M ₳No rationale
- Yes1.2M ₳No rationale
- Yes1.1M ₳No rationale
- Yes1.1M ₳No rationale
- Yes1.1M ₳No rationale
- Yes982.8K ₳No rationale
- Yes927.1K ₳No rationale
- Yes926.9K ₳No rationale
- Yes911.5K ₳No rationale
- Yes884.6K ₳No rationale
- Yes867K ₳No rationale
- Yes832.6K ₳Rationale
We support Intersect's budget process. This proposal is part of it.
- Yes812K ₳No rationale
- Yes665.2K ₳No rationale
- Yes622.3K ₳No rationale
- Yes586.6K ₳Rationale
Supporting the withdrawal for the proposal to get underway
- Yes581.7K ₳No rationale
- Yes570.1K ₳Rationale
Critical and good deal.
- Yes568.1K ₳No rationale
- No379.7K ₳Rationale
TxPipe is among the companies that in my opinion have extracted more than enough profits from the Cardano ecosystem and shouldn't be funded anymore.
Power to the edges!
- NoRevoted366.9K ₳History
Earlier votes
No2mo agoSuperseded
- No347.9K ₳No rationale
- Yes333.1K ₳No rationale
- Yes297.7K ₳Rationale
I think this is a reasonable price to pay for UTxO RPC to not die. Framing it in such dramatic terms makes me grateful for this treasury and our ability to use it to stave of death for many important projects during this particularly brutal winter. I'm glad that Cardano doesn't live or die on the whims of a handful of VCs.
- Yes284.5K ₳No rationale
- Yes275.9K ₳No rationale
- Yes272.4K ₳No rationale
- Yes261.1K ₳No rationale
- Yes214.5K ₳No rationale
- Yes188.5K ₳No rationale
- Yes182.9K ₳No rationale
- Yes161.1K ₳No rationale
- Yes160.9K ₳No rationale
- Yes155.9K ₳Rationale unavailable