ZCG Grants Prototype
Back to applications

Grant application

[Revised] zec-go: Independent, Alternative Zcash Full Node Client

Evaluation snapshot

Request at a glance

Applicant
Chainscore Labs
Requested
$1,296,000
Status
Declined
Review context
Forum discussion linked1 committee record linked

FPF source evidence

Milestone and disbursement ledger

Read-only milestone and disbursement fields normalized from the FPF grants ledger.

These ledger rows are FPF source evidence. They do not by themselves prove that a progress update was accepted, a payment request was approved, or an on-chain settlement was completed. Named rows can also describe reimbursements, returned funds, or other ledger adjustments.

No normalized FPF milestone or disbursement rows are linked to this application yet. The application and its other source evidence remain available below.
AI-grounded decision supportCommittee briefingReview an evidence-grounded briefing or ask a custom question about this application. AI output supports committee review; it does not recommend or make a funding decision.Not generated

No committee briefing yet

Generate a standard briefing from this application, linked evidence, team history, relationships, and comparable grants. The completed shared report will be available to other authorized users.

Your account can read shared briefings but cannot generate them.

Application-scoped research

Ask about this application

Ask a focused question. Answers use the grant knowledge index and retain numbered links to the evidence supplied to the model.

Your account can read shared analyses but cannot generate a custom answer.

Workflow signals
📋 Grant Application👀 Ready For ZCG Review❌ Grant Declined
Latest committee record
Declined1/19/2026

The project will develop zec-go, a clean-room, production-grade Zcash full node client written in Go to improve network resilience, performance, and decentralization by increasing node implementation diversity. With zcashd being deprecated…

Data quality and provenanceSource matching, linked-record coverage, and reconciliation diagnostics

Source coverage

Operational context for tracing how this canonical record was assembled.
Source stateGitHub + Sheet
GitHub-Sheet match100%
Primary forum1
Supporting forum0
GitHub labels3
Decision notes1

GitHub workflow labels

3 labels captured as structured grant attributes
đź“‹ Grant Application
Category
Intake
Status
Grant Application
Milestone
-
Observed
1/19/2026
Open GitHub issue
đź‘€ Ready For ZCG Review
Category
Review
Status
Ready For Zcg Review
Milestone
-
Observed
1/19/2026
Open GitHub issue
❌ Grant Declined
Category
Decision
Status
Declined
Milestone
-
Observed
1/19/2026
Open GitHub issue

Decision history

1 meeting note linked
Declined1/19/2026

Zec-Go - Independent Zcash Full Node Client

Unanimous rejection

The project will develop zec-go, a clean-room, production-grade Zcash full node client written in Go to improve network resilience, performance, and decentralization by increasing node implementation diversity. With zcashd being deprecated and zebra becoming the dominant client, Zcash faces systemic risk from client monoculture; a single consensus bug could disrupt the entire network. Zec-go will be an independent, consensus-compatible implementation using a modular, service-oriented, library-first architecture optimized for concurrency and cross-platform deployment. To reduce cryptographic risk, all consensus-critical cryptography will be accessed via FFI to the heavily audited librustzcash library, allowing the project to focus on robust node engineering. Phase 1 will deliver a fully operational full node capable of initial block download, full chain validation, mempool management, and peer-to-peer block and transaction propagation. Applicant is requesting $1,296,000. Gguy: There are pros and cons to having multiple nodes and we have very much experienced that very recently. And while I am open to the idea I don’t think that that would provide a net benefit at this point in time. I think it’d actually be a net negative for Zcash. I vote to reject. Zerodartz: Right now, I don’t see the benefits but when we’re stably running on Zebra, maybe then something like this could be revisited. Hanh: Yeah the full implementation would not be really a full implementation yet because they use librustzcash via FFI. The cryptographic part is not in Go. Second, they lack an audit. Without that, very few people will be comfortable using it as a full node. That’s in phase 2 & 3, and therefore is not covered by this proposal yet. It takes a lot of work to build a full node even for a team of experts Zcash engineers (the zebra team). So I think first of all we should have zebra work (it’s not fully ready yet) before we invest in having another implementation. At least, we would have the experience of building a full node from scratch and hopefully even some documentation regarding the pitfalls. Artkor: I agree with everything that has been said, given that the Zcash protocol is currently evolving rapidly and is expected to undergo significant change. Maintaining multiple full node implementations in parallel appears premature due to the high long term costs of keeping them in sync. For this reason I reject this proposal too. decentralistdan: Reject. As an Ecosystem we’re focused on deprecation of zcashd and Zebra as the single full node implementation. I would like to see that work finish and then possibly consider a new 2nd full node implementation in another language.

Confidence
100%
Match method
Direct Source Url
Minutes
Zcash Community Grants Meeting Minutes 1/19/2026
Committee notes

