# Grant Application - 1CAD Protocol: ZK-TLS Proof-of-Solvency Infrastructure **URL:** \ **Category:** Applications\ **Created:** [September 14, 2026, 11:38pm UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597 "2026-09-14T23:38:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Povolnov](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/povolnov/32/48314_2.png) [@Povolnov](https://forum.zcashcommunity.com/u/Povolnov)\ **Post date:** [September 14, 2026, 11:38pm UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597/1 "2026-09-14T23:38:46Z")
Hi Zcash Community, We have submitted a ZCG grant application for 1CAD Protocol — an open-source ZK-TLS infrastructure standard automating Proof-of-Solvency and Source of Wealth (SoW) verification without exposing sensitive user payloads (RFC-1001/0201). GitHub Grant Proposal Issue: > > > \### Terms and Conditions > > \- \[x\] I agree to the \[Grant Agreement\](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_f81ef4e4b5f040038350270590eb2e42.pdf) terms if funded > \- \[x\] I agree to \[Provide KYC information\](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD > \- \[x\] I agree to disclose conflicts of interest > \- \[x\] I agree to adhere to the \[Code of Conduct\](https://forum.zcashcommunity.com/t/zcg-code-of-conduct/41787) and \[Communication Guidelines\](https://forum.zcashcommunity.com/t/zcg-communication-guidelines/44284) > \- \[x\] I understand all milestone deliverables will be validated and accepted by their intended users or their representatives, who will confirm that the deliverables meet the required quality, functionality, and usability for each user story. > \- \[x\] I agree that for any new open-source software, I will create a \`CONTRIBUTING.md\` file that reflects the high standards of Zcash development, using the \[\`librustzcash\` style guides\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference. > \- \[x\] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any \[merge\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), \[branch\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), \[pull request\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and \[commit\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the \`librustzcash\` repository. > \- \[x\] I agree to post request details on the \[Community Forum\](https://forum.zcashcommunity.com/c/grants/33) > \- \[x\] I understand it is my responsibility to post a link to this issue on the \[Zcash Community Forums\](https://forum.zcashcommunity.com/c/grants/33) after this application has been submitted so the community can give input. I understand this is required in order for ZCG to discuss and vote on this grant application. > > \### Application Owners (@Octocat, @Octocat1) > > @Povolnov > > \### Organization Name > > US LLC / IDAA UK (#17223770) > > \### How did you learn about Zcash Community Grants > > Zcash Ecosystem Forums & Developer Community > > \### Requested Grant Amount (USD) > > 20000 > > \### Category > > Research & Development > > \### Project Lead > > \`\`\`project-lead.yaml > Name: Andrei Povolnov, Founder & Director at IDAA UK / US LLC (@Povolno > Role: Lead Cryptographic Systems Architect / Principal Investigator (PI) > Background: Founder and Director at IDAA UK (#17223770) / US LLC. Experienced in cryptographic protocol architecture, Zero-Knowledge proofs (ZK-TLS), open specification development (RFC standards), and regulatory compliance frameworks. > Responsibilities: Overall project management, architectural design, and delivery of the 1CAD Protocol core infrastructure. > Authoring and refining the open-source specification documents (RFC-1001, RFC-0201, RFC-0301, RFC-0401). Implementing and benchmarking client-side ZK-TLS circuit logic and Evidence Package verifier modules. > Serving as primary liaison for Zcash Community Grants (ZCG) milestones, ecosystem integrations, and security testing. > \`\`\` > > \### Additional Team Members > > \`\`\`team-members.yaml > None or N/A > \`\`\` > > \### Project Summary > > 1CAD Protocol is an open-source ZK-TLS infrastructure standard automating Proof-of-Solvency and Source of Wealth (SoW) verification without exposing sensitive user payloads. > > \[1CAD\_White\_Paper\_compressed.pdf\](https://github.com/user-attachments/files/32214969/1CAD\_White\_Paper\_compressed.pdf) > > \### Project Description > > The 1CAD Protocol introduces a modular framework (RFC-1001/0201/0301/0401) designed to bridge private data sources with public/private institutions using Zero-Knowledge proofs. It enables users to generate cryptographically verifiable Evidence Packages locally via ZK-TLS primitives. > > \[IDAA\_Arch\_2026\_4\_compressed.pdf\](https://github.com/user-attachments/files/32214973/IDAA\_Arch\_2026\_4\_compressed.pdf) > > \### Proposed Problem > > Institutional compliance (AML/SoW) currently requires invasive, centralized sharing of unencrypted financial documents, creating severe privacy risks and single points of failure for user data > > \[IDAA\_Briefing\_Note\_02\_EN.pdf\](https://github.com/user-attachments/files/32215000/IDAA\_Briefing\_Note\_02\_EN.pdf) > > \### Proposed Solution > > We replace raw document disclosure with zero-knowledge proofs generated on client devices, allowing institutions to verify solvency and wealth sources while preserving user data privacy. > > \### Solution Format > > Open-source software repository (ZK-TLS verifier), technical specification documents (RFCs), and cryptographic test suites > > \### Dependencies > > Standard Rust cryptography libraries, TLS 1.3 web infrastructure, and local execution environments (with R&D integration for hardware wallets like Tangem). > > \### Technical Approach > > Client-side ZK-TLS proof generation using lightweight circuit architectures, serializing output into standardized RFC-0201 Evidence Packages for decoupled verification. > > \### Upstream Merge Opportunities > > No direct forks of core Zcash repos required; outputs provide reusable Rust-based ZK-TLS verifier modules usable across the broader privacy ecosystem. > > \### Hardware/Software Costs (USD) > > 2000 > > \### Hardware/Software Justification > > Testing hardware (including cold-storage devices) and dedicated cloud environments for automated CI/CD ZK-verifier benchmark testing. > > \### Service Costs (USD) > > 2000 > > \### Service Costs Justification > > Legal compliance structure maintenance (IDAA UK / US LLC) and domain/infrastructure hosting. > > \### Compensation Costs (USD) > > 15000 > > \### Compensation Costs Justification > > Engineering and architecture compensation for protocol implementation, circuit optimization, and documentation over a 3-month cycle. > > \### Total Budget (USD) > > 20000 > > \### Previous Funding > > No > > \### Previous Funding Details > > N/A > > \### Other Funding Sources > > Yes > > \### Other Funding Sources Details > > Pending non-dilutive ecosystem grants (Ethereum Foundation ESP ecosystem review). > > \### Implementation Risks > > Complexities in optimizing ZK-TLS proof generation time on constrained client-side devices, mitigated by modular circuit design. > > \### Potential Side Effects > > Minimal. Verifier modules are open-source and run locally without centralized data lock-in. > > \### Success Metrics > > Open-source release of the RFC-1001/0201 ZK-TLS verifier repository, test coverage \>90%, and public verification capability of Evidence Packages. > > \### Startup Funding (USD) > > 5000 > > \### Startup Funding Justification > > Initial setup of core developer environments, hardware acquisition for circuit benchmarking, and repository architecture setup. > > \### Milestone Details > > \`\`\`milestones.yaml > Milestone 1 ($7,500 - Month 1): Release of RFC-1001 core specification and open-source ZK-TLS verifier base repository. > > Milestone 2 ($7,500 - Month 2-3): Implementation of RFC-0201 Evidence Package formatting, end-to-end integration testing, and documentation release. > \`\`\` > > \### Supporting Documents > > \`\`\`files.yaml > \- 1CAD\_Protocol\_RFC\_Overview.pdf: Technical specifications for RFC-1001/0201\[cite: 1\] > > \- \[https://github.com/EXCH-Services\](https://github.com/EXCH-Services): Public repository for 1CAD Protocol engineering > \`\`\` We welcome any feedback, questions, and discussion from the community! ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [September 15, 2026, 12:22am UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597/2 "2026-09-15T00:22:45Z")
You actually just pasted what the AI told you. You actually just uploaded documents Claude generated VERBATIM? “RFC-1001” RFC-1001 is an RFC about NetBIOS specs. RFC-0201 is not a document that exists or is ratified. What? “No jurisdiction in this set defines a common list of acceptable evidence types, a common data format, or a mechanism for one institution’s accepted SOF file to be recognised by another — across borders or even within the same country. Every freeze, every onboarding check, and every enhanced-due-diligence request currently starts from zero.” THATS THE ENTIRE ISSUE. THE JURISDICTION HAS NOT DEFINED IT. You cannot define it! You have no right to do that, and ergo, no one will adopt it until every jurisdiction’s government individually approves your (and countless others, see [xkcd: Standards](https://xkcd.com/927/) ) protocol. ![image](https://global.discourse-cdn.com/zcash/original/3X/d/5/d592925c243612182b04d8ff1aa6b4afe58fd494.jpeg) Which they would definitely do, right? The UN quorum can’t agree on what colour to put on the new building logo, let alone your “global AML structure”. All I ask to applicants here is (a) be coherent, (b) be authentic, and (c) actually be realistic. My god. ---
**Author:** ![Povolnov](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/povolnov/32/48314_2.png) [@Povolnov](https://forum.zcashcommunity.com/u/Povolnov)\ **Post date:** [September 15, 2026, 1:22pm UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597/3 "2026-09-15T13:22:21Z")
ok fair point on RFC-1001, that was dumb, that number’s literally the NetBIOS spec, my bad. honestly we shouldn’t be calling our own docs “RFC” at all, that’s an IETF thing not ours to use. gonna rename the whole series so this doesn’t happen again, will fix the application too. on the “who gave you the right” thing, no one did, that’s kind of the point, we’re not asking anyone’s permission we’re just building a spec and trying to get it recognized the same way PCI-DSS or SWIFT formats did, private thing first, government/institutional recognition later if it’s actually useful. that’s why we’re going through BSI, FCA, AMLA consultations etc, slowly, no guarantee it works. the “global AML structure” line in the application was overselling it, that’s on me, should’ve just said what it actually is. appreciate the harsh read tbh, better to hear it now than after wasting everyone’s time ---
**Author:** ![Povolnov](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/povolnov/32/48314_2.png) [@Povolnov](https://forum.zcashcommunity.com/u/Povolnov)\ **Post date:** [September 15, 2026, 2:11pm UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597/4 "2026-09-15T14:11:32Z")
fixed the RFC-1001/RFC-0201 naming thing you pointed out. renamed the whole series from RFC- to IDAA- across the repo, updated the internal cross-references, and also filled in the IDAA-1004 gap (verifier interface spec) that was referenced but never actually written. commit’s here if you want to check: [Remove local helper script, not part of the published specs · EXCH-Services/RFC@6652421 · GitHub](http://github.com/EXCH-Services/RFC/commit/6652421) still don’t expect anyone to just take “1CAD is the standard” at face value, that’s fair pushback and the whole point of publishing this stuff openly instead of behind closed doors. if you want more on the actual reasoning (not just the file names), the white paper goes into why we went with ZK-TLS attestation instead of raw document exchange: [https://idaa.uk/guides/1CAD\_White\_Paper.pdf](https://idaa.uk/guides/1CAD_White_Paper.pdf) ---
**Author:** ![ZCG](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/zcg/32/33712_2.png) [@ZCG](https://forum.zcashcommunity.com/u/ZCG)\ **Post date:** [September 30, 2026, 1:19pm UTC](https://forum.zcashcommunity.com/t/grant-application-1cad-protocol-zk-tls-proof-of-solvency-infrastructure/57597/5 "2026-09-30T13:19:00Z")
Thank you for submitting your proposal. Following a thorough review by the ZCG and a period for community feedback on the forum, the committee has decided not to move forward with this proposal. We encourage you to stay involved and continue contributing to the Zcash community. Further details: [Meeting minutes](https://forum.zcashcommunity.com/t/zcash-community-grants-zcg-meeting-minutes-9-28-2026/57928)