[Grant Application] - Laminar — The Tactical Spike: Batch Payment Infrastructure for the Zcash Shielded Economy

[Darklight_Z]

Official Submission: GitHub Issue #220

To the Zcash Community and ZCG Committee:

I am submitting the formal grant application for Laminar—a professional-grade, local-first operational console designed to close the most critical bottleneck in the Zcash shielded economy.

Project Attribute | Specification

-–|—

Applicant | Darklight Labs (Pty) Ltd

Project Lead | Darklight Z

Total Request | $50,000 USD (Paid in ZEC)

Timeline | 12 Weeks (Phase 1: The Spike)

Category | Ecosystem Tooling / Privacy Infrastructure

License | Open Source (MIT / Apache 2.0)

1. Executive Summary

Laminar is mandatory, local-first enterprise infrastructure for the Zcash shielded economy.

Currently, Zcash suffers from a critical “Spreadsheet Gap”: organizations, DAOs, and grant-funded entities must manage complex treasury flows using consumer-grade mobile wallets. This creates unacceptable friction and operational risk for entities handling significant ZEC holdings.

We are requesting $50,000 for a 12-week “Tactical Spike” to build the Iron Core of Laminar. This is a stateless, air-gapped transaction construction engine designed to handle high-volume batch payments (CSV/JSON ingestion) with industrial precision.

Core Deliverable: A working desktop terminal that converts a payroll spreadsheet into scannable QR codes (Static and Animated UR) for offline mobile wallet signing, without private keys ever touching an internet-connected machine.

2. Strategic Importance to Zcash

Laminar represents the “Hardened Shell” required for organizational adoption of the shielded pool.

Weaponizing Privacy for Corporate Security

Running heavy organizational operations on transparent rails is a catastrophic corporate security breach. Laminar exists because the Zcash shielded pool is the only viable infrastructure for confidential enterprise operations. Closing the “Spreadsheet Gap” allows a 100-person monthly payroll that currently consumes an entire workday to become a 15-minute, fully shielded operation.

Hardening Network Sovereignty

Laminar is strictly local-first with zero hosted dependencies. The software runs entirely offline after installation, eliminating reliance on central servers or third-party infrastructure.

The Calculator Defense

The software functions as a non-custodial, client-side calculator. It does not transmit, hold, route, or custody funds, providing a definitive regulatory boundary. All relay and fee logic is explicitly excluded from scope. Laminar is a “Calculator, not Conduit.”

3. Dual-Mode Architecture

Laminar is engineered with a deterministic Dual-Mode Architecture designed to serve both human treasurers and autonomous systems via a single unified codebase.

Operator Mode (Human Interface) When Laminar detects an interactive TTY session, it activates Operator Mode:

• High-contrast visual UI with progress indicators and batch summaries.

• ASCII table rendering for recipient review.

• Explicit safety confirmation prompts before QR generation.

• Color-coded validation feedback.

Agent Mode (Machine Interface) When stdin is piped or the --agent flag is set, Laminar activates Agent Mode:

• Silent execution with zero interactive prompts.

• Structured JSON output on stdout for programmatic parsing.

• Exit codes for strict error handling (0=success, 1=validation error, 2=system error).

This dual-mode architecture positions Laminar as the default financial primitive for the emerging AI-agent economy, allowing autonomous systems to natively construct shielded batches.

4. Technical Constraints & Batch Capacity

Laminar operates within deterministic payload constraints based on QR encoding and wallet capabilities. For payrolls exceeding single-QR capacity, Laminar automatically segments into sequential batches with clear progress indication. Each segment is a complete, valid ZIP-321 request.

Laminar targets UR-compatible ecosystem wallets, with Zodl serving as the primary target for full static QR and animated UR support. YWallet provides fallback via static QR and deep links.

5. The Growth Roadmap: From Spike to Scale

Laminar follows a phased evolution designed to move Zcash tooling from “Experimental” to “Institutional.”

• Phase 1: The Tactical Spike (Current Scope — $50,000) Establishing the “Iron Core.” CSV/JSON ingestion, strict u64 zatoshi arithmetic, dual-mode CLI, and animated UR construction. Delivers immediate utility to ZCG-funded grant recipients.

• Phase 2: Heavy Industry (Future Scope — ~$200,000) Industrial-grade security hardening. We are actively establishing architectural backchannels with Tier-1 enterprise cryptography partners (such as * Horizen Labs) to co-design this institutional scale. Features include direct Hardware Security Module (HSM) integration, cryptographically signed PDF audit manifests for external auditors, and Multi-Party Computation (MPC) workflows for organizational spending approvals.