Gguy: There are pros and cons to having multiple nodes and we have very much experienced that very recently. And while I am open to the idea I don’t think that that would provide a net benefit at this point in time. I think it’d actually be a net negative for Zcash. I vote to reject.

Zerodartz: Right now, I don’t see the benefits but when we’re stably running on Zebra, maybe then something like this could be revisited.

Hanh: Yeah the full implementation would not be really a full implementation yet because they use librustzcash via FFI. The cryptographic part is not in Go. Second, they lack an audit. Without that, very few people will be comfortable using it as a full node. That’s in phase 2 & 3, and therefore is not covered by this proposal yet.

Artkor: I agree with everything that has been said, given that the Zcash protocol is currently evolving rapidly and is expected to undergo significant change. Maintaining multiple full node implementations in parallel appears premature due to the high long term costs of keeping them in sync. For this reason I reject this proposal too.

Forum links

1 primary, 0 supporting
Primary forum thread

[Revised] Proposal: Zec-Go, An Alternative, Independent ZCash Full Node Client

Hello ZCash Community, Based on the feedback received from ZCG and upon discussions with members from ZF and ECC, we are revising our proposal’s scope, timeline, and structure for developing an alternative, Independent Full Node Client Implementation of ZCash - Grant Application - [Revised] zec...

Confidence
100%
Forum URL
https://forum.zcashcommunity.com/t/revised-proposal-zec-go-an-alternative-independent-zcash-full-node-client/54268
Open forum thread

source: forum_mirror | topicId: 54268 | fetchedAt: 2026-11-22T08:10:08.660Z | categoryId: 36 | mirrorKind: forum_topic | coverageCapped: false | discoveredFrom: ["github_issue_comment:ZcashCommunityGrants/zcashcommunitygrants#191:comment:3748207913","google_sheet_row:1FQ28rDCyRW0TiNxrm3rgD8ai2KGUsXAjPieQmI1kKKg:1164534734:grant-platform:700ebaf2b679e20ed88c3b49d2ce6a801a5739e495df725ab19f193644c0cd20"] | postStreamCount: 2

Application source evidence

Primary GitHub, Sheet, and other non-forum source records.
Github Issue

Grant Application - [Revised] zec-go: Independent, Alternative Zcash Full Node Client

### Terms and Conditions - [x] I agree to the [Grant Agreement](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_f81ef4e4b5f040038350270590eb2e42.pdf) terms if funded - [x] I agree to [Provide KYC information](https:/...

Confidence
100%
Source ID
ZcashCommunityGrants/zcashcommunitygrants#191
Open source record

repo: zcashcommunitygrants | owner: ZcashCommunityGrants | state: closed | author: prasad-kumkar | labels: ["📋 Grant Application","👀 Ready For ZCG Review","❌ Grant Declined"] | number: 191 | closedAt: 2026-01-19T14:23:46Z | commentCount: 1

Github Issue Comment

Comment on #191: Grant Application - [Revised] zec-go: Independent, Alternative Zcash Full Node Client

https://forum.zcashcommunity.com/t/revised-proposal-zec-go-an-alternative-independent-zcash-full-node-client/54268

Confidence
100%
Source ID
ZcashCommunityGrants/zcashcommunitygrants#191:comment:3748207913
Open source record

repo: zcashcommunitygrants | owner: ZcashCommunityGrants | author: prasad-kumkar | number: 191 | issueUrl: https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/191 | commentId: 3748207913 | createdAt: 2026-01-14T07:33:34Z | issueNumber: 191

Google Sheet Row

zec-go: Independent, alternative Zcash Full Node Client

Date Submitted: 1/14/2026 | Proposal Title: zec-go: Independent, alternative Zcash Full Node Client | Applicant(s): Chainscore Labs | Grant Platform Link: https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/191 | Forum Link: https://forum.zcashcommunity.com/t/revised-proposal-zec-go-

Confidence
100%
Source ID
1FQ28rDCyRW0TiNxrm3rgD8ai2KGUsXAjPieQmI1kKKg:1164534734:grant-platform:700ebaf2b679e20ed88c3b49d2ce6a801a5739e495df725ab19f193644c0cd20
Open source record

gid: 1164534734 | sheetId: 1FQ28rDCyRW0TiNxrm3rgD8ai2KGUsXAjPieQmI1kKKg | tabName: all_grants_tracking | rowNumber: 473 | legacySourceId: 1FQ28rDCyRW0TiNxrm3rgD8ai2KGUsXAjPieQmI1kKKg:1164534734:row:473 | identityStrategy: grant_platform_link | businessIdentifier: https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/191 | rowLocationSourceId: 1FQ28rDCyRW0TiNxrm3rgD8ai2KGUsXAjPieQmI1kKKg:1164534734:row:473