Project information
Repository scope, package status, and what is not yet in place.
Packages
The project is split into five source packages:
@opertus/contracts
The pool, executor, caller clones, fee logic, Poseidon LeanIMT (up to 32 levels), and four Groth16 verifier contracts.
@opertus/circuits
Transfer circuits for 1, 2, 4, or 8 inputs and three outputs.
@opertus/core
Log synchronization, note selection, witness construction, transaction hashing, proof generation, and call preparation.
@opertus/wallet
Key derivation, custom meta-addresses, note encryption, scanning, and local note storage.
@opertus/crypto
BabyJubJub stealth ownership plus Poseidon commitment, blind, and nullifier primitives.
Each package is MIT licensed. The SDK packages are pre-releases
(0.0.x-alpha) and are not published to npm yet: they install from the private
GitHub repos at their latest release tag, as shown in
getting started, and export TypeScript source
directly.
What is implemented
- Deposits, private transfers, public unshields, and one external call with up to four shielded return assets.
- Circuit and wallet tests for ownership, conservation, field bounds, commitment binding, nullifier derivation, clone salts, scanning, encryption, and local note handling.
- Contract tests for deposits, spends, fees, the executor, and the Merkle tree.
- Core tests for spend validation, live fee reads, log synchronization, and the prover.
What is not in place yet
- Audit. Opertus has not been audited.
- Deployments. There is a Sepolia testnet deployment; its addresses are in getting started. There is no production deployment.
- Package releases. Packages are not published to a registry, and there is no changelog or release policy.
- Security contact. There is no security disclosure address or bug bounty.
- Contribution policy. There is no formal contribution policy or contributor agreement.
Until these exist, treat any address, artifact, audit claim, or security contact you encounter as unofficial unless it appears in these docs or comes through a verified project channel. To evaluate a specific deployment, follow the deployment integrity checklist.