DarkNet $DNET

First look at the DarkNet dApp. The design discipline is the same as the protocol: nothing on screen that isn't yours, nothing collected that doesn't need to be. OTP sign-in. Session-bound dashboard. Zero telemetry on authenticated routes. A single dark surface where your shielded account lives — because the chain should feel like an envelope, not a billboard. What ships next into this same surface: → Deposit / Send / Withdraw → Viewing Key Manager → Compliance Proof Generator All ZK proofs generated in-browser via Web Workers. Notes decrypt locally. Your history never leaves your device. Private by default. Compliant on demand.

Selective Disclosure is live. 🛡️ `/dashboard/keys` — mint, scope, expire, revoke. → Full / Incoming / Scoped keys (fvk1 / ivk1 / svk1) → Scoped keys: amount cap, asset filter, expiry → Persisted to D1, revocable any time Hand your accountant a key for USDC notes under $50k, valid 90 days. They see exactly that. Nothing else. Sharing *some* of your history should never have required sharing *all* of it. dnetprotocol.xyz

darknet-cli is now public. One binary. Full access to DarkNet Protocol from your terminal. cargo install --path . dnet --help Shield, transfer, withdraw — all without touching a browser. Built for developers, power users, and anyone who wants privacy without the UI. 🔗 github.com/dnetprotocol/d…

Shield Funds is live. Connect your wallet → choose ETH, DNET, or USDC → the dApp handles the entire approve + deposit flow. No copy-pasting addresses. No manual contract calls. What happens when you hit “Shield”: - A Groth16 commitment is generated locally in your browser - ⁠ERC-20 approval is sent (only if needed — skipped for ETH) - ⁠depositETH / depositERC20 is called on the Shield Pool contract - The note commitment is posted on-chain → your shielded balance updates, with the amount kept private What’s coming next: - Shield Pool contract deployment (starting with Sepolia testnet) - ⁠Real ZK proof generation via Web Workers (replacing the stub commitment) - ⁠Send / Withdraw / History - ⁠Viewing Key Manager The UI is ready.

Every privacy protocol lives or dies by one question: Do all your tools agree on what a "note" is? If wallets, CLIs, and relayers each roll their own cryptography — one mismatch and funds are gone. darknet-core is the single source of truth. Keys. Notes. Nullifiers. Merkle. Stealth. Compliance. One Rust library. One security boundary. Everything else just imports it.

darknet-core is now public. The canonical Rust library for DarkNet Protocol client-side cryptography. One audited library. One security boundary. Every wallet, CLI, and relayer depends on it — no re-implementations. Ships with: → key hierarchy & derivation → note commitments & nullifiers → incremental Merkle tree → stealth addresses (DKSAP) → witness construction → compliance proof builders → WASM-ready for browsers no_std. Battle-hardened. Pre-audit, pre-1.0 — primitives landing crate by crate. 🔗 github.com/dnetprotocol/d…

Every transaction on Ethereum is public. Your trades. Your balance. Your strategy. All visible to anyone with a browser. DarkNet Protocol makes privacy the default and compliance a choice. Private by default. Compliant on demand. Enforced by math, not by trust. $DNET 🔐

Exchanges delist privacy coins because they can't satisfy FATF Travel Rule. $DNET Compliance Proof Generator: → Proof of Clean Funds → Proof of Transaction Range → Proof of Identity Binding (ZK-KYC) Auditable. Private. Regulator-ready. This is how privacy gets listed.

Monero: privacy, zero compliance → delisted everywhere Zcash: compliance, privacy opt-in → 80% tx are transparent Tornado: privacy, zero compliance → OFAC sanctioned $DNET breaks the trilemma: •Privacy by default •ZK compliance on demand •Full EVM composability Same cryptography. Different outcome.

DarkNet $DNET is LIVE! CA: 0x5E6FD2F576b9774c1D5Bf539F3dC2B0077Cc9753

Private by default. Compliant on demand. Enforced by math, not by trust. Welcome to $DNET🔐

Privacy is for everyone 🔐