Withdraw ₳1,161,000 for zkFold ZK Rollup administered by Intersect
191 DReps voted · 58 with a rationale · 9 changed their vote
Open a row to read the rationale.
- Yes208.3K ₳No rationale
- Yes191.1K ₳No rationale
- Yes185.6K ₳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.
- Yes178.9K ₳No rationale
- No147.5K ₳No rationale
- Yes138.4K ₳No rationale
- Yes137.4K ₳No rationale
- Yes133.7K ₳No rationale
- Yes129.1K ₳No rationale
- Yes110.9K ₳No rationale
- Yes108.3K ₳Rationale
I am voting in favor of approving the treasury withdrawal for all 39 withdrawal actions that are part of the approved ecosystem budget administered by Intersect. I am voting this way for several reasons, as I will outline here. This rationale will be included in all 39 withdrawal votes.
First and foremost, I believe that we would be making a mistake in underfunding our community with our available treasury funds. The budget system as it currently stands has some flaws, as should be expected from a first version of any system. Of the current proposals, I voted to include several in the budget when it was being formed; however, I also did not vote in favor of several others. This is, of course, the case for most DReps. If I were to vote only for the proposals I initially favoured, and all other DReps did the same, we would likely approve only 2 or 3 proposals out of 39 due to the vote split. In my view, this is not an acceptable outcome for the community, and this is why I was also opposed to the idea of having 39 separate treasury withdrawal actions. I have reviewed all 39 requests, and they all have merit. Are they exactly in line with the priorities I wanted as part of the initial budget? No. Is that reason enough to vote no on several of these and end up approving only 2 or 3 proposals in the end? I certainly don't believe so.
In addition to this, the total amount of the intersect budget is roughly 10% higher than what I voted for, and I find that to be within an acceptable margin to approve all the withdrawals.
The individual proposals also all received at least 50% community approval to be included and will be subject to reviews and milestones to receive funds.
For these reasons, I am casting my vote to approve and am wishing the best of luck to all the teams waiting for funding through this process. - Yes103.1K ₳No rationale
- Yes92.6K ₳No rationale
- Abstain71.3K ₳No rationale
- Yes68.8K ₳Rationale
- Yes65.7K ₳No rationale
- Yes58.6K ₳Rationale
Zero-knowledge tech is vital for future private transactions and scalable L2s.
Please ensure clear audit timeline, developer SDK deliverables, and public testnet targets are published during Q1 disbursements. - Yes55.9K ₳No rationale
- Yes50.5K ₳No rationale
- Yes49.6K ₳No rationale
- Yes48.6K ₳No rationale
- Yes46.5K ₳No rationale
- No45.2K ₳No rationale
- Yes36.3K ₳No rationale
- Yes36.3K ₳Rationale
✅ zkFold ZK Rollup – ₳1,161,000
Why I voted YES:
zkFold is building a general-purpose ZK rollup solution to scale Cardano without compromising decentralization or security. Their prototype already proves it fits within on-chain execution limits. This tech compresses hundreds of smart contract transactions into a single L1 transaction, paving the way for massive dApp scalability.Key benefits:
• ⚡️ Higher throughput
• 💸 Lower fees for users and dApps
• 🔐 Preserves L1 security guarantees
• 📈 Enables micro-payments and broader adoption
• 🔧 Built by expert Rust, Haskell, and ZK cryptography engineersWith L2 scaling being mission-critical, this proposal supports a key infrastructure pillar for Cardano’s future.
- Yes14.3K ₳No rationale
- Yes10.6K ₳Rationale
I vote for this proposal
- Yes8.3K ₳No rationale
- Yes6.7K ₳No rationale
- No4.8K ₳No rationale
- Abstain2.5K ₳No rationale
- Yes1.7K ₳No rationale
- Yes1.6K ₳No rationale
- Yes335.3 ₳No rationale
- Yes13.5 ₳No rationale
- Yes6.3 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale
- YesRevoted0 ₳History
Earlier votes
Yes0y agoSuperseded