DarkNet Protocol logo

Governance & Regulatory Strategy

DarkNet is designed to operate durably in a regulatory environment increasingly attentive to privacy tools. Governance is non-custodial and progressively decentralised; the regulatory position rests on three principles grounded in FSB, Basel, and FATF frameworks.

Governance Surface

$DNET holders control, via on-chain voting:

  • Proving-system upgrades (e.g., circuit version bumps, ceremony additions).
  • Fee schedule adjustments (gas denomination, burn ratios, SDK tiering).
  • Compliance blacklist oracle selection (OFAC SDN feed provider, revocation registry).
  • Treasury allocation and buyback/liquidity operations.
  • Approved KYC credential issuers admitted to the Layer-3 registry.

Votes use the shielded nullifier-based scheme: a voter proves their stake crosses the threshold, casts a vote, and records a nullifier. Vote-buying through public visibility of large positions is structurally prevented.

Principle 1 — Cryptographic Compliance ≡ Legal Compliance

A cryptographically-verified compliance proof — mathematically demonstrating that funds are clean, transactions were below threshold, or the holder has passed KYC — satisfies the substance of regulatory requirements even when the historical form was designed for traditional instruments.

Supported by: FSB 2023 crypto-asset framework explicitly acknowledging cryptographic attestations; Basel Committee's 2022 consultative document contemplating cryptographic proof systems as a valid risk-attestation mechanism.

Principle 2 — Privacy of Non-Criminal Activity is a Protected Interest

Financial privacy for legitimate activity is explicitly protected under GDPR Article 7, European Convention on Human Rights Article 8, and implicitly under the U.S. Fourth Amendment. The availability of on-demand compliance disclosure is sufficient to satisfy law enforcement access requirements without requiring universal transaction surveillance.

Supported by: ECtHR jurisprudence on mass surveillance (Big Brother Watch v. UK, 2021); academic work by Angela Walch, Ross Anderson, and Primavera De Filippi.

Principle 3 — Developer Non-Custody Eliminates Criminal Liability

The Tornado Cash prosecution hinged on the claim that the developers operateda money transmitter. DarkNet's legal architecture distinguishes itself on four counts:

Non-custodial design
Smart contracts never hold user assets in a manner accessible to developers. Assets are controlled exclusively by ZK spending keys.
Compliance pathway
Compliance Proofs and KYC credential integration remove the “no compliance pathway” argument central to Tornado Cash enforcement.
Decentralised governance
Control transfers to $DNET governance at launch. No developer admin keys retain upgrade authority.
Legal entity and jurisdiction
Operated via a Swiss or Cayman Foundation structure with dedicated crypto regulatory counsel on retainer prior to public launch.

Progressive Decentralisation

Phase 1
Core team stewardship
Testnet, audits, initial mainnet launch. Emergency council controls upgrade timelock.
Phase 1.5
Token-holder voting
Fee schedules, grants, and treasury operations move to on-chain vote. Council retains veto for circuit-level safety.
Phase 2
Full on-chain governance
Protocol upgrades, oracle selection, and compliance registry admission all governed by shielded $DNET vote.