• Phase 3: The Protocol Socket (Long-Term) Ecosystem-wide integration via a Public SDK, allowing third-party wallets to inherit Laminar’s batch-construction logic natively.

6. Prior Work & Team Credibility

Darklight Z — Project Lead & Product Architect Darklight brings demonstrated execution capability across protocol research, cryptographic architecture, and commercial product delivery. Responsibilities include strict architectural enforcement, PRD management, and acting as the definitive capital firewall for this ZCG grant.

• Protocol & Governance Strategy: Author of The Dark Forest Doctrine, a strategic framework for privacy technology adoption actively referenced in Zcash ecosystem discussions.

• Legal AI Platform: Orchestrated product management of a high-growth Legal AI platform, demonstrating ability to ship complex software under commercial constraints.

• Sovereign Finance Architecture: Directed the end-to-end architecture of a stablecoin within the Cosmos ecosystem, engineering the strict cryptographic safeguards required for decentralized minting.

Engineering Execution — Linum Labs AG Linum Labs is a premier Web3 engineering firm headquartered in Switzerland with a track record of delivering production-grade cryptographic infrastructure since 2016.

• Institutional Pedigree: Delivered decentralized infrastructure, smart contract systems, and protocol tooling for Tier-1 Web3 entities.

• Zero-Knowledge Capabilities: Linum Labs actively engineers high-performance zero-knowledge infrastructure and scalable data pipelines for advanced Web3 protocols. This specialized cryptographic background ensures they possess the exact operational competence required to execute the librustzcash bindings safely.

• The Delivery Commitment: Linum Labs has provided a formal engagement proposal mapping directly to our $35,000 engineering allocation. They will execute the batch-construction logic strictly under Darklight’s invariants.

@Anaximander — Strategic Advisor Provides ecosystem strategy guidance, ensuring Laminar maintains regulatory clarity and aligns with the broader Zcash ecosystem trajectory.

7. Budget & Resourcing

Total Request: $50,000 USD (Hard Cap) 70% of all capital is allocated directly to engineering to preserve the “Kinetic Mass” of the Spike.

Item	Allocation	Justification
Engineering (Linum Labs)	$35,000	Core Rust dev, librustzcash, UR encoding
Operational Delivery (Darklight)	$6,000	$2,000/milestone, paid on completion
Security Hardening	$5,000	Code review + community CTF bounty
Admin & Rails	$2,500	Banking, legal formation, licensing
Strategic Advisory	$1,500	Ecosystem strategy and alignment

8. Milestones, Timeline & Deliverables

Funds are released only upon verified completion of deterministic milestones.

• Milestone 1: The Iron Core (Weeks 1-5 | $20,000) Deliverable: laminar-core published to GitHub as an open-source Rust crate. Verification: CI/CD pipeline passing. 100% address validation test coverage. All test vectors passing.

• Milestone 2: The Interface (Weeks 6-10 | $20,000) Deliverable: Laminar Alpha Desktop Client (v1.0-alpha) for macOS, Windows, and Linux. Verification: Video demonstration of a 50-transaction batch constructed and successfully scanned by an offline mobile wallet.

• Milestone 3: Deployment & Field Manual (Weeks 11-12 | $10,000) Deliverable: Public v1.0 release plus “The Field Manual” (comprehensive guide for organization treasurers). Verification: The Genesis Report. Darklight Labs will process our own live grant-funded payroll natively via Laminar, demonstrating real-world operational use.

9. Risks & Mitigations

• Engineering Partner Alignment & Cash Flow: Cash Flow Asymmetry. Standard Web3 engineering agencies typically require a 20% to 50% upfront deposit to allocate resources and initiate development. However, ZCG capital is disbursed strictly in arrears upon the verified completion of milestones. Darklight Labs does not operate as a credit facility and will not front unsecured working capital to the vendor. A misalignment in these expectations would stall execution. Mitigation: SOW Synchronization & Execution Contingency. Darklight Labs is actively structuring the final Statement of Work (SOW) with Linum Labs to synchronize their invoice schedule directly with the ZCG milestone payouts. Darklight acts as the definitive financial firewall: the grant will not be formally initiated, and development will not commence, until the vendor signs a contract accepting this arrears-based, zero-upfront payment structure. If the agency refuses to align with the ZCG risk profile, Darklight maintains a contingency roster of pre-vetted independent Rust engineers capable of executing the exact same PRD under the allocated $35,000 budget.

• Regulatory Ambiguity: Software could be mischaracterized as money transmission. Mitigation: “Calculator, not Conduit” architecture. Laminar constructs payment intents only. All relay and fee logic is explicitly excluded.

10. Core Invariants

The following architectural constraints are inviolable. Every code review must verify compliance.

• INV-01: Laminar NEVER stores, generates, or requests spending keys or seed phrases.

• INV-02: Laminar NEVER signs transactions. It constructs Payment Intents only.

• INV-03: Laminar NEVER broadcasts transactions. The mobile wallet handles network communication.

• INV-04: ALL monetary arithmetic uses integer zatoshis (u64). Floating-point is PROHIBITED.

• INV-05: If ANY row fails validation, the ENTIRE batch is rejected. No partial processing.

11. Why Vote Yes?

We are building the hardened plumbing of the Zcash economy.

This $50,000 Tactical Spike delivers immediate, tangible utility. Any organization currently managing Zcash payroll via spreadsheets can adopt Laminar Alpha within weeks of release. The team has demonstrated execution capability, and the budget allocates 70% directly to Tier-1 engineering.

Phase 1 proves the plumbing works. Phase 2 hardens it for million-dollar treasuries. Phase 3 opens it to the ecosystem.

We build. We ship. Then we scale.

Gravity absolute.

[Darklight_Z]

Architectural Note: The Operational Reality of Enterprise ZEC

As the committee reviews the Laminar architecture, I want to address the macroeconomic reality of why this specific infrastructure is required immediately.

A common question when building enterprise-grade tooling is whether the immediate market demand justifies the heavy engineering. Zooko’s recent confirmation that 100% of Shielded Labs salaries are paid in Zcash provides the definitive answer.

The demand for shielded enterprise disbursements is not a theoretical future state; it is the active, operational reality of the network’s core development entities. However, executing a 50+ person payroll today requires navigating the “Spreadsheet Gap”, forcing human operators to manually process high-volume disbursements using consumer-grade wallets. This introduces unacceptable operational friction and human error vectors.

Laminar is not being built to chase a hypothetical market. It is being built to provide the exact zero-liability, air-gapped terminal required to scale the existing Shielded Labs payroll model seamlessly to every DAO, grant recipient, and sovereign treasury in the ecosystem.

We are upgrading the tracks for a train that is already running. I am standing by for any technical questions regarding the Dual-Mode CLI or the ZIP-321 boundary execution.

[Darklight_Z]

Subject: Update & Architectural Clarification: The Spreadsheet Gap and Heavy Industry

As the ZCG committee continues its review of the Laminar Tactical Spike proposal, we want to provide a strict architectural clarification regarding the core operational problem this infrastructure solves.

With the recent structural transitions in the ecosystem—specifically the decentralization of treasury operations and the ZIP 271 lockbox—the operational burden on decentralized entities has never been higher. The ecosystem is shifting, and the tooling must shift with it.

We are not building a consumer application, and while Laminar’s engine is extensible, our immediate focus is not on experimental integrations. We are building Heavy Industry Infrastructure to solve a critical, immediate vulnerability: The Spreadsheet Gap.

1. The Reality of the Spreadsheet Gap Currently, decentralized treasuries, DAOs, and grant programs attempting to manage shielded capital are forced to rely on manual, plaintext spreadsheets and consumer-grade browser extensions. This introduces catastrophic operational friction. Forcing human operators to manually copy-paste addresses to construct high-volume batch transactions is not scale; it is an uncompensated regulatory and operational liability.

2. Zero-Liability Execution Laminar physically isolates intent construction from key custody. By providing a local-first, air-gapped terminal, treasurers can construct massive payment batches deterministically. We hold no keys. We sign nothing. The enterprise terminal handles the complexity, and the operator’s offline device handles the execution.

3. A Neutral Verification Layer Most importantly, Laminar is designed as a neutral diagnostic tool for the ecosystem. By generating strict, deterministically parsed JSON receipts for every batch, Laminar provides a mathematical proof of allocation. We are solving operational opacity at the treasury level, ensuring that capital flows can be verified instantly without generating community friction.

The underlying cryptography of Zcash is flawless. But the operational layer required to move institutional capital remains fragile.

We are building the vessel to fix the operational layer. We look forward to any technical questions the committee or community might have regarding the deterministic parsing or the Zero-Liability architecture of the Tactical Spike.

Infrastructure precedes velocity.

[ZCG]

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 sincerely appreciate the time and effort you invested in your application and encourage you to stay involved and continue contributing to the Zcash community. Further details will be available in the meeting minutes to be posted later this week.