Withdraw ₳199,911 for OpShin - Python Smart Contracts for Cardano
153 DReps voted · 51 with a rationale · 1 changed their vote · 5 re-voted unchanged
Open a row to read the rationale.
Changed votes: 1 to yes, together voting with 223.1M ₳ of voting power.
- Yes6.7M ₳No rationale
- Yes6.5M ₳No rationale
- Yes5.7M ₳No rationale
- Yes5.7M ₳No rationale
- YesRevoted5.5M ₳Rationale
Python's widespread use and importance justify supporting smart contract tooling for Python developers. I endorse this proposal to enhance Cardano's accessibility and functionality for the Python developer community.
Earlier votes
Yes1y agoSuperseded
Python's widespread use and importance justify supporting smart contract tooling for Python developers. I endorse this proposal to enhance Cardano's accessibility and functionality for the Python developer community.
- Yes5.5M ₳No rationale
- Yes5.3M ₳Rationale
OpShin lowers the barrier to entry for Cardano development by enabling smart contract creation in Python, one of the most widely used and accessible programming languages. This aligns with STORM Partners’ goals to attract talent, improve infrastructure efficiency, and broaden adoption. As an open-source and bootstrapped project, we believe it deserves treasury support to continue growing and evolving. We vote YES.
- No5.1M ₳No rationale
- Yes5.1M ₳No rationale
- Yes4.9M ₳No rationale
- Yes4.8M ₳Rationale
Python with dataclass and type-hint really makes it readable and maintainable. On-chain script with Python will drive the future DApp development in Cardano.
Python with dataclass and type-hint really makes it readable and maintainable. On-chain script with Python will drive the future DApp development in Cardano.
- Yes4.6M ₳No rationale
- Yes4.5M ₳No rationale
- Yes4M ₳No rationale
- Yes3.9M ₳Rationale
I vote YES because core engineering is the priority of my DRep account.
Strength and honor.
- Yes3.6M ₳No rationale
- Yes3.5M ₳No rationale
- Yes3.5M ₳No rationale
- Yes3M ₳No rationale
- Yes2.8M ₳No rationale
- Yes2.7M ₳Rationale
Python as the #2 used programming language on github, makes sense to support it especially with the project already being bootstrapped.
- Yes2.7M ₳Rationale
OpShinは、Pythonベースでスマートコントラクトを記述できるツールチェーンを提供することで、Haskell/Plutusに依存しない開発者参入のハードルを大幅に下げます。既にドキュメント・Pioneerプログラム・GitHub活動も整備されており、₳200K未満の支援で大きな波及効果が期待できるため賛成します。
OpShin lowers the entry barrier for smart contract development on Cardano by enabling Python-based development while retaining functional programming benefits. Given its maturity, documentation, and low cost, I vote in favor to expand accessibility and developer onboarding.
- No2.5M ₳Rationale
This looks more like a Catalyst proposal. Moreover, it lacks details and a budget breakdown, even though the requested amount is not the largest compared to others.
- Yes2.5M ₳No rationale
- Yes2.5M ₳No rationale
- Yes2.2M ₳No rationale
- Yes2.1M ₳No rationale
- Yes1.9M ₳No rationale
- Yes1.7M ₳No rationale
- Yes1.6M ₳No rationale
- Yes1.6M ₳Rationale
I decided to vote ✅ YES on 37 treasury withdrawals, ➖ ABSTAIN on none, and ❌ NO on 2 treasury withdrawals from the Intersect 2025 budget.
It’s obvious I consider all proposals I approved in the budget vote on Ekklesia beneficial for Cardano, so those all receive a ✅ YES vote.
I also vote ✅ YES for most proposals I initially abstained from or voted against in the Ekklesia vote. There are a few reasons for this:
- Some proposals gained strong community support after all, so I don’t want to be the one standing in the way, especially when the requested amount is negligible in the bigger picture.
- Some proposals I actually liked, but I found them more suitable for Catalyst. However, with all the delays, it now makes more sense to fund them as soon as possible.
- Some didn’t get my initial support because I thought the requested amount was too high. But I now believe it’s better for the ecosystem to fund them, despite the larger budget, than not fund them at all.
- I needed to vote for budget proposals with my own NCL in mind. Not all those I approved made it, however, so that leaves some room for other ones.
I won’t approve the treasury withdrawal for two proposals:
❌ Withdraw ₳3,000,000 for High-yield RWA Asset for Cardano: Tokenized Real Estate
This proposal won’t bring much value to our ecosystem, imho.❌ Withdraw ₳1,500,000 for Complement Catalyst: Extended Quadratic Funding---Zero Operational Costs
While the proposal includes some interesting ideas for a fairer voting mechanism, I now support Catalyst and don’t see the need for an additional funding system at this moment, especially considering total spending. The requested amount also seems too small to meaningfully fund multiple projects. While the model relies on donations, it’s unclear what the donor incentive is. Since voting power is tied to donation size, why wouldn’t donors just support specific fundraisers run directly by the projects they care about? That way, they can ensure their contribution goes straight to their preferred initiative without needing it to win a vote first.
I do appreciate the idea of a hybrid funding model where the treasury covers part of a project, but ideally, the remaining portion should come from investors rather than donations, imho.
Lastly, I don’t appreciate that the proposal’s title refers to Catalyst, even though it has no relationship to it. This seems intended to mislead people into thinking Catalyst would benefit from this proposal, which it doesn’t...I acknowledge there’s a metadata issue in the proposal “Withdraw ₳45,217 for MLabs Core Tool Maintenance & Enhancement: Cardano.nix”, but I approved it nonetheless, as the problem is minor and not worth obstructing the process.
- Yes1.4M ₳No rationale
- Yes1.3M ₳Rationale
A couple of months ago, I supported the resolution to bundle all of the Intersect Budget Proposals into 1 or 2 formal on-chain governance votes.
Each of these proposals has already received 50% or greater support from the active DReps in the ecosystem, and I will honor that prior decision.
A PDF version of this rationale is also made available.
A couple of months ago, I supported the resolution to bundle all of the Intersect Budget Proposals into 1 or 2 formal on-chain governance votes.
Each of these proposals has already undergone extensive scrutiny and received 50% or greater support from the active DReps in the ecosystem, and I will honor that prior decision and the work these prospective developers have put in by voting yes on all the proposals from the Intersect Budget team.
- Yes1.2M ₳No rationale
- Yes1.2M ₳No rationale
- Yes1.2M ₳No rationale
- No1.2M ₳No rationale
- Yes1.1M ₳No rationale
- Yes1.1M ₳Rationale
I am voting Yes. Python is one of the most widely used programming languages globally, and supporting it lowers the barrier to entry for a vast pool of developers unfamiliar with Haskell or functional DSLs. The proposal demonstrates strong technical grounding and ecosystem alignment. At a modest cost, this initiative offers high potential impact by expanding Cardano’s developer base and fostering broader innovation.
- No1.1M ₳Rationale
I vote No on this treasury withdrawal. I urge the proposer to return with a refined proposal that includes:
- Clear, quantifiable milestones and KPIs aligned to ecosystem growth metrics;
- Independent performance benchmarks and security audits;
- A sustainability plan for post-funding continuation;
- Transparent mechanisms for milestone validation and community reporting.
- Yes951.2K ₳No rationale
- Yes929.9K ₳No rationale
- Yes927.7K ₳No rationale
- Yes888K ₳No rationale
- Yes884.5K ₳No rationale
- Yes796.1K ₳No rationale
- YesRevoted792.3K ₳Rationale
OpShin reduces the barrier to Cardano smart contracts by using Python. The maintainer is known. The tool is live and in use. The request is modest and covered by the approved 2025 budget. Funds keep the toolchain current with Plutus changes and standards. This backs core developer needs and ecosystem growth.
Earlier votes
Yes1y agoSuperseded
OpShin reduces the barrier to Cardano smart contracts by using Python. The maintainer is known. The tool is live and in use. The request is modest and covered by the approved 2025 budget. Funds keep the toolchain current with Plutus changes and standards. This backs core developer needs and ecosystem growth.
- Yes742.6K ₳No rationale
- Yes636.4K ₳No rationale
- Yes604.7K ₳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.