Zcash Applications Lab: Open-Source Builder Initiative

[Michae2xl]

Zcash needs more working applications beyond private payments, and ZCG needs fewer idea-stage proposals to adjudicate. The Lab addresses both: a continuous, hackathon-style open-source program, operating within a capped budget and governed by a rotating community judge panel: that converts application ideas into shipping prototypes across non-payment verticals. Each sprint ships open-source code, a spec, and a community evaluation. The Lab operates as a lightweight triage and incubation layer upstream of full ZCG grants.

Why I decided to open this discussion

A week of conversations with institutional people who sold their business for $30M usd made the path clear: adoption will be hybrid. End users are not going to learn wallets, seed phrases, or L1s. They will continue using the traditional financial systems and interfaces they already trust. The right strategy is to push crypto into the plumbing ZK and privacy primitives, doing invisible work underneath surfaces the user already knows.

NOTE: Similar to (ZCG RFP - DeFi Strategist), but this is a deeper foundation.

---

Why now

• DeFi exploit cycle creates concrete pull for privacy-preserving alternatives.

• Institutional Demand Signals → Lab Verticals (complete mapping)
  

  
  
  The seven verticals are not arbitrary: they form the minimum covering set of the institutional privacy demand landscape. Every signal surfaced by regulators, financial institutions, and cross-border stakeholders maps cleanly to one (sometimes two) of these verticals. Cross-cutting signals justify the Lab’s emphasis on extracted, reusable SDKs: a single primitive serves multiple verticals, multiplying ROI per sprint.

• ZCG proposal volume makes a triage/incubation layer valuable immediately

Problem we are solving for the ecosystem and for ZCG

ZCG receives a high volume of proposals each cycle. Many are promising in concept but unproven in execution. Reviewing requires assessing the feasibility of work that has never been prototyped.

The result:

• Strong ideas stall because feasibility is hard to judge on paper
• Weaker ideas consume review cycles
• The application layer of Zcash progresses more slowly than the protocol layer
• Builders with good ideas but no funding path never reach the prototype stage

The ecosystem gap is clear: There is no dedicated place where ideas become working open-source code cheaply and publicly. Zcash has no equivalent applied builder lab.

How does this help ZCG directly?

• Pre-filter for grants: concepts arrive at ZCG after having a working code, not as pure ideas. Review cycles shorten.
• The community has the freedom to see which product gains the most traction globally.
  Funding is managed in the labs for limited amounts, so there will often be no funding for ZCG.
• De-risked grant decisions: ZCG reviewers can evaluate running prototypes instead of speculative proposals.
• Triage layer: forum ideas that need validation can be handed to the lab for a quick sprint instead of forcing ZCG to adjudicate on a blank page.
• Public artifact trail: even failed experiments ship open-source code and a write-up that the community can build on or fork.

Reference models

This model is not novel, it is proven elsewhere in crypto:

• 0xPARC (Ethereum): applied ZK research and open-source apps
• Privacy & Scaling Explorations (PSE): Ethereum Foundation’s applied lab
• Flashbots: open-source research and infrastructure
• Protocol Labs: incubator pattern for Filecoin ecosystem

Proof of Capability

• A ZK Credit Global using the Zcash Blockchain.

ZK Credit Global is an open-source credit credential infrastructure that lets anyone prove credit-related facts, solvency, repayment history, identity, and creditworthiness, without revealing the underlying data and across jurisdictions. Built on Zcash using Halo2 circuits and anchored via the shielded memo field, it turns Zcash from private money into programmable private credit infrastructure.

• Solution

A credit credential system where:

• Borrowers generate zero-knowledge proofs of credit facts (score above threshold, repayment history, solvency, employment, income) from private data they already hold.
• Lenders and institutions verify those proofs without accessing underlying records
• Credentials are anchored to Zcash: shielded, censorship-resistant, portable globally.
• No trusted credit bureau sits between borrower and lender.

Concrete example: a Brazilian worker applying for credit in Portugal proves “I have 5+ years of on-time repayment history and current income above € x”, without handing over bank statements, tax records, or employment data. The Portuguese lender verifies cryptographically. No cross-border data transfer. No privacy leak. No bureau fee. No jurisdictional dead-end.

• ZECDEX (first p2p fiat DEX with shielded escrow using FROST, a desktop app + Tor, etc) Our dev team is working to make that happen

So, what is the Zcash Applications Lab:

The Zcash Applications Lab is a continuous open-source hackathon for privacy-preserving applications on Zcash beyond payments, but data, and more.

