DRep Votes
Epoch Snapshot 575
  • Total Stake: ₳ 12.91B
  • Yes Votes (Stake)
    ₳ 3.65B
  • Total No (Stake)
    ₳ 1.62B
    Explicit No
    ₳ 363.97M
    No Confidence
    ₳ 171.35M
    Not Voted
    ₳ 1.08B
  • Total Abstain (Stake)
    ₳ 7.64B
    Explicit Abstain
    ₳ 290.91M
    Auto Abstain
    ₳ 7.35B
  • Total Committee Members: 7
  • Yes Votes
    7
  • Total No
    0
    Voted No
    0
    Not Voted
    0
  • Abstain Votes
    0

Abstract

This treasury withdrawal funds PyCardano which will provide the following services: ​

PyCardano is a lightweight Python library that enables developers to interact seamlessly with the Cardano blockchain. It facilitates the creation and signing of transactions without reliance on external serialization tools, thereby simplifying the development process and broadening accessibility for Python developers. Given the dynamic nature of blockchain technology, particularly with Cardano's ongoing protocol upgrades and hard forks, it is imperative to maintain and update PyCardano to ensure continuous compatibility and functionality.​

This proposal aims to:

Ensure Compatibility: Regularly update PyCardano to align with the latest Cardano ledger rules and protocol changes, including upcoming hard forks in 2025.​

Enhance Reliability: Promptly identify and resolve bugs within PyCardano to maintain a robust and dependable library for developers for 12 months since the proposal is funded.​

Foster Community Engagement: Collaborate with the Cardano developer community to gather feedback, address issues, and implement improvements effectively.

This Treasury Withdrawal is submitted by Intersect on behalf of the vendor. The following sections; Abstract, Motivation, Rationale and Vendor Profile have been sourced from the approved proposal submitted by the Vendor as part of the Intersect budget process.

This treasury withdrawal funds one of 39 proposals to give effect to the approved budget info action for ₳275,269,340, administered by Intersect via gov_action1u9x73kwufaxa70lfy59g4ynwyrcsaxdcd0gxzzmh67s9fxq4j8hqqk2phgh. The information provided herein is intended to fulfill the spirit of the constitutional requirement for a treasury withdrawal info action by also providing the details of the proposed solution, alignment to the budget, and amount to be withdrawn from the Cardano Treasury.

Motivation

This proposal aims to solve the following problem:

The Cardano ecosystem primarily offers development tools and libraries in Haskell and JavaScript, creating a significant barrier for Python developers who wish to engage with the platform. This limitation hinders the growth and diversification of the developer community within the Cardano ecosystem. Furthermore, existing tools often depend on external serialization libraries, complicating the development process and potentially introducing additional points of failure. The absence of a native Python library that seamlessly integrates with Cardano's infrastructure restricts the ability of developers to build and deploy applications efficiently.

Rationale

Project Solution

PyCardano is a Python library designed to facilitate interaction with the Cardano blockchain by enabling users to create and sign transactions without relying on third-party serialization tools. This independence makes PyCardano lightweight and easy to set up across various environments. ​

Developing PyCardano addresses the challenges mentioned above by providing a native Python library tailored for the Cardano blockchain. This initiative aims to lower the entry barrier for Python developers, fostering a more inclusive and diverse developer community. By eliminating the need for third-party serialization tools, PyCardano simplifies the development workflow, enhancing both efficiency and reliability. This project not only broadens the accessibility of Cardano to a wider range of developers but also encourages innovation and the creation of new applications within the ecosystem.​

By implementing this proposal, we anticipate the following outcomes:

Sustained Compatibility: PyCardano will remain compatible with the latest Cardano protocol versions, enabling developers to build and maintain applications without disruption.​ Although there isn't a clearly specified roadmap or hardfork for Cardano in the next 12 months, we know it is likely that there will be Leios and Midnight integration. These integration and changes will more or less require corresponding updates in PyCardano.

https://iohk.io/en/research/library/papers/ouroboros-leios-design-goals-and-concepts/

https://midnight.network/

Improved Stability: Ongoing maintenance and prompt bug fixes will enhance the library's stability and reliability.​

Enhanced Developer Experience: Up-to-date documentation and community support will provide a more accessible and user-friendly experience for developers.​

Community Growth: Active engagement with the developer community will foster collaboration, innovation, and the broader adoption of PyCardano.

Vendor Profile

Jerry, the creator of PyCardano, will lead this project. His deep understanding of both the library and Cardano's ecosystem makes him uniquely qualified to oversee this upgrade.

Jerry's experience as a blockchain developer ensures that the technical challenges of aligning with the Chang hardfork can be effectively addressed.

Track Record:

The success of PyCardano, with over 170 dependent projects on GitHub and 7,000+ monthly downloads, demonstrates our team's ability to create and maintain critical infrastructure for the Cardano ecosystem.

The active Discord community (100+ members) shows our ongoing engagement with users and our ability to address their needs.

Technical Expertise:

Our team's familiarity with Cardano's protocol, combined with expertise in Python development, positions us to efficiently implement the necessary upgrades.

We have a history of successfully adapting PyCardano to previous Cardano updates, showcasing our ability to respond to network changes.

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.

References

Proposal Information
  • Type
    Treasury Withdrawal
  • Status
    Enacted
  • Submitted On
    Jul 18, 2025
  • Enacted On
    Aug 12, 2025
  • Proposal Tx
  • Voting Parties
    DRepCC