Withdraw ₳199,911 for OpShin - Python Smart Contracts for Cardano
153 DReps voted · 45 with a rationale
Open a row to read the rationale.
- Yes 654.5K ₳ No rationale
- Yes 624.8K ₳ Rationale
I have voted in favor of this action to demonstrates my intention to execute without delays and move the treasury expenditure process forward. I also want to note that I will not seriously consider individual requests from the treasury for less that 1,500,000 ADA moving forward. I reserve the right this round because I feel the process was not properly explained to proposers and DRep and it would be unfair to implement this personal guardrail at this time. Requests below that threshold are better suited for Catalyst funding or bundled together in MBO, DAO, or conglomerate entities. TWA (Treasury Withdrawal Actions) need be comprehensive and not ad hoc as that makes oversight more costly and inefficient.
A budget and all included line items has already been approved, and now is the time to disperse funding and enable further development of the Cardano network. The proposal was selected through a well-defined process, and I will fully support it out of respect for the will of the broader Cardano community and a belief in respecting the consensus we achieved together under the Intersect-administered budget process. The process reflects a coordinated, strategic approach to funding Cardano’s ecosystem-critical infrastructure. The community has thoroughly reviewed the proposal. I was actively involved in the entire process and the proposal presented represents development that provides a tangible benefit to our ecosystem. It would be a mistake to underfund our ecosystem’s development when we can sustainably provide the required funding with our available treasury reserves.
Furthermore there are exceptional oversight mechanisms in place to ensure a minimum amount of wast, fraud, and abuse of treasury expenditures, such as Intersect’s smart contract framework (audited by TxPipe and MLabs), Multi-party oversight (including Cardano Foundation, Sundae Labs, NMKR, etc.), A clear milestone-driven disbursement model, and full transparency via TRSC/PSSC dashboards.
These governance and assurance systems meet the constitutional standards for accountability and risk management and provide confidence in efficiency and execution. - Yes 589.2K ₳ No rationale
- Yes 587.1K ₳ Rationale
I vote YES on the OpShin proposal because it significantly lowers the barrier to entry for smart contract development on Cardano by allowing developers to write contracts in Python—one of the most widely used and beginner-friendly languages in the world. This accessibility will accelerate DApp development, especially for developers coming from Web2 backgrounds who may not be familiar with Haskell or Aiken.
Moreover, the project is already functional and used within the ecosystem, with an active and doxed lead developer, showing clear traction and credibility. Supporting OpShin aligns with Cardano’s strategic goal of expanding its developer base and fostering broader adoption. The continued maintenance and evolution of OpShin are vital as Cardano's smart contract standards progress. Funding this initiative ensures Cardano remains a competitive and developer-friendly blockchain platform.
- Yes 559.5K ₳ No rationale
- Yes 502K ₳ Rationale
When i first read this, i thought " Whoa, are you sure?" Python's dynamic nature fights against everything we've learned about smart contract safety. The "strict typing" overlay feels like putting a safety harness on a motorcycle, better than nothing, but you're still on a motorcycle. haha. Initially I was going to vote no on this, but I changed my mind because you know what? I might be have been overthinking the security concerns on OpShin. Python is the second most popular language on GitHub with a 22.5% year-over-year growth rate. That's a massive developer pool we're currently excluding from Cardano. And Niels has been working on this for a while - it's not some weekend hackathon project.
The strict typing system on top of Python type hints is actually clever. They're getting the accessibility of Python syntax while enforcing the safety guarantees we need for smart contracts. Plus, all the typing gets erased during compilation for efficiency - that's solid engineering.
My concern about Python's dynamic nature might be overblown since they're essentially using Python as a higher-level syntax that compiles down to safe Plutus Core. It's not like they're running raw Python on-chain.
For ₳199,911, we could potentially unlock thousands of Python developers who are currently intimidated by Haskell or even Aiken. That ROI on developer onboarding could be massive. I am still open to change my mind on this if anyone thinks otherwise on this as my technical know how might be limited, but as of now i think this is a great win for cardano if we implement it the right way. - Yes 466.2K ₳ No rationale
- Yes 445.1K ₳ No rationale
- Yes 443.5K ₳ No rationale
- Yes 385.6K ₳ Rationale
Krypto Labs have taken part in the budget debates and agree with proposer that this is something the Cardano blockchain ecosystem need.
I started with making a rationale and arguement for each proposal, but to save time i need to do bulk voting to speed this prosess up. - Yes 382.6K ₳ No rationale
- Yes 377.3K ₳ No rationale
- Abstain 371.8K ₳ No rationale
- Yes 314.4K ₳ Rationale
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
In alignment with my voting on the 2025 Cardano Budget Reconciliation process through Ekklesia platform, I support this withdrawal and therefore vote YES.
- Yes 298.6K ₳ Rationale
I'm defaulting to voting yes because there is some degree of consensus already achieved on each of these. So unless I have a significant issue with one of these proposals I will be voting yes on it.
- Yes 271.5K ₳ No rationale
- Yes 262.3K ₳ No rationale
- Abstain 258.6K ₳ Rationale
This vote was submitted based on a completed checklist. A detailed rationale is available at:
👉 https://github.com/Agora-Cardano - Yes 257K ₳ Rationale
After careful assessment of the "Withdraw ₳199,911 for OpShin - Python Smart Contracts for Cardano" proposal, I am voting YES based on the following considerations:
Strategic Alignment:
The proposal promotes expanding the Cardano smart contract ecosystem by supporting OpShin’s development of Python-based smart contracts. Offering additional smart contract language support, specifically in a widely-used language like Python, directly aligns with Cardano’s goals to increase developer accessibility, adoption, and ecosystem growth. It enhances developer experience and lowers the entry barrier for smart contract development on Cardano.Ecosystem Diversification and Inclusion:
Supporting smart contracts beyond Plutus/VHDL/Haskell strengthens the network’s inclusivity and innovation capacity. Python’s large developer community and familiar programming paradigms offer a compelling opportunity for onboarding new developers into the Cardano ecosystem, potentially accelerating real-world dApp creation.Technical Merit and Track Record:
OpShin has demonstrated steady progress and a clear roadmap for continued Python smart contract development with sound technical foundations. The funding requested is aligned with achieving tangible milestones and delivering a production-ready toolset. This will enable broader developer engagement and ecosystem tooling expansion.Reasonable Funding and Oversight:
The requested withdrawal amount of ₳199,911 is appropriate for the scope and stage of the project. It reflects a responsible and proportional investment in the further development of essential programming infrastructure without undue risk or overlap with other funded efforts.Transparency and Deliverables:
The proposal sets forth clear deliverables, including secure smart contract execution, integration with existing Cardano toolchains, and comprehensive documentation. The progress will be verifiable within the governance framework and subject to the community oversight and milestone assurance protocols.
In summary, supporting OpShin's Python smart contracts development is a strategic step toward fostering a more diverse and accessible developer ecosystem on Cardano. It complements existing initiatives by enabling smart contract development in a broadly used programming language, ultimately accelerating Cardano’s mission for widespread blockchain adoption.
Therefore, I endorse funding this withdrawal and will vote YES.
- Yes 252.6K ₳ No rationale
- No 245K ₳ No rationale
- Yes 238.2K ₳ No rationale
- No 208.6K ₳ Rationale
While I acknowledge the potential of OpShin to broaden developer accessibility by leveraging Python’s popularity and ease of use, I believe the Cardano ecosystem should prioritize maintaining a high technical standard for smart contract development.Cardano’s strength lies in its robust, secure, and formally verified smart contract framework, primarily built on Haskell and Plutus. These tools, though challenging to learn, ensure a level of rigor and reliability critical for decentralized applications handling significant financial and operational responsibilities. Lowering the technical barrier through Python-based solutions like OpShin risks diluting this standard by attracting developers who may lack the depth of expertise required to build secure and efficient smart contracts.While Python’s accessibility could onboard more developers, the proposal does not sufficiently address how OpShin will maintain the same level of security and performance as PlutusTx, beyond general claims of efficiency and type erasure. The Cardano ecosystem benefits most from developers who are willing to meet its high technical demands, ensuring the integrity and scalability of the network. Prioritizing accessibility over technical excellence may compromise the long-term quality of the ecosystem.
- Yes 190.2K ₳ No rationale
- Yes 184.4K ₳ Rationale
I am voting yes on all 39 Intersect Governance actions. The community has thoroughly reviewed the many proposals presented in the Intersect Budget Process for the 2025 budget. I was deeply involved in the entire process as an SME for the Budget Committee, and then as the Secretary for the Budget Committee.
The proposals presented represent an incredible amount of development for our ecosystem for the next year. The teams all received at least 50% on Ekklesia polling. The teams will face milestones in order to continue to receive funding. If a team fails to deliver, the process will stop them from enriching themselves without returning value.
If anything, we are spending too little on our community. We need to spend more to further develop our governance and our organized events. This is a liquid democracy. If you believe that all of these proposals deserve a chance to deliver, you can shift your delegation to my DRep ID.
- Yes 180.9K ₳ No rationale
- No 177.6K ₳ No rationale
- Yes 143.9K ₳ No rationale
- Yes 137.3K ₳ No rationale
- Yes 111.7K ₳ No rationale
- Yes 103K ₳ No rationale
- Yes 88.7K ₳ No rationale
- Yes 64.7K ₳ No rationale
- Yes 61.9K ₳ No rationale
- No 59.6K ₳ No rationale
- Yes 58.6K ₳ No rationale
- Yes 55.9K ₳ No rationale
- Yes 53K ₳ No rationale
- Yes 49.3K ₳ No rationale
- Yes 48.5K ₳ No rationale
- Yes 48.4K ₳ No rationale
- Yes 45.2K ₳ No rationale
- Yes 36.2K ₳ No rationale
- No 14.3K ₳ No rationale
- Yes 6.8K ₳ No rationale
- Yes 4.1K ₳ No rationale
- Yes 1.6K ₳ No rationale
- Abstain 335.1 ₳ No rationale
- Yes 13.5 ₳ No rationale
- Yes 0 ₳ No rationale