Update: so much news.
- ZEC Observatory · OpenZcash
- Scheduled payments · OpenZcash
- ZCG Investments · OpenZcash
- any companies/funding ZEC treasury calculator · OpenZcash
- More.
Update: so much news.
Really appreciate the work you’ve put into OpenZcash, @Michae2xl — from the original 13-tabs pain point to ZCG Copilot to this budget consultation, it’s rare to see this level of transparency and iteration in the same project. The tiered-proposal idea from your July post especially stuck with me — treating scope as negotiable up front instead of through decline/resubmit cycles feels like an obvious win once you see the 84% decline-rate data.
Personally, as a community member, the tool has genuinely helped me navigate Zcash and spot opportunities, while solving that same many-tabs headache everyone’s mentioned here. I’d love to see this funded — but I think it would help to see more detail on how the funds would actually be used. Right now the tiers read more like a summary of what gets delivered than a breakdown of where the money goes — I think if you could share a rough cost split (e.g., between the paid assistant, infrastructure, and your own time) there will be more response from the community
Received $424M. Worth $5.2B today. Where did every ZEC outside of mining go?
Block 1: https://cipherscan.app/block/1
Thank you very much for the valuable feedback and for participating. I really want to keep sharing valuable insights about Zcash, information on transparency, and where to find specific resources that few others are aware of. I’m calling myself the “Greek Librarian of Zcash.”
Introducing OpenZcash Monthly: openzcash.org/monthly/2026-09
OpenZcash weekly update — October 2–9
Over the past week, OpenZcash received several improvements:
We’ve also added five interactive Coinholder charts for the finalized Q3 2026 round:
Casts and revealed shares do not identify unique voters. Final ZEC weights remain separate from activity over time.
Next on the roadmap: prepare near-real-time counting of accepted casts for the next voting window, after chain inclusion and subject to the public data feed. The current charts are historical; final ZEC weights remain separate.
Feedback is welcome—what would make the next round easier to follow?
Keep up the awesome work @Michae2xl @openz
Openzcash has quickly become one of the most important resources available to me (and many others) in the Zcash ecosystem! It’s awesome having all this information organized, and easy to ingest in one spot ![]()
Thank you very much! That motivates me to keep improving. I’ll have more news soon, and it’s really cool.
Hey everyone,
A grant decision should leave a history people can inspect: the proposal, the community’s feedback, each member’s reasoning, and the final outcome.
I’m building Participate inside OpenZcash to connect that history with blockchain timestamping on Zcash. The pilot has already anchored proposal records and a separate batch of comments and likes on mainnet, using batches and Merkle trees so many records can share one transaction and still have individual proofs.
Published proposal records, budgets and committee positions in Participate.
Authors can follow published committee positions and read each member’s feedback beside the proposal, with links to the original sources. Community comments and likes keep the conversation attached to the application.
The goal for committee review is practical: bring relevant feedback into the proposal workspace, reducing the need to reconstruct a discussion across long forum threads. The intended journey connects proposal → community feedback → individual votes → final verdict → verifiable history.
Comments contribute context; likes express community interest; committee votes determine the outcome. Zcred do not buy voting power or approval. Historical positions shown today are summaries of published ZCG sources. Operating the review and verdict through Participate would require the committee’s agreement.
A summary of a member’s published feedback, with its source.
The initial batch anchored 25 proposal records in one Zcash transaction. A later automatic capture brought the archive to 26 anchored proposal records at the 11 October 2026 checkpoint.
A separate mainnet pilot anchored 17 discussion events, including comments and likes. Its retained receipts connect each event to the batch; the recorded verification reached 12 confirmations. That demonstrated preserving activity around a proposal, alongside the proposal archive.
Each record gets a cryptographic fingerprint. A Merkle tree combines those fingerprints into a single root anchored on Zcash. An individual inclusion proof connects a record to that root, so a changed copy fails verification without needing every other record in the batch.
Read & verify lets you download preserved files, receipts and verification tools. The confirmed commitment provides a timestamped integrity reference that cannot be silently rewritten in the archive. The content itself stays in downloadable files: keeping those files and receipts is essential for recovery.
Archive downloads and the saved mainnet check for an official-source capture.
Sign in with an email code and try your own profile. Eligible accounts can claim 25 free demo Zcred: a test proposal uses 20, a comment 1, and a like 1.
These credits support participation around proposals. The aim is to make useful community input easier for authors and reviewers to find. No ZEC purchase is needed; purchases are closed during this pilot. Start with a private draft if you just want to explore.
Participate is an independent OpenZcash pilot. The official ZCG application and decision process continues unchanged, and the committee workspace is restricted.
Automatic mainnet anchoring currently covers eligible proposals from the official ZCG GitHub source. New user-created demo proposals, comments and likes stay outside that queue. The earlier 17-event batch is a completed pilot, not a promise that every new interaction is sent to mainnet. New committee verdicts still need their own anchoring flow.
Publishing a test requires a relevant forum discussion link; please do not create dummy forum topics to test the form. A saved private draft is enough.
These historical anchors used Sapling. New automatic proposal anchors require Ironwood; the first confirmed Ironwood receipt remains a separate milestone. Original proposal packages contain metadata snapshots or decision summaries; newer automatic captures preserve GitHub Markdown and metadata. Linked attachments are not included. The activity batch contains imported events: its block time is distinct from when someone originally commented or liked.
File and Merkle checks can run offline. A fresh blockchain check additionally requires a synchronized node and a compatible view-only reader. An anchor establishes a commitment’s inclusion, not authorship, committee endorsement or permanent file availability.
Open a proposal, inspect a member’s feedback, then download a record through Read & verify. Does the decision become easier to understand? Can you recover the files? What would make the discussion more useful to an author or reviewer?
Share what you tried and where you got stuck. This is the foundation I want to improve with the community, before wider committee, Coinholder or DAO use.
The committee preview brings the proposal, discussion, individual votes and published feedback together, making the reasoning behind each decision easier to follow.
The proposed workflow gives each of the five members one signed vote and a public explanation. Results become final after all five respond, with at least three approvals required to pass. No deadline. Zcred does not influence voting power.
This screenshot shows historical ZCG decisions imported from public sources. Committee operations remain read-only in the pilot, pending authorization.
This is insane. Nice work!