Privacy-as-a-Service SDK
Layer 4 exposes a developer SDK that lets any EVM-compatible dApp integrate transaction privacy without deploying or managing the underlying ZK infrastructure. SDK access is gated and denominated in $DNET.
Core API
The SDK exposes three primary operations — shield, generateProof, andverifyProof. It handles circuit proving-key management, IPFS artifact storage, and L1↔L2 bridging transparently.
// Shield a transaction (deposit into shielded pool)
const shieldedNote = await dnet.shield({
token: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC
amount: ethers.utils.parseUnits("1000", 6),
recipient: "dnet1qp4xnzghtfnm3n2v...", // shielded address
});
// Generate a compliance proof for a claim
const proof = await dnet.generateProof({
type: "CLEAN_FUNDS",
amount: ethers.utils.parseUnits("5000", 6),
window: { from: 1704067200, to: 1735689600 },
blacklist: "0x...", // OFAC SDN list oracle
});
// Verify a proof (callable by counterparties)
const valid = await dnet.verifyProof(proof);Integration Surfaces
Client-Side
Wallets construct shielded transactions and user-authorised viewing proofs locally.
Server-Side
Backend services coordinate proof artifacts, IPFS storage, and relayer submissions.
Smart Contracts
EVM protocols connect to shielded execution without rewriting core logic. Solidity contracts deploy on DarkNet unmodified.
Access Model & Fees
Developers pay SDK access fees in $DNET. 10% of all SDK fees are burned; the remainder is distributed between stakers and the ecosystem development fund. The tiered model includes a generous free tier for protocols below a defined TVL threshold.
Phased Rollout
Proof Artifacts
Every compliance proof is exported as a portable JSON bundle:
{
"proof": "0x...",
"public_inputs": [ ... ],
"verifying_key_hash": "0x...",
"ipfs_cid": "bafy..."
}