Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp P...
Discussed in the Governance Review for epochs 642 to 646.
119 DReps voted · 36 with a rationale · 2 re-voted unchanged
Open a row to read the rationale.
Struck-through weight was cast after ratification and did not count in the tally.
- Yes5.3M ₳No rationale
- Yes5.1M ₳No rationale
- Yes4.9M ₳No rationale
- Yes4.5M ₳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.8M ₳No rationale
- Yes2.7M ₳Rationale
私は本Treasury Withdrawalに賛成します。
Tx3は、CardanoのdApp protocolを開発者・wallet・aggregator・AI agentが共通のinterfaceで発見・統合・実行できるようにする重要なDevX公共インフラです。CardanoのUTxO/eUTxO型dAppは堅牢である一方、protocolごとのtransaction pattern理解が必要で、統合コストが高いという課題があります。Tx3は、共通API・SDK・Protocol Registryを通じて、Cardano dAppの統合と再利用を容易にします。
また、TxPipeはPallas、Dolos、UTxO RPCなどで実績があり、既にTx3 developer layerと複数protocol onboardingの実績がある点も評価します。追加12 protocol onboarding、MCP server、agent skills frameworkは、CardanoをAI agent時代に対応したprotocol ecosystemへ近づける可能性があります。
資金管理面でも、Intersect管理のSmart Contract Disbursement、milestone-based controls、oversight、dashboard透明性が含まれており、Treasury資金を検証可能に管理する設計として妥当です。
I support this Treasury Withdrawal.
Tx3 is an important DevX public infrastructure that allows Cardano dApp protocols to be discovered, integrated, and executed through a common interface by developers, wallets, aggregators, and AI agents. While Cardano’s UTxO/eUTxO-based dApps are robust, each protocol requires specific understanding of transaction patterns, which raises integration costs. Tx3 helps reduce this friction through common APIs, SDKs, and a Protocol Registry.
I also value TxPipe’s proven track record with Pallas, Dolos, UTxO RPC, and other Cardano infrastructure, as well as the existing Tx3 developer layer and multiple protocol onboardings. The additional 12 protocol onboardings, MCP server, and agent skills framework can help move Cardano toward a protocol ecosystem ready for the AI agent era.
From a funding-management perspective, I also appreciate the inclusion of Intersect-managed Smart Contract Disbursement, milestone-based controls, oversight, and dashboard transparency. This is a reasonable structure for managing Treasury funds in a verifiable way.
- 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 Tx3 proposal.
I have considered this proposal carefully because, unlike the lower-level TxPipe maintenance proposals I have already supported, Tx3 sits higher in the developer stack. It is not simply core library maintenance. It is an open API/interface layer intended to make Cardano dApp protocols easier to describe, integrate with, and consume.
However, I believe this proposal still fits within my broader “fund the rails before the growth bets” approach.
Tx3 aims to help protocol authors define reusable interfaces for UTxO-based dApp interactions, allowing wallets, applications, SDKs, agents and other tools to generate typed clients and build transactions against those protocols more reliably. This can reduce integration friction, improve developer experience, and make Cardano applications easier to compose and connect.
Cardano’s UTxO model is powerful, but dApp interaction remains harder to standardise than in account-based ecosystems. A common interface layer for protocol interactions could become valuable infrastructure if adopted widely and kept open.
I also view this proposal differently from large commercial growth, liquidity, or treasury-capital deployment proposals. The ask is 1,684,050 ADA, which is material but comparatively modest relative to many live treasury requests. It is Cardano-native, developer-facing, open-source oriented, and linked to a credible technical team with a strong delivery history across the ecosystem.
In the current NCL environment, I remain cautious on broad growth asks, private commercial subsidies, and large DeFi or treasury-investment programmes. But I am willing to support focused proposals that strengthen the technical rails builders use to create applications on Cardano.
My support is not unconditional. I would expect clear reporting on protocol onboarding, SDK generation, adoption by external teams, documentation quality, open-source delivery, and evidence that Tx3 becomes an ecosystem tool rather than a narrow TxPipe-specific layer.
On balance, I believe this proposal is a proportionate investment in Cardano developer infrastructure and dApp composability.
For these reasons, I vote YES.
- Yes1.9M ₳No rationale
- Yes1.6M ₳No rationale
- Yes1.3M ₳No rationale
- Yes1.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 withdrawal
- Yes581.7K ₳No rationale
- Yes570.1K ₳Rationale
Absolutely
- Yes568.1K ₳No rationale
- Yes482.3K ₳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!
- No366.9K ₳No rationale
- No347.9K ₳No rationale
- Not countedYes335.5K ₳No rationale
- Yes333.1K ₳No rationale
- Yes297.7K ₳Rationale
Seems like a good idea
- Yes284.5K ₳No rationale
- Yes275.9K ₳No rationale
- Yes272.4K ₳No rationale
- Abstain261.1K ₳Rationale
Non-Critical Infrastructure Spend.
While the AI-agent integration design via MCP is innovative, it represents an ecosystem luxury rather than critical, life-sustaining Layer-1 node infrastructure during major protocol upgrade cycles. - Yes214.5K ₳No rationale
- Yes188.5K ₳No rationale
- Yes182.9K ₳No rationale