State the surprising connection up front: a Treasury notice about Venezuela sanctions belongs on a blockchain desk because sanctions compliance is now an on-chain discipline. On June 10, 2026, the Department of the Treasury's Office of Foreign Assets Control published General Licenses 48A and 49A, issued pursuant to the Venezuela Sanctions Regulations. The notice formalizes in the Federal Register two general licenses that OFAC had previously made available on its website. The "A" suffix signals these are amended versions of earlier licenses — a revision, not a brand-new authorization.
To understand why this matters, you have to understand what a general license is. Sanctions programs work by broadly prohibiting transactions with designated persons, entities, or jurisdictions. A general license is a pre-authorized carve-out: it permits a defined category of otherwise-prohibited activity without requiring each party to apply for a specific license. The license text is therefore not a press release — it is operative law that compliance teams parse line by line to decide what they can and cannot do. When OFAC amends a general license, it is redrawing the boundary of what is permitted, and every regulated party that relies on that boundary has to re-read it.
"The Department of the Treasury's Office of Foreign Assets Control (OFAC) is publishing two general licenses (GLs) issued pursuant to the Venezuela Sanctions Regulations: GLs 48A and 49A, which were previously made available on OFAC's website."— OFAC, Federal Register notice 91 FR 35143, source
Here is the link to the crypto world, and it is not theoretical. OFAC sanctions apply to U.S. persons regardless of the rails a transaction rides on. Crypto exchanges, stablecoin issuers, custodians, and wallet providers all owe the same obligation a bank owes: do not facilitate prohibited transactions, screen counterparties against OFAC's lists, and block or reject what the regulations forbid. The novel wrinkle is that on a public blockchain the "counterparty" is an address, and OFAC has in the past designated specific wallet addresses tied to sanctioned actors. So a Venezuela general license — by defining precisely which transactions are authorized — is part of the same rulebook a crypto compliance team must apply when deciding whether a flow to or from a Venezuela-linked party is permitted.
Why publication in the Federal Register is the news
OFAC routinely posts general licenses to its website before they appear in the Federal Register. The formal publication does two practical things. First, it puts the licenses on the official, citable public record — 91 FR 35143 — which matters for legal certainty and for anyone who needs an authoritative source rather than a website snapshot that can change. Second, it confirms the amended texts (the "A" versions) as the operative ones, superseding whatever they replaced. For a compliance officer, "which version is current" is not pedantry; relying on a superseded license is a fast path to a violation.
The substance of what GLs 48A and 49A authorize lives in the license texts themselves, which is exactly the point: this is a beat where the document, not the summary, governs. The Federal Register notice is the pointer that tells regulated parties the authoritative texts have been published and amended. The responsible move for any firm with Venezuela exposure — including crypto firms that touch Venezuelan counterparties, remittances, or oil-and-gas-adjacent flows that frequently feature in that sanctions program — is to pull the actual license language and re-paper their screening rules against it.
The discipline: authorized is not the same as encouraged
A recurring trap in sanctions coverage is conflating "OFAC issued a license" with "OFAC is loosening sanctions." An amended general license can narrow as easily as it can widen; the only way to know is to read it. What the published notice establishes, verifiably, is that two specific licenses under the Venezuela program have been formally issued in amended form and entered onto the public record on June 10, 2026. It does not, on its own, tell you whether any particular crypto transaction is now permitted — that depends on the license's defined scope and conditions.
It also helps to understand why OFAC structures so much of its program around general licenses rather than case-by-case approvals, because the design choice has direct consequences for crypto firms. Sanctions are intentionally broad — they prohibit whole categories of dealings with a target — and that breadth would freeze legitimate humanitarian, contractual, and wind-down activity if there were no pre-authorized exceptions. General licenses are those exceptions, drafted to permit defined activity without forcing every party to seek an individual specific license. For a crypto compliance team, the practical effect is that the general-license file is not optional reading: it is the authoritative list of what is permitted within an otherwise-prohibited program. A transaction that touches a Venezuela-linked counterparty might be flatly barred, or it might fall squarely inside the scope of GL 48A or 49A — and the only way to know is to map the transaction against the license's defined activities, conditions, and expiry. Amendments like the move to the "A" versions can shift those edges, which is why a fresh publication is an operational event, not just a filing.
The connective lesson for this beat is the one worth keeping: crypto compliance is not a parallel universe with its own rules. It inherits the federal sanctions framework wholesale, and OFAC's general-license file is a living document that defines the edges of what's allowed. A wallet screen, a stablecoin redemption check, an exchange's transaction monitor — all of them are, in the end, implementations of texts like GLs 48A and 49A. The transparency of a public blockchain cuts both ways: it makes evasion easier to trace, and it makes a firm's compliance posture, or failure of one, easier to reconstruct after the fact. Follow the license, not the headline, and screen accordingly.