Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026
158 DReps voted · 51 with a rationale · 3 changed their vote
Open a row to read the rationale.
- Yes575M ₳Rationale
Yoroi DRep votes YES on Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026. 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,310,960 ada for Hardware Wallet Maintenance 2026, 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
- No171.3M ₳No rationale
- No123.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
- Yes90.6M ₳Rationale
As a DRep, I vote YES on the proposal: Hardware Wallet Maintenance 2026.
My rationale:
Hardware-wallet support is part of Cardano’s basic security and access infrastructure. Many users rely on Ledger and Trezor devices to securely hold and use ADA and Cardano native assets. If hardware-wallet compatibility breaks, users may lose practical access to secure signing, wallets and dApps may face integration problems, and Cardano’s user experience would suffer.
This is a continuity proposal focused on maintenance, compatibility, supporting libraries, cardano-hw-cli, and developer support for integrations. In my view, this is a reasonable and necessary scope.
I also consider the budget acceptable. The total request is ₳1,310,960. For 12 months of specialized maintenance on a security-critical layer used by the ecosystem, this does not appear excessive.
The vendor has relevant prior experience and a proven track record in this area. Repeated funding is normally something I examine carefully, but maintenance of critical infrastructure is naturally recurring.
Cardano users should not discover hardware-wallet maintenance problems only after something breaks. Preventive maintenance is cheaper, safer, and less disruptive than emergency repair.
For these reasons, I vote YES.
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.6M ₳No rationale
- Yes88.4M ₳Rationale
SIPO DRep votes YES, with expectations, on the treasury withdrawal of 1,310,960 ada for Hardware Wallet Maintenance 2026.
Why SIPO votes Yes. Hardware wallet support is the layer where custody actually meets users. It is maintenance work that no single vendor fully internalizes, and its failure mode is borne directly by holders. Keeping it funded and current is a baseline obligation of a self-custody ecosystem.
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 として、Hardware Wallet Maintenance 2026（1,310,960 ada）のトレジャリー引き出しに、期待事項付きで賛成（YES）を投じます。
SIPO が賛成する理由。ハードウェアウォレット対応は、カストディが実際にユーザーと接する層です。どの一社も完全には内部化しない保守作業であり、その破綻は保有者が直接負います。これを資金面で維持し最新に保つことは、セルフカストディのエコシステムにとって基礎的な責務です。
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 の記録上の立場表明です。
- Yes85M ₳Rationale
Hardware wallet maintenance is absolutely essential for the ecosystem. At this price, this is an easy "YES".
- Abstain76.7M ₳No rationale
- Yes75.9M ₳Rationale
I support this proposal because it focuses on maintaining, securing, and ensuring the continued compatibility of Cardano's hardware wallet ecosystem rather than developing a new wallet product.
Hardware wallets such as Ledger and Trezor are a critical security layer for Cardano users. Maintaining compatibility with protocol upgrades, firmware changes, and vendor requirements helps ensure that users, developers, wallets, and dApps continue to have reliable and secure access to the network.
Preventive maintenance is also far more effective than reacting after compatibility issues disrupt users or ecosystem integrations.
I encourage continued transparency through milestone reporting and measurable maintenance outcomes. Overall, I believe this proposal represents an important investment in Cardano's security and long-term reliability, and I vote Yes.
本提案は、新しいウォレットを開発するものではなく、LedgerやTrezorなどのハードウェアウォレットがCardanoのプロトコル更新や各ベンダーの変更後も、安全かつ継続的に利用できるよう維持・保守することを目的としています。
ハードウェアウォレットは、ユーザー資産を安全に管理するための重要なインフラです。互換性の維持やセキュリティ対応を継続することは、ユーザーだけでなく、ウォレット、dApp、開発者を含むエコシステム全体に利益をもたらします。
また、不具合が発生してから対応するよりも、継続的な保守によって互換性を維持する方が、安全性・コストの両面で合理的であると考えます。
今後も進捗状況や対応内容について透明性の高い報告を期待しますが、本提案はCardanoのセキュリティと信頼性を支える重要な公共インフラへの投資であると判断し、賛成します。
- Yes74.6M ₳No rationale
- Yes73.6M ₳Rationale
I am voting YES on the Hardware Wallet Maintenance 2026 treasury withdrawal. Maintaining continuous Ledger and Trezor compatibility is absolutely critical to ensuring users and developers retain secure and unbroken access to the Cardano network.
A PDF version of this rationale is also made available.
I am voting YES on the Hardware Wallet Maintenance 2026 treasury withdrawal. Maintaining continuous Ledger and Trezor compatibility is absolutely critical to ensuring users and developers retain secure and unbroken access to the Cardano network. Funding this preventative maintenance guarantees that future protocol upgrades or vendor firmware changes will not break our most essential security access layer, especially in the current climate of advanced AI.
- Yes69.3M ₳No rationale
- Yes62.7M ₳No rationale
- Yes53.8M ₳Rationale
I am voting Yes on the Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026 proposal.
This proposal is a small budget to maintain that compatibility layer for twelve months, and I support it because it secures the continuity of an already-proven access layer rather than building a new product.
The timing is also appropriate, given that protocol changes such as the recent Van Rossem hard fork are exactly what tends to break this compatibility.
Since this maintenance is not a company's commercial product but public signing infrastructure that everyone relies on, I consider Treasury support justified at this stage.
That said, this Yes does not assume open-ended subsidy.
As this item has already received Treasury funding several times, I believe the level of support should be reviewed if future requests grow excessively, and that over the long term it should transition toward the vendor and the wallet ecosystem sharing these costs.
- 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
- No50.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), 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/
- Yes50.2M ₳Rationale
Same rationale as the one presented for the Intersect budget.
- No49.5M ₳No rationale
- Yes47.5M ₳No rationale
- No39.9M ₳No rationale
- Abstain37.4M ₳No rationale
- Yes37.3M ₳No rationale
- No34.5M ₳No rationale
- Yes34.4M ₳Rationale
Socious votes Yes. This 1,310,960 ADA withdrawal funds hardware wallet maintenance for 2026 — keeping Cardano's hardware-wallet integrations current as the protocol evolves, so that signing support for new transaction features (including governance actions themselves) keeps working across device firmware and API changes. Hardware wallets are how the most security-conscious holders — often the largest ones — custody ADA and vote; if this integration layer lags a hard fork, those users are locked out of new protocol features or pushed onto hot wallets, which is a security regression for exactly the wrong cohort. This is unglamorous, security-critical maintenance, vetted and approved through the Intersect community budget process and disbursed under its milestone-based administration. Consistent with Socious's policy of supporting budget-process withdrawals, we vote Yes.
Sociousは賛成します。本引き出し（1,310,960 ADA）は2026年のハードウェアウォレット保守に資金を供給します。プロトコルの進化に合わせてCardanoのハードウェアウォレット統合を最新に保ち、新しいトランザクション機能（ガバナンスアクション自体を含む）への署名対応がデバイスのファームウェアやAPIの変更をまたいで機能し続けるようにするものです。ハードウェアウォレットは、最もセキュリティ意識の高い保有者 — 多くの場合最大の保有者 — がADAを管理し投票する手段であり、この統合レイヤーがハードフォークに遅れれば、そうした利用者は新機能から締め出されるかホットウォレットへの移行を強いられ、まさに最も望ましくない層でのセキュリティ後退となります。地味だがセキュリティ上重要な保守であり、Intersectのコミュニティ予算プロセスで審査・承認され、マイルストーンベースの管理下で執行されます。予算プロセスを経た引き出しを支持する方針に沿い、賛成します。
- Yes31.4M ₳Rationale
Hardware wallet maintenance is essential infrastructure that preserves secure user access, signing reliability, and compatibility as Cardano, Ledger, and Trezor evolve. Breakage in hardware‑wallet flows directly impacts user safety, developer integrations, and ecosystem utility. The requested amount is modest, the scope is clear, and the work maintains critical security infrastructure rather than expanding new functionality. Strong governance controls, milestone‑based drawdowns, and independent oversight further reinforce accountability. As this proposal protects core user‑access infrastructure without increasing Treasury depletion risk, I vote YES.
- Yes30.6M ₳No rationale
- No28M ₳No rationale
- Yes27.9M ₳Rationale
If the recent SecondFi hack taught us anything, it's that we should not rely on hot wallets to protect the private key controlling our assets. Continued support for hardware wallets is a must-have.
- Yes27.2M ₳No rationale
- YesRevoted26.1M ₳History
Earlier votes
Yes1mo agoSuperseded
- Yes25.3M ₳Rationale
I am voting YES on Withdraw 1,310,960 ada for Hardware Wallet Maintenance. Ensuring support with major hardware wallets is essential to ecosystem resiliancy.
- Yes23.6M ₳Rationale
Hardware wallets are generally good.
- 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.
- Yes18.2M ₳No rationale
- Yes17.4M ₳Rationale
Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026
- Yes16.9M ₳Rationale
We support this proposal because hardware wallet compatibility is security-critical infrastructure for Cardano users and builders.
Ledger and Trezor support must be maintained continuously as Cardano, wallet software, firmware, and vendor requirements evolve. If this layer breaks, users can lose secure access to staking, governance, payments, DeFi, and dApp interactions.
This is not a new commercial product. It is maintenance of an already-proven access layer: compatibility updates, supporting libraries, tooling, developer support, release support, and vendor-required assurance work.
The request is reasonable for the scope, and the work fits the type of ecosystem infrastructure the treasury should support.
- Yes14.1M ₳No rationale
- Yes13.3M ₳Rationale
RCADA votes YES on Withdraw 1,310,960 ada for Hardware Wallet Maintenance 2026.
RCADA supports this proposal because hardware-wallet compatibility is a security-critical access layer for Cardano. Users rely on hardware wallets for secure signing, staking, governance participation, DeFi, payments, and everyday self-custody. If Ledger or Trezor support falls behind Cardano protocol changes, firmware updates, or wallet and dApp integration needs, users and builders can face avoidable disruption.
This proposal is clearly focused on continuity rather than speculative new development. It funds 12 months of maintenance for Cardano hardware-wallet support, including Ledger and Trezor compatibility updates, supporting interoperability libraries,
cardano-hw-cli, developer support for ecosystem integrators, release support, and vendor-required audit or assurance work where needed.RCADA views this as important public-good infrastructure. Hardware-wallet support benefits the wider ecosystem, including users, wallets, dApps, builders, and institutions that depend on secure self-custody flows. Maintaining this layer proactively is preferable to waiting until compatibility breaks and then reacting after users lose access or integrations fail.
The governance and administration structure is also positive. This withdrawal passed the required Intersect Budget Process support threshold and will use the 2026 Treasury management smart contract framework, including oversight, milestone-based disbursement controls, and public dashboard visibility.
The requested amount of 1,310,960 ADA is larger than some maintenance proposals, so RCADA expects clear reporting and evidence of value delivered. This should include visible compatibility work, release updates, audit or vendor-assurance evidence where applicable, issue resolution, integrator support, and transparent capped time-and-materials reporting.
On balance, this proposal supports security, interoperability, developer experience, and user confidence in Cardano’s self-custody infrastructure. It is clearly scoped, process-approved, and focused on maintaining a proven access layer that many users and builders depend on.
RCADA's full vote assessment can be found here:
https://brolloks.github.io/rcada-drep-votes/