Clean SDK
The Clean SDK (@human.tech/clean.sdk) is a no-UI, programmable-privacy SDK for moving tokens between Ethereum L1 and Aztec L2 under a compliance gate. It is the engine behind Shield: the same identity attestation, per-transfer sanctions screening, and private bridging, exposed as a package that developers integrate directly into their own applications.
Where Shield is the hosted bridge front end, the Clean SDK is the headless building block. Use it to add compliant, privacy-preserving value flows to your app without shipping a bridge UI or holding personal data.
Install
npm install @human.tech/clean.sdkWhat it does
- Private bridging. Move USDC from Ethereum L1 into Aztec L2’s private layer, arriving as Clean USDC (cUSDC), and withdraw back to L1.
- Compliance built in. Identity attestation and sanctions screening run on every transfer, at both entry and exit, enforced cryptographically rather than by storing personal information.
- Two-tier verification. Casual users clear a Human Passport personhood check for smaller transfers; larger transfers require a full Proof of Clean Hands credential. See How verification works.
Verification tiers
- Human Passport (de-minimis tier). For transfers under $1,000, a Human Passport unique-personhood score of 20 or higher is sufficient. No government ID required.
- Proof of Clean Hands (full tier). For transfers of $1,000 and above, a ZK Gov-ID Proof of Clean Hands credential is required.
Fees and assets
Transfers settle in USDC with a 0.5% fee.
Contract addresses
Contract addresses are dynamic per deployment and are not hardcoded in documentation. Resolve them from the canonical published source:
- Support portal: support.shield.human.tech/contracts
- SDK: the
deployments.jsonbundled with the package.
Network status
The Clean SDK targets Aztec v5 mainnet (live as of 2026-07-21, deployment 5.0.0_2026-07-21). Aztec is an alpha network with ongoing audits and an active bug bounty. Only bridge funds you can afford to lose.