### 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)
Mharris40
### Organization Name
Compliledger
### How did you learn about Zcash Community Grants
X and Zypherpunk Hackathon
### Requested Grant Amount (USD)
$60000
### Category
Infrastructure
### Project Lead
```project-lead.yaml
Name:Maranda Harris
Role:Founder/CEO
Background:Over 14 years of compliance and security experience with a masters in cybersecurity
Responsibilities:I lead the development implementation and growth of Compliledger
```
### Additional Team Members
```team-members.yaml
- Name:None No employees or co founders at this time (Contracting a AI engineering team in India to build it)
Role:
Background:
Responsibilities:
- Name:
Role:
Background:
Responsibilities:
- Name:
Role:
Background:
Responsibilities:
- Name:
Role:
Background:
Responsibilities:
- Name:
Role:
Background:
Responsibilities:
- Name:
Role:
Background:
Responsibilities:
```
### Project Summary
CompZ is an open-source, Zcash-native compliance and attestation SDK that enables organizations to prove regulatory compliance and audit integrity using zero-knowledge proofs, without exposing transaction data or compromising Zcash’s privacy guarantees so institutions and enterprises can adopt Zcash without sacrificing confidentiality.
### Project Description
CompZ is an open-source, Zcash-native compliance and attestation SDK designed to enable privacy-preserving auditing, regulatory assurance, and enterprise adoption without compromising Zcash’s cryptographic privacy guarantees.
Zcash offers best-in-class privacy through shielded transactions, but enterprises, custodians, and exchanges cannot adopt Zcash at scale without mechanisms for proving compliance. In current systems, compliance and auditing typically require exposure of sensitive transaction data, identities, or metadata — creating a direct conflict with Zcash’s privacy model. This has resulted in weaker-privacy chains seeing greater institutional adoption not because they are superior, but because they are easier to audit.
CompZ eliminates this false trade-off by introducing privacy-preserving compliance primitives built specifically for Zcash.
The project delivers a developer-friendly SDK that allows Zcash-based applications to produce cryptographic “Proof-of-Compliance” artifacts using zero-knowledge techniques. These proofs verify policy compliance, transaction integrity, and operational controls without requiring access to transaction contents, wallet keys, identities, or addresses. The result is auditability without surveillance.
CompZ is designed as public infrastructure for the Zcash ecosystem, not as a product or platform. The SDK will be released as open-source software under a permissive license, enabling any developer, wallet, exchange, custodian, or enterprise system to integrate compliance proofs without vendor lock-in or centralized dependencies. All proof verification will be performed through trustless, open-source tooling.
Key capabilities of CompZ include:
• Zero-knowledge compliance attestation for shielded transactions
• Cryptographic verification of policy adherence
• Zcash-native verification interfaces
• Trustless compliance validation tools (CLI/API)
• Documentation, examples, and reference integrations
CompZ does not act as a custodian, indexer, surveillance system, or monitoring platform. It does not collect transaction data, access private keys, or deanonymize users. Instead, it provides cryptographic evidence that certain conditions have been satisfied — without revealing underlying data.
CompliLedger is a downstream adopter of CompZ, but CompZ is not dependent on CompliLedger. The SDK is intentionally designed as independent ecosystem infrastructure and may be freely adopted by third-party projects.
The goal of CompZ is to make Zcash operationally viable for regulated environments without undermining privacy. By addressing compliance as a cryptographic problem rather than an administrative one, this project extends Zcash’s philosophical commitment to privacy into the real world of audits, regulation, and enterprise deployment.
This project enables Zcash not only to remain the most private blockchain — but to become the most deployable privacy system in production.
### Proposed Problem
Zcash lacks privacy-preserving compliance and audit infrastructure, which limits real-world and institutional adoption of shielded transactions.
While Zcash’s cryptography enables world-class privacy, there is currently no standardized way for organizations to prove regulatory compliance, policy enforcement, or transaction integrity without revealing sensitive data. Existing compliance approaches require exposure of transaction records, identities, or metadata in order to satisfy auditors and regulators. This directly conflicts with Zcash’s privacy model and deters enterprises, custodians, and exchanges from using shielded transactions.
As a result:
• Organizations avoid shielded pools despite Zcash’s security advantages.
• Enterprises choose less private blockchains because they offer audit tooling.
• Compliance becomes synonymous with surveillance.
• Zcash remains under-deployed in regulated environments.
The ecosystem currently forces a false choice:
Privacy OR compliance — but not both.
Without privacy-preserving compliance primitives, Zcash cannot realize its full potential as a production-grade financial system for real-world use cases governed by regulatory and operational accountability.
CompZ exists to resolve this structural gap by introducing Zcash-native audit and compliance infrastructure that preserves privacy while enabling accountability.
### Proposed Solution
CompZ solves this problem by providing a Zcash-native, open-source SDK that enables cryptographically verifiable compliance and audit proofs without exposing private transaction data.
Rather than relying on data collection or surveillance, CompZ treats compliance as a cryptographic problem. The system generates zero-knowledge attestations that prove required conditions were met—such as policy enforcement, transaction legitimacy, and operational controls—without revealing transaction contents, wallet addresses, identities, or metadata.
CompZ introduces several core capabilities:
1. Zero-Knowledge Compliance Attestations
Applications using CompZ can produce cryptographic “Proof-of-Compliance” artifacts that demonstrate regulatory and operational requirements have been satisfied without revealing private inputs.
2. Zcash-Native Verification Tooling
CompZ includes open-source verification mechanisms (CLI/API) so auditors, partners, and regulators can independently validate compliance proofs without trusted intermediaries.
3. Developer-Friendly SDK
CompZ provides a standardized interface for integrating compliance proofs into wallets, custodians, and Zcash-based applications. Developers can embed compliance capabilities without reinventing custom logic or compromising privacy.
4. Non-Invasive Architecture
CompZ does not custody assets, scrape blockchain data, access private keys, or deanonymize users. Proofs are generated using local policy logic and cryptographic primitives, not transaction monitoring or surveillance.
5. Open and Reusable Infrastructure
All components are released as open-source under a permissive license, allowing the Zcash ecosystem to share tooling without vendor lock-in.
By delivering compliance as verifiable math rather than disclosure-based oversight, CompZ makes Zcash deployable in real-world and regulated environments while preserving its core privacy guarantees.
Instead of weakening privacy to satisfy compliance, CompZ enables Zcash to become the first blockchain where compliance enhances privacy rather than eroding it.
### Solution Format
The project will be delivered as an open-source software initiative composed of reusable tooling, documentation, and reference implementations for the Zcash ecosystem.
Primary Deliverables
1. Open-Source Software (CompZ SDK)
A modular, Zcash-native SDK providing:
• Compliance attestation functions
• Zero-knowledge proof generation
• Standardized integration interfaces
• Policy validation logic
• Cryptographic verification mechanisms
2. Verification Tooling
• Command-line interface (CLI) for proof verification
• API endpoints for enterprise and developer systems
• Trustless verification support for auditors and integrators
3. Open Technical Documentation
• Architecture overview
• Integration guides
• API reference documentation
• Security and cryptographic design notes
4. Reference Implementations
• Example wallet-level integration
• Sample Zcash compliance workflow
• Demonstration deployment environment
5. Public Code Repository
• All development hosted in a public GitHub repository
• Community-reviewable pull requests
• Open issue tracking
• Open roadmap and milestone tracking
Secondary Deliverables
• Developer onboarding documentation
• Community walkthroughs
• Installation guides
• Release notes
• Contribution guidelines
The project will not produce proprietary software or gated access systems. All tooling will be publicly available and maintained as open ecosystem infrastructure.
### Dependencies
CompZ has minimal external dependencies and is designed to be developed and delivered as a self-contained, open-source project.
Technical Dependencies
• Zcash Protocol & Documentation
Required for accurate integration of shielded transaction primitives and Zcash-specific cryptographic parameters.
• Rust / Python / TypeScript Tooling
Depending on final implementation choices for the SDK, verifier, and CLI tools.
• Zero-Knowledge Cryptography Libraries
Standard open-source ZK frameworks (e.g., Halo2, Pasta curves, or equivalent Zcash-compatible tooling).
• Public Zcash Node Access
Standard RPC/Lightwallet access for reference integrations—no special permissions required.
Resource Dependencies
• Development infrastructure (GitHub repository, CI/CD, automated testing environment).
• Documentation generation tooling.
• Community feedback during open-source review.
Collaborations / External Coordination
CompZ does not require formal partnerships or exclusive collaboration.
The following interactions are helpful but not required:
• Zcash Community Developers
For feedback and ecosystem alignment.
• Wallet or Custodial Teams (Optional)
To test reference integrations and validate developer experience.
• Zcash Foundation / ECC (Advisory Only)
For cryptography best practices and protocol-aligned guidance if they choose to provide input.
What CompZ Does Not Depend On
• No proprietary systems
• No third-party APIs
• No custodial integrations
• No private datasets
• No commercial agreements
CompZ is intentionally built as independent, open-source infrastructure that can be maintained, used, and extended by the Zcash ecosystem without reliance on external organizations.
### Technical Approach
CompZ is implemented as a modular, Zcash-native toolkit focused on cryptographic verification rather than data collection. The architecture is intentionally lightweight, privacy-first, and compatible with Zcash’s shielded model.
System Architecture
The system is composed of four primary layers:
1. Compliance Abstraction Layer
Encodes regulatory or policy requirements as deterministic rules and verifiable conditions. Rules are expressed as policy templates that define what must be proven, not what must be revealed (e.g., policy class compliance, transaction constraints, operational controls).
2. Zero-Knowledge Proof Engine
Generates compliance proofs using zk techniques compatible with Zcash’s cryptographic ecosystem (e.g., Halo2-compatible circuits). These circuits validate compliance conditions without disclosing sensitive inputs.
3. Zcash Integration Interface
Integrates with shielded Zcash workflows by consuming Zcash state data through standard interfaces without custody, indexing, or data scraping. Proof generation occurs locally and produces cryptographic attestations tied to Zcash activity without exposing transaction contents.
4. Verification Tooling
Open-source verification via CLI and API for independent validation of proofs by auditors, integrators, or ecosystem participants.
⸻
Methodology
CompZ follows a phased engineering approach:
Phase 1 – Architecture & Cryptographic Design
• Zcash-specific design review
• Proof model definition
• Policy-to-circuit mapping
• Threat modeling and privacy validation
Phase 2 – Core SDK Implementation
• Compliance engine implementation
• ZKP circuit design and testing
• Proof artifact schema
• Local proof generation logic
• Packaging libraries and APIs
Phase 3 – Integration Framework
• Reference wallet flows
• SDK APIs
• Proof verification tooling
• Public docs and examples
Phase 4 – Hardening & Release
• Security review
• Documentation
• Open source release
• Developer onboarding
⸻
Key Technical Principles
• No Surveillance – No transaction monitoring or indexing
• No Key Custody – No wallet access
• No Data Centralization – No logs of sensitive activity
• Local Proof Generation – Proofs are generated by the client
• Trustless Verification – Anyone can verify proofs independently
• Composable Design – SDK is reusable across projects
⸻
Technology Stack (Tentative)
• Rust (core SDK & circuits)
• Halo2 or Zcash-compatible zk frameworks
• CLI in Rust or Python
• Public repository on GitHub
• CI/CD for testing and reproducibility
• JSON proof artifacts
• Open documentation stack
⸻
Verification Model
• Proof outputs are cryptographically verifiable.
• No trusted third-party required.
• Deterministic replay supported.
• Independent verification enabled via CLI or API.
⸻
This approach ensures CompZ remains aligned with Zcash’s privacy guarantees while delivering enterprise-grade accountability via cryptography rather than surveillance.
### Upstream Merge Opportunities
CompZ does not require forking or modifying Zcash core protocol repositories. The project is intentionally designed to operate as an external SDK and tooling layer that integrates with Zcash via standard interfaces without altering consensus logic, wallet internals, or protocol-level cryptography.
Upstream Zcash Repositories
There are currently no required upstream forks planned for:
• zcashd
• librustzcash
• ECC or Foundation wallets
• Consensus or cryptographic libraries
Planned Modifications
No direct modifications are required to upstream Zcash codebases for this project. CompZ will operate through:
• SDK integration
• Proof generation modules
• Verification tooling
• Policy abstraction logic
Ecosystem Merge Opportunities
While no upstream changes are required, the project may optionally propose upstream contributions in the following forms:
• Example reference integrations for wallets
• Documentation improvements related to privacy-preserving compliance workflows
• Optional libraries demonstrating Zcash-compatible proof verification flows
• Test harnesses or tooling that could benefit developer experience
Any such contributions would be coordinated with maintainers and proposed as optional enhancements rather than required protocol changes.
Coordination With Maintainers
Coordination with ECC or Zcash Foundation maintainers is optional, not required, for delivery of CompZ.
If any reusable code or documentation is identified as appropriate for upstream contribution, discussions would be opened following community governance norms.
Timeline Considerations
Because CompZ does not rely on upstream merges for core functionality, no timeline blockers exist for deployment.
Any upstream proposals would occur after initial release and stabilization, based on maintainability, community value, and maintainer interest, typically no earlier than 3–6 months into the project.
### Hardware/Software Costs (USD)
1500
### Hardware/Software Justification
Total estimated hardware and software cost: $1,500
Cost Breakdown
• Development workstation hardware (if needed): $500
• Cloud compute / test environments: $500
• CI/CD tooling and repository operations: $250
• Documentation tooling and build systems: $150
• Miscellaneous development expenses: $100
Notes
• The project does not require specialized hardware (e.g., GPUs, proprietary cryptographic appliances).
• All core dependencies are open-source.
• No paid third-party APIs or closed-source services are required.
• Development assumes use of publicly available Zcash tooling and libraries.
• Costs are minimized to favor open infrastructure and open standards.
The requested hardware and software funds are strictly for development infrastructure required to build, test, and release CompZ as a production-grade open-source SDK.
General-purpose development hardware is necessary for local testing, proof generation, and build validation. Standard cloud compute resources are needed to support automated testing, proof verification in CI pipelines, and reference deployments for reviewers and developers. CI/CD tooling ensures reproducibility, regression testing, and security validation across operating systems and environments.
Documentation tooling is required to generate accurate SDK references, compliance specification outputs, and developer guides. These are essential for adoption by the Zcash community, integrators, and external users. Miscellaneous tooling covers development utilities, build dependencies, and test frameworks that improve code quality and security validation.
All major components rely on open-source software. No proprietary platforms, closed APIs, or expensive infrastructure are required. Costs are minimized to ensure the grant predominantly supports engineering work and public infrastructure rather than operational overhead.
### Service Costs (USD)
0
### Service Costs Justification
Total external service cost: $0
Explanation
The project does not rely on paid third-party services, proprietary APIs, external consultants, or commercial infrastructure.
All development will be performed using:
• Open-source tooling
• Public Zcash infrastructure
• Self-managed repositories and CI/CD
• Community-supported cryptographic libraries
No vendors, contractors, or ongoing service subscriptions are required to deliver CompZ.
### Compensation Costs (USD)
$58500
### Compensation Costs Justification
Total team compensation cost: $58,500
Breakdown
• Lead Developer / Architect (5 months): $45,000
• Documentation and Open Source Support: $8,500
• QA / Testing and Review: $5,000
Notes
Compensation covers only labor directly tied to the delivery of open-source software and public documentation. No funds are allocated to executive salary, sales, marketing, or commercial product development. All work funded under this request contributes directly to the creation of public goods for the Zcash ecosystem.
Developer Role & Rate
Lead Developer / Architect (Solo Maintainer)
• Rate: $90/hour
• Estimated Hours: 650 hours
• Total: $58,500
• Responsibilities:
• System & cryptographic architecture
• SDK implementation
• Zcash integration logic
• Zero-knowledge proof framework design
• CLI & verification tooling
• Documentation & examples
• Maintenance and release management
Justification
The project is intentionally designed for single-developer execution to minimize coordination costs and ensure accountability. The scope focuses on infrastructure development, not commercialization or support operations. All work is aligned to delivery of public goods.
Progress will be milestone-based and tracked through public GitHub commits and releases.
### Total Budget (USD)
$60000
### Previous Funding
No
### Previous Funding Details
_No response_
### Other Funding Sources
No
### Other Funding Sources Details
_No response_
### Implementation Risks
1. Cryptographic Complexity
Zero-knowledge systems are complex and require careful design and testing.
Mitigation:
Use well-established Zcash-compatible cryptographic libraries and follow conservative design principles. Development will prioritize correctness and verifiability over experimental cryptography.
⸻
2. Scope Expansion Risk
Compliance projects can grow quickly if not tightly scoped.
Mitigation:
Scope is intentionally limited to SDK-level infrastructure. The project explicitly avoids building full platforms, governance systems, or enterprise integrations.
⸻
3. Ecosystem Alignment
Developing in isolation may result in limited adoption.
Mitigation:
Design decisions will be documented publicly, and code will be developed in public repositories to allow community feedback. Early integrations and documentation will focus on developer usability.
⸻
4. Technical Integration Challenges
Variations in wallet architectures and Zcash tooling can complicate integration.
Mitigation:
CompZ focuses on external SDK interfaces rather than modifying wallets or core software. Reference integrations are optional and non-invasive.
⸻
5. Single-Developer Execution Risk
Reliance on a single contributor may pose throughput or continuity challenges.
Mitigation:
Scope is calibrated for solo execution. Development will be milestone-driven and publicly tracked via GitHub to ensure accountability and transparency.
⸻
6. Adoption Uncertainty
Even strong tooling requires outreach to gain use.
Mitigation:
The project will prioritize clear documentation, examples, and verification tooling to encourage adoption and independent experimentation.
### Potential Side Effects
1. Misinterpretation of Compliance Guarantees
Users may incorrectly believe that using CompZ automatically guarantees regulatory compliance for all jurisdictions.
Mitigation:
Documentation will clearly state that CompZ provides cryptographic attestations and tooling, not legal certification. Compliance responsibility remains with the integrator.
⸻
2. Centralization Misconceptions
There may be concerns that CompZ introduces centralized oversight or monitoring.
Mitigation:
CompZ does not collect data, monitor transactions, custody keys, or operate as a central service. All proofs are generated locally and verified independently.
⸻
3. Misuse of Proof Artifacts
Proofs could be reused incorrectly or claimed out of context.
Mitigation:
Proofs will be time-bound, verifiable, and cryptographically scoped to prevent reuse or misrepresentation.
⸻
4. False Assumptions of Regulatory Acceptance
Regulators may not immediately recognize cryptographic proofs as sufficient.
Mitigation:
CompZ focuses on standards-based cryptography and verifiable evidence, while encouraging independent audit validation.
⸻
5. Increased Complexity for Developers
Integrating cryptographic tooling may increase technical burden.
Mitigation:
CompZ will provide simplified APIs, examples, and documentation to reduce integration complexity.
### Success Metrics
Success will be measured through delivery, usability, verification, and ecosystem adoption metrics.
Delivery Milestones
• Public release of the CompZ SDK
• Completion of CLI verification tooling
• Documentation and API references published
• Reference integration completed
• Open-source repository live
Technical Validation
• All proofs verifiable using open-source tools
• Successful test cases demonstrating privacy-preserving compliance
• Reproducible builds and deterministic verification
• Passing automated test suite
Adoption Metrics
• At least one reference integration completed
• Community testing or usage by external developers
• Engagement through GitHub issues or pull requests
• Verified downloads, forks, or clones
Ecosystem Impact
• Feedback from Zcash developers
• Discussion or mentions in community forums
• Educational utility (citations, references, usage examples)
Maintenance Indicators
• Tagging of stable releases
• Ongoing issue resolution
• Documentation updates following release
CompZ will be considered successful if it delivers public, verifiable infrastructure that meaningfully lowers the barrier to deploying Zcash in privacy-sensitive and regulated environments.
### Startup Funding (USD)
$5000
### Startup Funding Justification
Startup funding is required to initiate development immediately while the full grant review and disbursement process is underway.
These funds will be used to:
• Set up development environments and repositories
• Perform initial architecture and design work
• Build the first proof-of-concept components
• Establish testing and documentation tooling
• Cover minimal infrastructure costs necessary to begin development
The startup funding enables early momentum and reduces project risk by ensuring the project progresses from day one. It is not intended for long-term operations or commercialization, only to support early technical execution.
### Milestone Details
```milestones.yaml
Milestone 1 — Architecture & Cryptographic Design
Duration: 4 weeks
Budget: $9,000
User Stories
• As a developer, I want a documented system architecture so I can understand how CompZ integrates with Zcash.
• As a cryptography reviewer, I want to review proof design choices and assumptions.
• As an open-source contributor, I want documentation to understand the project structure.
Deliverables
• Architecture design document
• Zero-knowledge proof design specification
• Threat model and privacy analysis
• Integration flow diagrams
• Public GitHub repository initialization
Acceptance Criteria
• Architecture documentation is published in the repository
• Threat model is publicly accessible
• ZK design documentation exists in the repository
• GitHub repository is public and accessible
• README links to all documents
Budget Use
• Architecture design
• Cryptography research
• Threat modeling
• Repository setup
⸻
Milestone 2 — Compliance Engine Implementation
Duration: 6 weeks
Budget: $17,000
User Stories
• As a developer, I want to define compliance policies as code.
• As a user, I want policy logic separated from transaction logic.
• As a tester, I want deterministic compliance validation behavior.
Deliverables
• Policy abstraction layer
• Compliance validation engine
• SDK structure
• Local execution capability
• Unit tests for compliance logic
Acceptance Criteria
• Compliance logic runs locally
• Policy definitions are version-controlled
• SDK directory structure exists
• Unit tests pass
• Policy documentation exists
Budget Use
• SDK core development
• Compliance logic implementation
• Unit tests
⸻
Milestone 3 — Zero-Knowledge Proof Framework
Duration: 6 weeks
Budget: $17,000
User Stories
• As a user, I want compliance proofs without revealing private data.
• As a verifier, I want to independently validate proofs.
• As a developer, I want reproducible proof results.
Deliverables
• ZK proof templates
• Proof generation logic
• Proof schema definition
• Test proofs
Acceptance Criteria
• Proofs successfully generate
• Proofs successfully verify
• Test vectors are included
• Proof format is documented
• Proof constraints are documented
Budget Use
• Proof design
• Circuit implementation
• Debugging and test coverage
⸻
Milestone 4 — SDK & Verification Tooling
Duration: 4 weeks
Budget: $8,000
User Stories
• As a developer, I want easy SDK integration.
• As an auditor, I want proof verification via CLI.
• As an integrator, I want API access for validation.
Deliverables
• Packaged SDK
• CLI verification tool
• API documentation
• Versioned proof format
Acceptance Criteria
• SDK installs successfully
• CLI verifier runs successfully
• Proof validation completes
• API documentation is published
• Example usage works
Budget Use
• SDK packaging
• Verifier tooling
• API documentation
⸻
Milestone 5 — Documentation, Reference Integration & Release
Duration: 2 weeks
Budget: $4,000
User Stories
• As a developer, I want onboarding instructions.
• As a user, I want example usage.
• As the community, I want an official release.
Deliverables
• Reference integration example
• Developer documentation
• Public release
• Final project report
Acceptance Criteria
• Reference example runs
• Documentation is complete
• Release is published
• Final report submitted
Budget Use
• Documentation
• Example integration
• Release preparation
```
### Supporting Documents
```files.yaml
- CompZ GitHub Repo Link - https://github.com/Compliledger/CompZ/tree/main
```
,