Washington State has no bespoke crypto-asset licensing statute. Virtual currency businesses (exchanges, custodians, exchangers) are brought within the state's general money-transmitter regime — the Uniform Money Services Act (RCW 19.230) — via 2017's Senate Bill 5031, effective July 23, 2017. Businesses conducting money transmission involving virtual currency must obtain a license from the Washington State Department of Financial Institutions (DFI), administered through NMLS, and comply with bonding, disclosure, and (for custodial operators) third-party security-audit requirements.
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.
Washington has no state-level token classification framework. Whether a given crypto asset is a security, commodity, or other instrument is determined at the federal level by the SEC and CFTC (see US federal JID); the state licensing regime addresses money-transmission and custody activity only, not the legal character of the underlying token.
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.
Washington has no state-specific licensing or regulatory regime that separately addresses on-chain activities such as staking, DeFi lending, DEX operation, node operation, validation, or tokenization. These activities would only be captured incidentally if they meet the general money-transmission definition under RCW 19.230. At the federal level, FinCEN has clarified that a person who mines convertible virtual currency solely for their own purposes is not a money transmitter, which is the only closely on-point interpretive guidance bearing on on-chain activity and is federal, not Washington-specific.
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.
Washington has no state-level stablecoin issuance, reserve, redemption, disclosure, or systemic-designation regime. Stablecoin issuance in the U.S. is increasingly governed at the federal level (e.g., the GENIUS Act framework referenced in federal payment-stablecoin legislative activity), which would apply to any Washington-domiciled issuer, but no Washington-specific stablecoin statute was identified.
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.
Washington's SB 5031 amendments to the Uniform Money Services Act impose specific consumer-facing obligations on virtual currency licensees: disclosure of whether products are insured/guaranteed, an itemized list of fees and charges, and rules restricting the use of license/trade names confusingly similar to existing licensees.
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.
Washington State levies no general state personal income tax, so cryptocurrency capital gains are not subject to a Washington-specific state income tax layer (federal IRS treatment of digital assets as property, generating capital gains/losses on disposition, still applies). Washington does operate a state capital gains excise tax (RCW 82.87) on certain long-term gains above a statutory threshold, but no Department of Revenue guidance confirming or excluding cryptocurrency from that excise tax's scope was located in this pass — this is flagged as an open question requiring primary-source escalation.
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 Washington-specific restriction on outbound or cross-border cryptocurrency transfers was identified. Cross-border transmission is governed by the same state money-transmission licensing framework applicable to domestic transfers, layered under federal sanctions (OFAC) and FinCEN funds-travel-rule requirements, neither of which is Washington-specific.
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.
AML/CFT obligations for crypto businesses (KYC/CDD, travel rule, SAR/STR reporting, sanctions screening, record-keeping, risk assessment) are addressed under the crypto consumer's subscription to the FIM aml_ctf module rather than in this baseline. This module is emitted for structural completeness only; substantive AML/CFT claims are intentionally out of scope here per the fleet subscription model. For disambiguation context only: federal FinCEN guidance treats virtual-currency administrators and exchangers as money transmitters/MSBs subject to BSA obligations, which is the substrate the FIM module draws upon.
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.
Sources and findings (1)
T?source not recordedM1non-binding
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 – Washington
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.