It runs rolling 2–4 week sprints. Each sprint ships a working prototype, a spec, a short writeup, and a public demo, in a specific application vertical: verifiable credentials, private credit, compliance rails, institutional settlement, RWA attestations, private governance, ZK audits.

It is the triage and incubation layer Zcash is currently missing. Ideas enter as forum threads, ZCG-referred concepts, or community proposals. They leave as open-source code, the ecosystem can fork, extend, or productize. Reviewers evaluate running prototypes instead of speculative proposals.

Everything is public at the end of the sprint: repos, specs, writeups, and builder calls. Failed experiments still ship code and lessons. Successful ones become candidates for mini-grants, spinouts, or partner initiatives. Ideas go in, open-source code comes out, continuously, publicly, cheaply.

[Michae2xl]

Can that support decisions for the retroactive coinholder?

Test Flow:

Zcash Applications Lab sprints (1-3 months) <> ZCG (code products who gains traction can be submitted) <> in case it was reproved, there is a “second chance” 6 months, can try Retroactive Coinholder - Loop.

We can attract many developers, products, and ideas and run a year-round “hackathon-style” search for solutions based on Zcash, the protocol, ZK, collaborations, etc.

Coinholder-Directed Retroactive Grants Program Q2 2026 - Now Accepting Proposals

This program provides retroactive funding exclusively for completed projects. To qualify for a grant, your work must be verifiable; if coinholders cannot confirm your project’s completion and impact, your proposal will not be funded. When submitting your retroactive request via GitHub, you must agree to the following: I understand that this program is only for fully completed work. Applications for planned or partially finished projects will not be considered. All work must be verified by its…

[Michae2xl]

ZAL

Hi all,

The idea is the Zcash Applications Lab (ZAL): a small, volunteer-run (for now, donations-funded), open-source sandbox for applications beyond private payments. It’s not a grants program, not a research lab, and not affiliated with ZF, ZCG, Shielded Labs, and ZOLD. It’s a format experiment: time-boxed 2–4 week sprints across seven verticals (verifiable credentials, private credit, regulated privacy, institutional settlement, RWAs, governance, ZK audits/analytics, voting), where each sprint ships code + spec + writeup + demo under Apache 2.0.

The hope is that having a public track record of working prototypes in these areas is useful, whether authors later apply for ZCG / Retroactive Grants on their own, pitch elsewhere, or leave the code as a reference.

Two repos, both public, both early-draft:

• Main: GitHub - ZcashApplicationsLab/lab: The Zcash Applications Lab is a continuous open-source hackathon for privacy-preserving applications on Zcash beyond payments, but data, and more. · GitHub
• Org profile: ZcashApplicationsLab (Zcash Applications Lab) · GitHub

The README, RUBRIC, and GOVERNANCE are all v0 drafts. There’s no budget, no legal entity, no tokens, just a format proposal and a README.

Help is welcome from anyone. ZAL is a volunteer effort, so there is no gatekeeping. You can contribute by proposing a sprint, running a sprint, reviewing code or writeups, mentoring active sprints, improving the docs, flagging prior art, or just giving honest feedback in a Discussion.

I’d genuinely like honest feedback on:

1. Is this useful?
2. Rubric and verticals: anything missing, miscategorized, or too narrow?
3. Governance draft: obvious holes?
4. Format risks: anything that could make this look like competing with ZCG, which is the opposite of the intent.

Thanks, Michael.

[aaal]

It seems this proposal is meant to short circuit the ZCG route for applicants, routing activity through a new proposed entity called Zcash Applications Lab (ZAL). This would delegate oversight and authority away from ZCG and to the ZAL. Is that all correct?

[Michae2xl]

Thanks for your question, but nope, the goal is to run it as a light, hackathon-style event year-round for people who want to build before submitting empty proposals and ideas to ZCG without proof, for example. It’s also for people who want to create things without the intention of seeking grants, just to collaborate with Zcash and privacy. This was done independently, as I said above; it has no affiliation with any entity. The goal is to be open, and there’s even a chat where we can find brilliant new devs. This can help entities hire people who stand out.

It’s something interesting and something I’ve been learning, like an incubation + mirror + ideas + products + world real challenges.

[aaal]

So the idea is AND:

ZCG would continue and ZAL would exist, helping independent builders by creating a kind of live-fire program where ideas and products can incubate?

[Michae2xl]

Bingo, perfect John!

[aaal]

