0x4a885aef4a88…4a885aec

ConfirmedRegulation & Policy454 vB145 sat/vB2 min decode

DOJ Narrows Money Transmission Charges for Decentralized Software

DOJ guidance dated Aug. 21, 2025 restricts charges under 18 U.S.C. § 1960(b)(1)(C) for truly decentralized, non-custodial peer-to-peer software, but stops short of developer immunity.

DOJ's 2025 Guidance Limits Charges Involving Decentralized Software
WitnessDOJ's 2025 Guidance Limits Charges Involving Decentralized SoftwareBernd 📷 Dittrich / unsplash

Outputs

  1. DOJ issued the guidance in remarks dated Aug. 21, 2025.

  2. The policy covers only 18 U.S.C. § 1960(b)(1)(C), one provision of federal law.

  3. Charges are disallowed only when software is truly decentralized, automates peer-to-peer transactions, and no third party controls users' assets.

  4. The guidance does not create blanket immunity for developers.

  5. Prosecution continues for knowing crimes, and other charges may still apply.

The U.S. Department of Justice has issued guidance dated Aug. 21, 2025 that restricts when prosecutors may bring charges under one specific federal money transmission statute against parties behind decentralized software. The policy covers 18 U.S.C. § 1960(b)(1)(C), a single provision of federal law, and applies only in a narrow set of circumstances.

The charging standard is relevant only when the software in question automates peer-to-peer transactions and no third party controls users' assets. Prosecutors would not approve a charge under that provision when three conditions hold: the software is truly decentralized, it solely automates peer-to-peer transactions, and the third party has no custody or control of users' assets.

What exactly does the guidance cover?

The scope is narrower than headlines may suggest. One statute, one charging scenario, and a strict set of technical predicates frame the entire policy.

  • Applies to new charges against a third party, not retroactively described cases.
  • Requires that the software genuinely be decentralized in operation.
  • Requires that the software's function be limited to automating peer-to-peer transactions.
  • Requires that the third party hold no custody or control over users' assets.

If any of those conditions fails, the restriction on charging does not apply. In plain words: the guidance protects a narrow category of software, not software developers as a class.

Does this grant developers immunity?

No. The remarks do not establish blanket immunity for software developers, and the DOJ took care to say so. The guidance states that developers who contribute code without specific criminal intent are not criminally liable under this framework.

That protection is conditional, and the caveats are significant. The DOJ will continue prosecuting people who knowingly commit crimes or aid them, according to the Aug. 21 remarks. Other charges may still apply when criminal intent is present, meaning the limitation on § 1960(b)(1)(C) does not shut the door on alternative theories of liability.

What is not said matters as much

The guidance leaves several questions unanswered. It does not define "truly decentralized" in technical terms, leaving prosecutors to assess custody, control, and automation case by case. It also does not address other provisions of federal law beyond § 1960(b)(1)(C), nor does it bind civil regulators such as the Securities and Exchange Commission or the Commodity Futures Trading Commission.

The consequence for operators is operational, not merely legal. Teams building non-custodial, peer-to-peer software now have a clearer, if narrow, federal criminal charging boundary; teams with any custody arrangement or third-party asset control remain fully exposed under the same statute. The practical takeaway is simple: the guidance buys certainty only for protocols where no one holds the keys.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,203 articles