Oregon has no bespoke crypto-asset licensing statute. Crypto exchange, custody and transmission businesses fall under Oregon's general Money Transmitter licensing regime (administered by the Division of Financial Regulation within the Department of Consumer and Business Services), accessed via the multistate NMLS portal. Oregon was among the first states (2015) to expand the statutory definition of 'money' to capture virtual-currency-like mediums of exchange, bringing crypto businesses within money-transmission scope; multiple crypto exchanges (e.g., CEX.IO) have since obtained Oregon MTLs via NMLS.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Oregon has no state-level statutory token taxonomy. Federal SEC/CFTC characterization governs token-as-security/commodity status. However, Oregon's Attorney General has pursued an independent state-court securities-enforcement theory against Coinbase (filed April 2025) alleging sale of unregistered crypto-asset securities to Oregonians, in tension with the SEC's February 2025 dismissal-with-prejudice of its parallel federal case and the SEC/CFTC's March 2026 joint interpretive release classifying bitcoin as a 'digital commodity' rather than a security. Coinbase disputes the AG's authority, asserting that Oregon securities matters are generally the province of the Division of Financial Regulation, not the Attorney General. This litigation remains a live source of classification uncertainty specific to Oregon.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Oregon has not enacted state-specific statutes governing staking, DeFi lending, mining, node operation, tokenization, or validator activity. The only Oregon-relevant activity in this space is indirect: the now-dismissed SEC staking-as-a-service claims against Coinbase (2023-2025), which concerned federal, not Oregon-specific, securities law. On-chain activity in Oregon is governed only by the general MTL/securities overlays discussed in other modules, plus federal guidance.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Oregon has not enacted a state-level stablecoin issuance, reserve, or redemption-right statute. Stablecoin regulation in the US now runs primarily through the federal GENIUS Act, which established the first federal regulatory framework for payment stablecoins and under which entities such as Circle and Ripple have received provisional national banking charters from the OCC. Oregon-domiciled stablecoin activity is expected to be governed by this federal framework rather than any state-specific regime.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Consumer protection in the crypto space in Oregon is currently most visible through the Attorney General's securities-enforcement theory against Coinbase, which frames unregistered crypto-asset sales as exposing Oregon consumers to pump-and-dump and fraud risk. Coinbase disputes that the AG (rather than the Division of Financial Regulation) holds primary authority over such consumer-protection-adjacent securities matters, and has separately sued Governor Kotek over public-records access related to the enforcement action.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No Oregon-specific virtual-currency tax guidance was identified in this research pass. Oregon personal income tax generally starts from federal taxable income, so the federal property characterization of crypto (and resulting capital-gains/income-tax treatment) is expected to flow through to Oregon liability, but this state-level conformity has not been independently confirmed against a primary Oregon Department of Revenue source. At the federal level, the IRS has for roughly a decade treated cryptocurrency as property rather than currency, making sales and exchanges taxable events, and beginning with the 2025 tax year, crypto brokers must report transactions to the IRS via the new Form 1099-DA.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Oregon imposes no identified state-specific outbound restriction, sanctions nexus, or cross-border reporting threshold for crypto-asset transfers beyond the federal Bank Secrecy Act/FinCEN framework. Cross-border virtual-currency transmittals by Oregon-licensed money transmitters are governed by FinCEN's Funds Travel Rule and related BSA recordkeeping/reporting rules, applied uniformly nationwide.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
Crypto AML/CFT obligations (KYC/CDD, travel rule, SAR/STR reporting, sanctions screening, record-keeping, risk assessment) are addressed at the fleet level via the shared Financial Integrity Module (FIM) 'aml_ctf', to which this crypto consumer baseline subscribes. Per station instructions, this baseline does not independently produce aml_cft_regime claims for US-OR; any AML-relevant material encountered during research (e.g., FinCEN money-transmitter/MSB registration requirements applicable to Oregon-licensed crypto businesses) is disambiguation context only and is expected to be captured under the FIM sub_regime pattern rather than duplicated here.
Absence reason not determinableNo sub-brief exists and the JID records no gap or review marker explaining why. The renderer will not invent a reason.
No periodic updates recorded against this sub-brief.
No categories match.
Filters combine as OR inside a group and AND across
groups.
Editorial metadata
Provenance only. Nothing below gates publication or affects the render.
Editorial metadata for United States – Oregon
Field
Value
trust.lawyer_review.status
never_reviewed
trust.lawyer_review.reviewer
not recorded
trust.content_source
ai_generated
Provenance and declared absence
Disclosure model: module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is.
Sentinel-fed modules receive no special rendering treatment. sentinel_feed is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page.
Family taxonomy is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning.