Privacy-preserving AI-assisted escrow for milestone-based work.
Sentinel-Z is a hackathon prototype exploring a shielded escrow workflow built around Zcash privacy primitives, independently reviewable milestone evidence, and an AI-assisted verification oracle.
This repository is being built in clearly separated stages:
- Demo mode: deterministic local escrow state and visibly simulated receipts. No real Zcash funds move.
- Zcash integration boundary: a server-only adapter contract for a future wallet/signer integration. Unified Addresses, viewing keys, and transaction signing are distinct concepts.
- AI verification: structured milestone assessment is advisory. It cannot sign transactions or release funds by itself.
- Escrow authorization: a separate, authenticated state transition is required before any configured signer can be called.
- Next.js App Router, React, TypeScript (strict)
- Tailwind CSS
- Three.js / React Three Fiber for the vault visualization
- Appwrite for authentication and application metadata (configured separately)
- Zcash wallet/signer adapter boundary (real network integration is not enabled by the demo)
- Install Node.js 20 or newer.
- Install dependencies:
npm install. - Copy
.env.exampleto.env.localand fill in only the values you have configured. - Start the development server:
npm run dev. - Open
http://localhost:3000.
Run checks before opening a pull request:
npm run typecheck
npm run lint
npm run buildSee .env.example. Never commit real API keys, Appwrite server keys, wallet seeds, private keys, or viewing keys.
- A Zcash Unified Address (typically
u1...) is a payment address, not a viewing key. - Viewing keys are sensitive capabilities. Never put them in browser storage, logs, analytics, or AI prompts.
- Lightwalletd uses gRPC; it is not a generic JSON REST endpoint.
- Real Orchard spends require a supported wallet implementation and secure signer. This Next.js app does not fabricate Orchard transactions.
- Demo receipts are explicitly labelled simulated and are not proof of an on-chain transaction.
- AI output is untrusted, schema-validated input to a review process—not authorization to release funds.
- URL-based evidence inspection must use strict allowlists and SSRF protections before production use.
app/: Next.js routes and API handlerscomponents/: interface and 3D scenelib/escrow/: escrow domain state and transition ruleslib/zcash/: wallet/signer adapter contracts and demo adapterlib/ai/: structured milestone assessmentlib/appwrite.ts: Appwrite client configuration
- Create a demo escrow.
- Lock it in the local simulated state.
- Submit milestone evidence.
- Run the advisory AI assessment.
- Review the result and explicitly authorize the demo release.
- Inspect the simulated receipt and event log.
main: production-ready integration branchdev: integration branch- Feature work uses
feat/<topic>branches and pull requests intodev. - Never merge unreviewed changes directly into
main.
See CONTRIBUTING.md for contribution rules.