Withdraw ₳424,800 for Hardware Wallets Maintenance administered by Intersect

This proposal aims to solve the following problem:

Hardware wallets Ledger and Trezor and additional supporting tooling (cardano-hw-cli) need to be regularly updated in order to be able to support Cardano blockchain development.

There are 2 aspects of this:

• regular maintenance, bugfixing and developer support

• implementation of new Cardano features and breaking changes

HW wallets in scope: Ledger, Trezor, Keystone (from support perspective as Keystone firmware and tooling is developed by the Keystone team)

Currently it is not known which features in Cardano Roadmap will affect hardware wallets integrations.

Project Solution

If implementation of new Cardano features and breaking changes is not completed then hardware wallets may become incompatible with Cardano, stopping users from accessing newer blockchain features or stop working altogether.

If regular maintenance, bugfixing and developer support is not completed, wallets may lack functionalities and development of tooling that is using HW wallets may become impossible or much more difficult.

Vendor Profile

Vacuumlabs has been developing the Cardano HW wallets integrations (Ledger and Trezor) since 2018.

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.