Skip to content
GitHub / veilops-protocol

Read the code. Run the tests.

VEILOPS is developed in the open under Apache-2.0. The claims on this website are only as good as the code behind them, so here is where it lives.
publishedRepositories are live at github.com/veilops-protocol.

Privacy infrastructure for programmable financial operations, cryptographic proofs and selective disclosure.

Main protocol monorepo: source of truth
apps/ · packages/ · docs/ · tests/ · examples/
experimental
veilops/
├── .github/            workflows (CI, audit), issue + PR templates, dependabot
├── apps/website/       Next.js site: homepage, explorer, verify, dashboard, docs
├── packages/
│   ├── shared/         types, canonical JSON, ids, encoding
│   ├── encryption/     AES-256-GCM envelopes, X25519/HKDF key wrapping
│   ├── policy-engine/  declarative policies, public + confidential rules
│   ├── proof-engine/   Pedersen commitments, range proofs, attestation
│   ├── sdk/            createClient().process(): the 5-stage pipeline
│   └── solana-adapter/ memo anchoring (experimental, untested on-chain)
├── docs/               architecture, protocol, cryptography, security, guide, roadmap
├── examples/           runnable integrations
├── tests/              unit · integration · security (vitest)
├── scripts/            sample dataset generator
└── README · CONTRIBUTING · SECURITY · CODE_OF_CONDUCT · LICENSE
Quality gates
TypeScripttsc --noEmit across packages and website
LintESLint 9 + typescript-eslint
Testsvitest: unit, integration, security (tamper) suites
Buildnext build of the website
Dependenciesnpm audit + Dependabot

No stars, forks, releases or audits are shown here because none exist yet. That is the point.

How to check this project is genuine
  1. 01 The organization github.com/veilops-protocol links to veilops.tech, and this site links back to it, both ways.
  2. 02 Clone the monorepo and run npm test: 31 unit, integration and tamper tests exercise the real cryptography.
  3. 03 Every proof in the explorer can be re-verified in your browser with the same open-source code, and the deliberately tampered samples fail.
  4. 04 CI, CodeQL and dependency audits run in public on every change. Their badges link to the actual runs.
  5. 05 Security reports go through GitHub private advisories. See security.txt.
  6. 06 We state what is missing: no external audit, no mainnet deployment and no npm packages yet. Treat any claim otherwise as not coming from this project.