For anyone tracking the legal substance: the "developer exemption" framing matters because it directly responds to the Storm / Tornado Cash precedent, where prosecutors argued that publishing immutable smart-contract code can constitute money transmission if the dev anticipates illicit use.
The DOJ memo (assuming this is the https://www.justice.gov/dag/media/1419476/dl) carves out non-custodial software publication as protected, but keeps the door open for cases where the developer (a) controls user funds, (b) markets to sanctioned jurisdictions, or (c) operates an in-app fee-capture layer. So self-hosted wallets, full-node software, and pure protocol code get clearer cover; centralized "DeFi" frontends with admin keys still don't.
The downside is "non-custodial" remains undefined at the statute level — any dev with an upgradeable proxy or admin multisig is still in a gray zone. The case to watch is whoever DOJ picks as the first post-guidance test prosecution.
For anyone tracking the legal substance: the "developer exemption" framing matters because it directly responds to the Storm / Tornado Cash precedent, where prosecutors argued that publishing immutable smart-contract code can constitute money transmission if the dev anticipates illicit use.
The DOJ memo (assuming this is the https://www.justice.gov/dag/media/1419476/dl) carves out non-custodial software publication as protected, but keeps the door open for cases where the developer (a) controls user funds, (b) markets to sanctioned jurisdictions, or (c) operates an in-app fee-capture layer. So self-hosted wallets, full-node software, and pure protocol code get clearer cover; centralized "DeFi" frontends with admin keys still don't.
The downside is "non-custodial" remains undefined at the statute level — any dev with an upgradeable proxy or admin multisig is still in a gray zone. The case to watch is whoever DOJ picks as the first post-guidance test prosecution.