Triage is a process of prioritizing patients based on the severity of their condition.

In medicine, triage (/ˈtriː.ɑːʒ/) is a process by which care providers such as medical professionals and those with first aid knowledge determine the order of priority for providing treatment to injured individuals and/or inform the rationing of limited supplies so that they go to those who can most benefit from it.

So if ZAL is a triage, it sounds like a kind of filter for ZCG.

or, is it like this:

@aaal

ZCG would continue and ZAL would exist, helping independent builders by creating a kind of live-fire program where ideas and products can incubate?

…ZAL is not a filter for ZCG, but stands on its own besides it?

[Michae2xl]

This is at a community level, I can’t affirm it’s a filter for them. The committee makes its own decisions. Look outside of ZCG, what does this add to the ecosystem and to the builder? They can use this for other hackathons, for their career, and to get feedback from the community. It’s something that can be autonomous at the community level, and those interested can see it, act on it, join teams, find trusted members, and can be observers; it’s all win-win. If it makes sense, this could be funded to drive small rounds during the year, or live off donations later, and the community will judge. For example, it’s totally scalable in many ways for the public benefits.

[aaal]

I think it’s a good idea, as long as it does not interfere with ZCG.

ZCG applicants need to retain the option (in theory and in practice) to not engage with ZAL.

I think I was confused by the language (especially triage, which when in place isn’t an optional thing). The first sentence of your first post:

@Michae2xl

ZCG needs fewer idea-stage proposals to adjudicate

and then

@Michae2xl

The Lab operates as a lightweight triage and incubation layer upstream of full ZCG grants.

…I cannot agree with. ZAL should not be ‘upstream’ of ZCG (projects flow from ZAL to ZCG) and it should not be a triage. If that’s not the intention or the proposal I don’t have to go into why I think this way.

If you want to make a hackathon system to help future ZCG applicants who opt-in to ZAL (which has its own stream), that appears different than some of what you have said in your messages.

But again, if that’s what you’re aiming to make, it could be a good idea.

[Michae2xl]

@Michae2xl

hackathon-style open-source program

Sometimes it’s figurative, but perhaps poorly chosen words, sorry. But I think you understand the idea now, and it’s about what I said above - a hackathon-style open-source program.

[thowar2]

I love the enthusiasm and the concept in general.

However, the proposed focus of the sprints greatly concerns me.

Zcash is, and must remain, pure cypherpunk sound money that is entirely resistant to state censorship.

Some of the concepts you are talking about: private credit, compliance, RWA, governance, etc, are non-specific but they scare me. Each of those topics has the potential to open up attack surface to Zcash. The “DeFi apocalypse” is not a problem of transparency, it is a problem of complexity and cultural degradation of acceptable trust assumptions.

I generally think its good to foster new ideation, but I would be strongly opposed to using Zcash dev rewards to incubate ideas that would be bad for Zcash security or are not even going to be used by Zcash.

It’s also interesting to note that the comparables you mentioned are generally considered to be commercial failures:

@Michae2xl

This model is not novel, it is proven elsewhere in crypto:

• 0xPARC (Ethereum): applied ZK research and open-source apps
• Privacy & Scaling Explorations (PSE): Ethereum Foundation’s applied lab
• Flashbots: open-source research and infrastructure
• Protocol Labs: incubator pattern for Filecoin ecosystem

They were mostly useful at advancing generalized research, but with the exception of the flashbots mempool, not much was commercialized, and for the ones that were focused on a particular chain, it is also debatable that they advanced that chain.

Historically, people have treated the Zcash dev reward as a generalized zk use case research fund, which caused problems for growing Zcash itself. There has been a cultural shift away from using Zcash funds for generalized research to instead focus on improving and growing Zcash and ZEC itself.

As such, I would be opposed to any proposals that are straying from scaling ZEC as encrypted sound money, whether it may pose a security risk to the chain or it is something that is not focused on Zcash. I think you will find others with similarly strong opposition on using Zcash dev rewards for such things.

[Michae2xl]

Thanks for your point, but did you check the GitHub repo? I think that is similar to what you said → ideathon, plus it can also be a co-founder matching, you can find a partner to build with.

Zcash is private money, a store of value, a medium of exchange, and can be infrastructure as well, new verticals to adoption, people can use Zcash shielded blockchain without knowing that they are using it, it’s the hybrid I meant.

These things can’t be an attack in zcash, it’s open-source, permissionless, people can build things on Zcash with what is running today, there is no proposal to change it as it is.