Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp P...
119 DReps voted · 36 with a rationale · 2 changed their vote
Open a row to read the rationale.
- Yes575M ₳Rationale
Yoroi DRep votes YES on Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp Platform. The Cardano community has spoken clearly through the Hydra off-chain voting platform, and Yoroi is committed to honouring that voice.
- Honouring the Community Mandate: With a supermajority of over 67% in the off-chain governance process, this proposal carries a strong and unambiguous signal of community support. Yoroi votes Yes in alignment with that collective decision.
- Yes384.3M ₳Rationale
Please check the following link for the reasons for the vote.（投票理由は次のページを参照してください。)
- Abstain331.6M ₳No rationale
- Yes299.7M ₳Rationale
EMURGO as a DRep votes YES on Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp Platform, with rationale outlined below.
This proposal successfully completed the off-chain community governance process on the Hydra voting platform, crossing the required 67% approval threshold. EMURGO respects the legitimacy of this community-led process and votes YES in recognition of the mandate that the Cardano community has clearly expressed. For these reasons, EMURGO votes yes.
- Yes258.5M ₳No rationale
- Yes219.4M ₳Rationale
We vote on Intersect budget items as we did on Ekklesia.
- Yes175.4M ₳No rationale
- Abstain171.3M ₳No rationale
- Abstain123.7M ₳Rationale
This document includes the Cardano Foundation’s voting decisions and individual voting rationales for the 11 Treasury Withdrawal governance actions submitted following the Intersect-facilitated budget process.
A PDF version of this rationale is also made available.
Our approach is designed to ensure both transparency and efficiency, applying a consistent evaluation framework (see the “Cardano Foundation Voting Decisions for the 2026 Intersect Budget Process”) to each proposal and presenting our reasoning in a single, comprehensive document.
No material changes have been made to the individual proposals since the budget proposals were approved in Hydra Voting, therefore our votes on these withdrawals reflect our original assessment and vote. Our voting decisions on the 11 treasury withdrawals are made available in the table below.
Fund administration clarity is an important consideration for our voting decisions. Our expectation is that expect Intersect, as administrator, will manage funds diligently, provide public transparency on contracts, and ensure robust oversight, holding recipients accountable for deliverables.
Conclusion
The Cardano Foundation’s votes on these 11 treasury withdrawal governance actions are the direct execution of a single, comprehensive review process that began during the Hydra Voting phase. Although we present one aggregate rationale for efficiency, each proposal and governance action was individually assessed against a consistent framework anchored in our publicly stated principles.
Voting Record
Governance Action ID Title Vote Rationale gov_action1k02...cw2nc5 Withdraw 3,961,538 ada for Bringing Real-World Payments to Cardano with Wirex YES The Wirex proposal credibly contributes to adoption and utility because the deliverables provide card-based financial services and open payment rails linked to on-chain balances. The proposal is expected to expand real-world payment utility and leverage Wirex's established scale to create a plausible path toward increased ecosystem usage to justify treasury investment. The budget justification would benefit from establishing explicit Cardano-specific user migration volumes, ADA spending targets, and a delineation of open-source components. However, the team demonstrates a strong operational history and extensive multi-jurisdictional transaction experience. Based on this, CF votes Yes. gov_action1k02...tttste Withdraw 540,750 ada for by TxPipe Dolos: Maintaining Cardano's Lightweight Data Node, Year 2 YES The Dolos by TxPipe proposal credibly contributes to infrastructure and research excellence because the deliverables target a mature, non-Haskell alternative node implementation that directly decentralizes data access. The proposal is expected to drive sustained protocol-level engagement and support long-term network resilience by safeguarding critical node diversity. Furthermore, the team has a proven track record of continuous infrastructure delivery and verifiable software releases across prior cycles, and the budget is appropriately justified given a clean cost structure for a part-time maintainer that features a transparent return-to-treasury clause for unused contingency reserves. However, the proposal would benefit from less generic milestone definitions that commit to specific protocol-version readiness for upcoming hard forks and more defined deliverables to support its speculative AI-integration scope. Based on this, CF votes Yes. gov_action1k02...hyg4hw Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026 NO The Hardware Wallet Maintenance 2026 proposal has potential to contribute to security, continuity, and ecosystem access as the deliverables target a critical access layer to ensure ongoing hardware wallet compatibility for ADA holders. However, the budget is not appropriately justified and compared to previous funding cycles for similar scopes seems too high. Additionally, the project presents substantial execution and accountability risks, evidenced by incomplete milestones and significant delivery delays in the 2025 cycle, alongside a repository changelog that suggests an undocumented complete rewrite rather than routine maintenance. Without explicit clarifications regarding vendor responsibilities, itemized cost increases, and structured milestone definitions managed via clear, centralized ecosystem demand, the current proposal lacks the necessary transparency for public funding. Based on this, CF votes No. gov_action1k02...ypfkyr Withdraw 1,193,000 ada for Intersect Technical Steering Committee Support YES IntersectTSC credibly contributes to the development of Cardano governance and supports infrastructure and research excellence. The proposed milestones strongly align with the strategic priorities and 'Our Cardano' principles by funding critical operations for the Parameter Committee, CIP Editors, and Hard Fork Working Group. The proposal is expected to generate meaningful on-chain activity through direct network usage, transaction volume, governance participation, and enhanced by WP1 expert event engagements. The team has a proven track record of delivering ecosystem grants and meaningful outcomes, as evidenced by their coordination of the Plomin and Chang hard forks. The budget is appropriately justified given the phased milestone structure with clearly defined acceptance criteria and provisions for independent oversight, including independent third-party audit verification via Appold and an absolute return-to-treasury policy for all unspent capital. However, it is recommended that WP1 track active delivery metrics rather than event attendance, and mandate the publication of post-event reports to turn travel into a strategic intelligence asset, while WP3 must enforce its promised total independent recusal framework. Based on this, CF votes Yes. gov_action1k02...x6wlxf Withdraw 25,400,000 ada for Intersect: Governance coordination and technical stewardship for the Cardano ecosystem ABSTAIN This Intersect proposal credibly contributes to open governance coordination, technical stewardship, and ecosystem outreach as the deliverables successfully support the off-chain coordination model outlined in the Cardano 2030 Strategy. However, the immediate impact of its 2026 technical budget to on-chain network growth remains obscured by substantial operational ambiguities. This is because its technical focus risks introducing unnecessary parallel management layers rather than directly driving clean, high-impact technical utility. Furthermore, while the organization has demonstrated experience managing an evolving decentralized landscape over the past two years, the total requested budget of 25,400,000 ADA is not appropriately justified given a lack of granular, itemized baseline financial accounting and clear 2025 actual expenditure statements to verify true value-for-money. Additionally, extensive work packages within the proposal heavily overlap with core software maintenance, repository stewardship, and infrastructure monitoring solutions already maintained by the ecosystem, while the current committee framework introduces administrative overheads that require swift structural streamlining to prioritize tangible, democratic, and measurable outcomes. Based on this, CF votes Abstain. gov_action1k02...4l0u4y Withdraw 3,810,423 ada for Mithril Protocol YES The Mithril Protocol proposal credibly contributes to infrastructure, scalability, and research excellence by providing critical light-client verification models, Layer 2 anchoring primitives, and SNARK-based certificate compression frameworks. The proposal is expected to drive long-term protocol maintainability, cross-chain interoperability, and future-proof network resilience, thereby justifying treasury investment. Furthermore, the team has a proven track record of peer-reviewed engineering delivery and technical execution, and the budget is appropriately justified, as the requested funding is consistent with the strategic importance of the core infrastructure tracks. However, the proposal would benefit from a clearer, itemized breakdown of staffing costs and full-time equivalent (FTE) allocations to address headline cost concerns, as well as a more explicit articulation of broader system impacts regarding network decentralization and production wallet integration pathways. Based on this, CF votes Yes. gov_action1k02...fsvefn Withdraw 1,162,746 ada for MLabs Core Tool Maintenance & Enhancement: Plutarch and Ply YES The MLabs Core Tool Maintenance & Enhancement proposal credibly contributes to infrastructure and developer experience by providing essential maintenance and ongoing enhancements for widely used developer tools. While maintenance itself is not expected to generate immediate on-chain activity, safeguarding heavily used builder infrastructure protects the ecosystem from severe disruption and ensures that future transaction volume and adoption remain sustainable. Furthermore, the team has a demonstrated track record of delivering foundational developer tools, and the budget is appropriately justified given that it represents a fairly reasonable and standard funding request for specialized repository oversight. Based on this, CF votes Yes. gov_action1k02...64d667 Withdraw 540,750 ada for Oura by TxPipe: Maintaining Cardano’s Event Pipeline YES The Oura by TxPipe proposal credibly contributes to infrastructure, developer decentralization, and ecosystem accessibility by providing essential open-source event data pipeline tooling that directly benefits a wide range of active deployments. The proposal is expected to drive sustained protocol-level engagement and protect ecosystem growth from the adverse risks of critical tool attrition to justify treasury investment. Furthermore, the team has established a reliable track record of building foundational developer solutions, and the budget is appropriately justified given that the funding request is neither excessive nor unrealistic for a dedicated maintenance resource. However, the proposal would benefit from increased clarity regarding its SLAs and explicit expectations for the full-time maintainer. Based on this, CF votes Yes. gov_action1k02...d0ztd8 Withdraw 540,750 ada for Pallas by TxPipe: Maintaining Cardano's Core Rust Libraries, Year 2 YES The Pallas by TxPipe proposal credibly contributes to infrastructure and research excellence because the deliverables target core, low-level building blocks that directly support critical downstream network dependencies like Amaru. The proposal is expected to drive sustained protocol-level engagement and safeguard foundational infrastructure that justifies treasury investment. Furthermore, the team has demonstrated the necessary expertise to maintain the solution, and the budget is appropriately justified given the essential utility and ongoing ecosystem reliance on the repository. However, the proposal would benefit from clearer resource guarantees to ensure the allocated developer actively manages and maintains the codebase. Based on this, CF votes Yes. gov_action1k02...72rg72 Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp Protocols ABSTAIN The Tx3 by TxPipe proposal has potential to contribute to adoption, utility, and ecosystem growth as the deliverables target a standardized open interface layer, multi-language SDKs, and agent-facing tools designed to make decentralized protocols discoverable and composable. While this proposal has potential to drive future protocol-level engagement and enhance developer experiences, its immediate on-chain impact remains prospective rather than proven. Although the team has demonstrated a credible foundation with active public repositories and strong strategic alignment, the budget is not appropriately justified given an overly broad 12-month scope backed by a thin financial breakdown. Additionally, the proposal lacks crucial technical and governance evidence, including a specific protocol candidate list, detailed FTE allocations, cloud sizing parameters, explicit SLA assumptions, and concrete acceptance criteria. Based on this, CF votes Abstain. gov_action1k02...z9qdza Withdraw 540,750 ada for UTxO RPC by TxPipe: Maintaining Cardano’s Integration Standard, Year 2. YES The UTxO RPC by TxPipe proposal credibly contributes to ecosystem growth, infrastructure, and interoperability by providing a standardized integration surface and multi-language SDKs that systematically reduce developer friction. The proposal is expected to drive sustained protocol-level engagement by reinforcing node and client diversity across key projects like Amaru, Dingo, and the Haskell Cardano node that justifies treasury investment. Furthermore, the team has demonstrated a specialized track record as a protocol maintainer with strong public code and runtime evidence, and the budget is appropriately justified given the essential nature of shared open infrastructure. However, the proposal would benefit from increased specificity in its milestone definitions, including clearly defined maintenance SLAs, explicit mapping for version compatibility targets, and proper license file cleanup across all active repositories. Based on this, CF votes Yes. - Yes92.2M ₳No rationale
- Abstain90.6M ₳Rationale
As a DRep, I ABSTAIN on the proposal: Tx3 by TxPipe – Open API Layer for Cardano’s dApp Protocols.
My rationale:
Tx3 addresses a real problem in the Cardano developer ecosystem. Integrating with Cardano protocols often requires developers to understand protocol-specific transaction structures, datums, redeemers, reference inputs, and off-chain logic. A standardized interface that can generate documentation, SDKs, and deterministic unsigned transactions could reduce duplicated integration work.
The project is not starting from zero. The core framework, protocol gateway, registry, and several protocol definitions are publicly visible on GitHub. TxPipe has also demonstrated that it can deliver technically complex open-source infrastructure.
I particularly value the developer-facing part of the proposal. A common interface for Cardano protocols could benefit wallets, aggregators, developers, and other applications even if the expected growth of AI-driven blockchain activity does not materialize as quickly as predicted.
However, I am not ready to vote YES on the proposal in its current form.
The proposal states that five protocols are already live, but this does not necessarily mean that the complete functionality of these protocols has been integrated. For example, the Strike implementation covers staking rather than the main derivatives protocol, while parts of the Bodega workflow remain outside the current Tx3 capabilities.
The proposal does not clearly define what will count as one of the twelve new protocol onboardings. A small or partial feature of a large dApp should not automatically be considered a complete protocol integration.
The twelve protocols are also not identified, and there is no clear selection process, evidence of demand from protocol teams, or requirement for those teams to validate the resulting interfaces.
I would also expect a clear verification standard. Each integration should be tested against real on-chain transactions, include reproducible test vectors, document unsupported functionality, and ideally receive confirmation from the relevant protocol team.
The AI-agent and MCP components are interesting, but they remain more speculative than the existing developer tooling. The proposal should be justified primarily by current developer demand and measurable adoption rather than assumptions about future autonomous-agent activity.
The proposal also lacks sufficient information about the team, FTE allocation, cost per protocol integration, development costs for the MCP server, security review, hosting, and maintenance of the existing integrations.
The total request of 1,684,050 ADA may be reasonable for the proposed scope, but the budget is presented as a single work package and does not provide enough detail for me to evaluate whether the cost is proportionate.
There is also no clear long-term maintenance model. Protocols change, contracts are upgraded, and addresses and transaction patterns may become outdated. The proposal should explain who will be responsible for keeping the protocol definitions accurate and how outdated or unsafe integrations will be identified and disabled.
I see clear potential in Tx3, and the visible work gives me confidence that TxPipe is capable of delivering. However, the proposal does not provide enough detail about the exact deliverables, integration completeness, verification standards, adoption, security, cost breakdown, and long-term maintenance.
For these reasons, I ABSTAIN.
If you'd like to support my work, consider delegating to the MANDA pool and backing me as a DRep. Your support is the only way I can get time for governance.
MANDA Pool ID:
pool1c3fjkls7d2aujud8y5xy5e0azu0ueatwn34u7jy3ql85ze3xya8My DRep ID:
drep1y2m0g4r66pyaw3p7u454wc0p4f0ygm8ueaev0mgd3tvwm7sskqwqpBuy me a beer:
https://pay.cexplorer.io/pay/c0410d5b237b6ec0 - Yes88.4M ₳Rationale
SIPO DRep votes YES, with expectations, on the treasury withdrawal of 1,684,050 ada for Tx3 (TxPipe) — Open API Layer for Cardano's dApp Platform.
Why SIPO votes Yes. Tx3 is an open API layer for the dApp platform. An open, maintained API surface is the difference between an ecosystem builders can enter and one gated behind bespoke integrations.
SIPO DRep votes on this action as part of the 2026 Intersect Budget Process infrastructure batch — eleven treasury withdrawals submitted in a single transaction by Intersect on behalf of vendors, each having achieved the required 67% support threshold in the 2026 Intersect Budget Process Hydra Voting phase.
Shared basis. All eleven withdrawals share a single on-chain recipient: the 2026 Intersect Treasury Reserve Smart Contract at the script credential stake1784sdxt6jjennmstphgdu7l7c2scf5d02a6cve2dgn5s2kq5u3j9v, built on the Sundae Labs treasury-contracts framework. Disbursement is milestone-gated through a Project-Specific Smart Contract; authorization requires a quorum spanning Intersect admins, Intersect leadership and independent trusted entities; an Oversight Committee of six external parties — Sundae Labs, Cardano Foundation, Dquadrant, NMKR, Sundial and Eternl — independently verifies key administrative actions using on-chain logic; the contracts cannot be staked with an SPO and are delegated to the auto-abstain DRep; and a public dashboard lets the community audit the flow. This is the strongest fund-control class SIPO recognizes, and the same structure SIPO has already supported on Cardano Critical Integrations V2, Cardano Vision 2026, IO Hydra and Tweag Core Cardano Infrastructure. SIPO voted Yes on the Cardano Budget Process Framework and holds that treasury allocation should converge and mature through that route; having supported the route, SIPO does not reject its outputs absent a specific defect. This withdrawal complies with the 350M Net Change Limit covering Epochs 613 to 713 and with guardrail TREASURY-02a.
Expectations attached to this Yes. (1) Milestone-level reporting through the TRSC and PSSC of what was disbursed, to whom, and against which deliverable, surfaced on the public dashboard. (2) Continued open-source release of the funded work, and a clear statement of which work is baseline maintenance versus new development. (3) Continued independence of the Oversight Committee, and transparent tracking of cumulative treasury receipts by the recipient and by Intersect. (4) Where scope could overlap with other funded efforts, articulation at ecosystem level of the boundary, so that scope does not silently duplicate.
This vote is SIPO DRep's recorded position.
SIPO DRep として、Tx3 (TxPipe) — Open API Layer for Cardano's dApp Platform（1,684,050 ada）のトレジャリー引き出しに、期待事項付きで賛成（YES）を投じます。
SIPO が賛成する理由。Tx3 は dApp プラットフォームのためのオープン API 層です。開かれ、保守された API 面があるかどうかは、ビルダーが参入できるエコシステムか、個別統合の背後に閉ざされたエコシステムかの分かれ目です。
SIPO DRep は、本アクションを 2026 Intersect Budget Process インフラ・バッチ（Intersect が各 vendor を代表して単一トランザクションで提出した 11 件のトレジャリー引き出し。いずれも 2026 Intersect Budget Process の Hydra Voting フェーズで必要な 67% の支持閾値を達成）の一部として評価しました。
共通の根拠。11 件すべてが単一のオンチェーン受領先を共有します: script credential stake1784sdxt6jjennmstphgdu7l7c2scf5d02a6cve2dgn5s2kq5u3j9v の 2026 Intersect Treasury Reserve Smart Contract（Sundae Labs の treasury-contracts フレームワーク）です。払い出しは Project-Specific Smart Contract を通じてマイルストーンでゲートされ、承認には Intersect の admin・leadership・独立した trusted entity にまたがる定足数を要します。6 社の外部 Oversight Committee（Sundae Labs・Cardano Foundation・Dquadrant・NMKR・Sundial・Eternl）がオンチェーンロジックで主要な管理アクションを独立検証します。コントラクトは SPO にステークできず auto-abstain DRep に委任され、公開ダッシュボードでコミュニティが資金の流れを監査できます。これは SIPO が認める最強クラスの fund-control であり、SIPO が既に支持した Cardano Critical Integrations V2・Cardano Vision 2026・IO Hydra・Tweag Core Cardano Infrastructure と同一の構造です。SIPO は Cardano Budget Process Framework に賛成しており、トレジャリー配分はこのルートで収斂・成熟すべきだと考えます。ルートを支持した以上、特段の瑕疵がない限りその産物を拒みません。本引き出しは Epoch 613〜713 を対象とする 350M Net Change Limit および guardrail TREASURY-02a に準拠しています。
本賛成に付す期待事項。(1) TRSC / PSSC を通じて、何が・誰に・どの成果物に対して払い出されたかをマイルストーン単位で報告し、公開ダッシュボードに反映すること。(2) 資金提供された成果のオープンソース公開を継続し、どこまでが baseline の保守で、どこからが新規開発かを明示すること。(3) Oversight Committee の独立性を維持し、受領者および Intersect の累計トレジャリー受領額を透明に追跡すること。(4) 他の資金提供済の取り組みとスコープが重複しうる場合、その境界をエコシステムレベルで明確化し、暗黙裡に重複しないようにすること。
本投票は SIPO DRep の記録上の立場表明です。
- Yes76.7M ₳No rationale
- Yes75.9M ₳Rationale
I support this proposal because it funds shared infrastructure that benefits the broader Cardano ecosystem rather than a single application.
By providing standardized APIs, SDKs, auto-generated documentation, and an MCP server, this project lowers integration costs and makes Cardano protocols more accessible to both developers and future AI agents. This should improve interoperability and composability across the ecosystem.
I also recognize TxPipe's proven track record of delivering open-source infrastructure through Catalyst and Intersect, which gives me confidence that this proposal builds upon demonstrated execution rather than an untested concept.
That said, I encourage continued transparency regarding adoption metrics, ecosystem usage, milestone reporting, and long-term maintenance beyond the initial funding period.
Overall, I believe this is a valuable public-good investment that strengthens Cardano's developer ecosystem and future readiness, and I therefore vote Yes.
この提案は、単一のプロジェクトではなく、Cardanoエコシステム全体の開発者体験と相互運用性を向上させる共有インフラへの投資であると評価しました。
標準化されたAPI、SDK、自動生成ドキュメント、MCPサーバーの整備により、開発者や将来的なAIエージェントが複数のCardanoプロトコルへ容易にアクセスできるようになります。これにより、統合コストの削減やプロトコル間のコンポーザビリティ向上が期待できます。
また、TxPipeはCatalystやIntersectを通じて既に複数の成果を提供しており、本提案も既存の実績を基盤とした継続的な開発である点を評価しました。
一方で、採用状況を測るKPIや利用実績、長期的な運用・保守計画については、今後も透明性の高い進捗報告を期待します。
Cardano全体に恩恵をもたらす公共性の高いインフラ投資であると判断し、本提案に賛成します。
- Abstain74.6M ₳No rationale
- Yes69.3M ₳No rationale
- Yes62.7M ₳No rationale
- Abstain51M ₳Rationale
Because of fundamental concerns with the current treasury process, I vote Abstain on all Treasury Withdrawal proposals until the treasury budgeting process undergoes fundamental reform.
More information: https://x.com/ada_stat/status/2068315882539921703
- NoRevoted50.4M ₳Rationale
I am voting No on this proposal. This year's Net Change Limit (NCL) has been set well above the level I consider sustainable. Under my published voting framework, an appropriate NCL is roughly 15% of the previous year's staking rewards (on the order of 82M ADA), whereas the NCL currently in force is several times that amount. Because the treasury is already authorized to disburse far beyond my personal NCL threshold, I am voting No on all treasury withdrawal proposals until aggregate withdrawals are brought back within a sustainable limit — regardless of the individual merits of any single proposal. This vote reflects a position on total treasury spend, not a judgment on the value of your specific project. Reference: https://coffeepool.jp/notes/drep-voting-framework-for-sustainable-ecosystem/\n\n[Japanese version follows]\n\n本提案に反対票を投じます。今年のNet Change Limit（NCL）は、私が持続可能と考える水準を大幅に上回って設定されています。公開済みの投票フレームワークでは、適正なNCLは前年のステーキング報酬の約15%（82M ADA）ですが、現行のNCLはその数倍に達しています。トレジャリーは既に私のpersonal NCL（個人として許容する上限）を大きく超える出金が認められている状態にあるため、出金総額が持続可能な範囲に戻るまで、個別提案の良し悪しに関わらず、すべてのトレジャリー出金提案に反対票を投じます。本投票はトレジャリー支出全体に対する立場の表明であり、貴提案の価値そのものを否定するものではありません。参照: https://coffeepool.jp/notes/drep-voting-framework-for-sustainable-ecosystem-jp/
Earlier votes
No1mo agoSuperseded
I am voting No on this proposal. This year's Net Change Limit (NCL) has been set well above the level I consider sustainable. Under my published voting framework, an appropriate NCL is roughly 15% of the previous year's staking rewards (on the order of ₳82M), whereas the NCL currently in force is several times that amount. Because the treasury is already authorized to disburse far beyond my personal NCL threshold, I am voting No on all treasury withdrawal proposals until aggregate withdrawals are brought back within a sustainable limit — regardless of the individual merits of any single proposal. This vote reflects a position on total treasury spend, not a judgment on the value of your specific project. Reference: https://coffeepool.jp/notes/drep-voting-framework-for-sustainable-ecosystem/ [Japanese version follows] 本提案に反対票を投じます。今年のNet Change Limit（NCL）は、私が持続可能と考える水準を大幅に上回って設定されています。公開済みの投票フレームワークでは、適正なNCLは前年のステーキング報酬の約15%（₳82M程度）ですが、現行のNCLはその数倍に達しています。トレジャリーは既に私のpersonal NCL（個人として許容する上限）を大きく超える出金が認められている状態にあるため、出金総額が持続可能な範囲に戻るまで、個別提案の良し悪しに関わらず、すべてのトレジャリー出金提案に反対票を投じます。本投票はトレジャリー支出全体に対する立場の表明であり、貴提案の価値そのものを否定するものではありません。参照: https://coffeepool.jp/notes/drep-voting-framework-for-sustainable-ecosystem-jp/
- No49.5M ₳No rationale
- Yes47.5M ₳No rationale
- Yes39.9M ₳No rationale
- Yes37.4M ₳No rationale
- Yes37.3M ₳No rationale
- Yes34.5M ₳No rationale
- Yes34.4M ₳Rationale
Socious votes Yes. Tx3 is TxPipe's open API layer for dApp protocols: a standard way for applications to describe and construct the transactions a protocol expects, so integrating with a Cardano dApp stops meaning reverse-engineering its datum formats by hand. Cardano's eUTxO model gives strong guarantees but a steep integration curve, and shared transaction-level standards are one of the few levers that genuinely flatten it for every team at once. This is the largest of the TxPipe asks (1,684,050 ADA), reflecting new build work rather than pure maintenance, but it was vetted and approved through the Intersect community budget process alongside the rest of TxPipe's portfolio and is disbursed under milestone-based administration. Consistent with Socious's policy of supporting budget-process withdrawals, we vote Yes.
Sociousは賛成します。Tx3はTxPipeによるdAppプロトコル向けのオープンAPIレイヤーです。プロトコルが期待するトランザクションをアプリケーションが記述・構築するための標準的な方法を提供し、CardanoのdAppとの統合が「datum形式を手作業でリバースエンジニアリングする作業」でなくなることを目指します。CardanoのeUTxOモデルは強い保証を与える一方で統合の学習曲線が急であり、トランザクションレベルの共有標準は、それを全チームに対して同時に平坦化できる数少ないレバーの一つです。TxPipe案件の中では最大の1,684,050 ADAで、純粋な保守ではなく新規構築を含みますが、TxPipeの他案件とともにIntersectのコミュニティ予算プロセスで審査・承認され、マイルストーンベースの管理下で執行されます。予算プロセスを経た引き出しを支持する方針に沿い、賛成します。
- No31.4M ₳Rationale
I vote NO.
I recognize the value of Tx3 and TxPipe’s strong track record, and I understand the importance of standardized, agent‑ready interfaces for Cardano’s future.
That said, given the current Treasury balance and Net Change Limit utilization, I cannot support funding for initiatives that are not strictly essential to Cardano’s operational continuity. To preserve long‑term financial sustainability and prioritize life‑support infrastructure, I must vote against this proposal. - No28M ₳No rationale
- Yes27.9M ₳Rationale
TxPipe maintains some of the highest-quality and most-used tools for developers on Cardano. The modest ask is very reasonable, so this is an easy YES for me.
- Yes27.2M ₳No rationale
- YesRevoted26.1M ₳History
Earlier votes
Yes1mo agoSuperseded
Improves developer experience and lowers integration friction for Cardano applications.
- Yes25.3M ₳Rationale
I am voting YES to Withdraw 1,684,050 ada for Tx3 by TxPipe. I think this will enhance the developer experience while better aligning Cardanop to capitalize on agentic commerce.
- Yes23.6M ₳Rationale
Tx3 was used for the buidler fest sign up. It greatly simplifies most chain interactions.
- Yes21.5M ₳Rationale
This vote corresponds with my previous vote on the Hydra Voting platform.
- Yes21.4M ₳No rationale
- Yes20.9M ₳No rationale
- Abstain20.4M ₳No rationale
- Yes20.3M ₳No rationale
- Yes20M ₳Rationale
As voted in Ekklesia, I vote yes on this proposal. I had hoped Intersect would bundle the winning proposals in one.
- Yes17.4M ₳Rationale
Withdraw 1,684,050 ada for Tx3 by TxPipe: Open API Layer for Cardano's dApp P...
- Yes16.9M ₳Rationale
We originally voted YES on Tx3 during the Intersect Budget process, and we maintain that position.
Tx3 addresses a real developer-experience problem on Cardano: each dApp protocol often requires custom integration work, which increases friction for wallets, builders, tooling providers, and eventually AI agents. A shared open API layer for Cardano dApp protocols can make integrations more reusable, composable, and easier to maintain.
We also recognize TxPipe’s strong delivery record and the fact that this proposal builds on their broader open-source infrastructure stack. While Tx3 is more forward-looking than pure maintenance proposals, it has clear public-good potential if adopted by multiple protocols and developer tools.
We would still like to see strong reporting on protocol onboarding, real developer usage, SDK adoption, MCP usage, and long-term maintenance needs. However, we believe the strategic value and open infrastructure nature of the work justify support.
- Yes10.9M ₳No rationale
- Yes10.4M ₳No rationale
- Yes8.6M ₳Rationale
Tx3はCardanoのdAppプロトコル向けに標準化されたオープンAPIレイヤーを提供し、開発者の利便性とプロトコル間の相互運用性を高める基盤です。AIエージェント対応を含むオープンソースの公共インフラとしてエコシステム全体への価値が高いと判断し、本提案に賛成します。\n\nTx3 provides a standardized open API layer for Cardano dApp protocols, serving as a foundation that improves the developer experience and interoperability across protocols. I support this proposal because I believe it provides significant value to the Cardano ecosystem as open-source public infrastructure, including support for AI agents.
- Yes7.4M ₳Rationale
Voting YES on the 5 TxPipe proposals.
I voted YES on 4 TXPipe proposals and NO on the TX3 proposal on Ekklesia. However, I have decided to vote YES on the TX3 proposal as well, as it adds a new interface description format for UTxO blockchain protocols, plus the associated tooling
- Abstain7.2M ₳No rationale
- Yes5.9M ₳Rationale
Consistent with my 2026 Intersect budget process votes, I am voting YES. This is part of the bulk proposals submitted by Intersect from that process.
Hydra Evidence IPFS: https://bafybeie6yykngvn5xsq6va6nwz3sdeadgxd45yhsoeqpuiyxh4tky5tuzi.ipfs.inbrowser.link/
X-Post: https://x.com/mr_cata/status/2063660464450527709?s=20 - Yes5.7M ₳No rationale
- Yes5.4M ₳No rationale
- Yes5.4M ₳No rationale