Maryland has no bespoke crypto-asset licensing statute. <cite index="34-6,34-7">Any company that offers to exchange, administer, or maintain virtual currencies may be subject to state regulation and licensing, as well as federal regulation, and services that engage in converting, buying, selling or transmitting digital currencies must be registered as a money services business</cite>. Virtual-currency exchange, custody, and transmission businesses are therefore folded into Maryland's general Money Transmission Act (Financial Institutions Article) administered by the Office of the Commissioner of Financial Regulation (OCFR) via the NMLS licensing portal, rather than under a distinct crypto licence.
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.
Maryland has not adopted a state-level statutory taxonomy for crypto-assets. Per the injected disambiguation, token characterisation for securities purposes is governed by federal SEC/CFTC jurisdiction (see US JID) rather than by Maryland-specific rules. <cite index="87-1,87-2">The SEC provided interpretive guidance in 2026 on crypto assets under the federal securities laws, distinguishing digital commodities from other crypto asset categories</cite>, but this is a federal, not Maryland, classification scheme.
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.
Maryland has not legislated specifically on staking, DeFi lending, DEX operation, mining, node operation, validator activity, or tokenization. Any relevant guidance in this space (e.g., SEC staff statements on protocol staking and proof-of-work mining) originates at the federal level and does not create Maryland-specific obligations or exemptions.
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.
Maryland has no state-level stablecoin issuance-authorisation, reserve, or redemption regime. The federal GENIUS Act establishes the primary payment-stablecoin framework applicable nationwide, including to Maryland-domiciled issuers. <cite index="97-13">The GENIUS Act will become effective on the earlier of 18 months after its date of enactment (July 18, 2025) or the date that is 120 days after the date on which the primary Federal payment stablecoin regulators issue</cite> implementing rules, meaning the federal regime is still phasing in as of this research date.
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 recordedM4bindingenacted not yet effective
Maryland relies on general state consumer-protection law and the bonding/customer-fund provisions embedded in its general Money Transmission Act rather than any crypto-specific statute. Unlike several peer states, no Maryland-specific crypto-ATM/kiosk consumer-protection law (fee caps, transaction limits, fraud warnings) has been confirmed as enacted. <cite index="65-6,65-7">Illinois Governor JB Pritzker signed the Digital Asset Kiosk Act (SB 2319), which requires kiosk operators to register with state regulators, establish live customer service, and cap transaction fees at 18%, with daily transactions for new customers limited to $2,500</cite> — illustrating the type of regime Maryland has not been confirmed to have adopted. Federally, <cite index="61-3">in 2024, the FBI's IC3 received more than 10,956 complaints reporting the use of CVC kiosks, with reported victim losses of approximately $246.7 million</cite>, underscoring the fraud-risk backdrop against which Maryland's silence on kiosk-specific rules should be read.
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.
Maryland has not enacted crypto-specific tax statutes and is understood to follow the federal characterisation of virtual currency as property for income tax purposes, since Maryland's income tax base starts from federal adjusted gross income; a Maryland Comptroller-specific digital-asset tax bulletin was not located in this research pass. Federally, <cite index="57-2">the U.S. Internal Revenue Service (IRS) in 2014 decided bitcoin and other cryptocurrencies should be treated as "property", meaning they qualify for capital gains treatment similar to traditional assets like stocks and bonds</cite>, and new broker-reporting obligations have recently taken effect: <cite index="53-4,53-5">for the first time, cryptocurrency exchanges will issue Form 1099-DA, a new document that declares cost basis and proceeds directly to the IRS, with brokers required to issue them by February 17, 2026, covering all sales and exchanges from 2025</cite>.
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.
Maryland imposes no state-specific outbound restriction, reporting threshold, or travel-rule overlay on cross-border crypto transfers beyond the federal baseline. Cross-border virtual-currency transfers by Maryland persons/entities remain subject to federal OFAC sanctions and the FinCEN BSA travel-rule/reporting framework applicable nationwide. <cite index="40-2,40-3">OFAC designated Blender.io, which provided mixing services that were used by DPRK to launder over $20.5 million from the Axie Infinity Heist in May 2022, and also designated Tornado Cash, which provided mixing services that obfuscated the movement of over $455 million stolen in March 2022 by the OFAC-designated, North Korea-controlled Lazarus Group</cite>, illustrating the binding federal sanctions-nexus layer that applies regardless of Maryland's lack of a state-specific overlay.
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 applicable to Maryland-licensed virtual-currency money transmitters (BSA registration, travel rule, SAR filing, sanctions screening, recordkeeping) are governed by the federal Bank Secrecy Act / FinCEN MSB framework. Per fleet module-subscription doctrine, crypto subscribes to the shared Financial Integrity Module (FIM) `aml_ctf` baseline; no Maryland-specific AML/CFT claims are produced in this crypto DR baseline to avoid duplicative cross-consumer claims. Any AML-scope material surfaced during this research (e.g., FinCEN CVC-kiosk advisories) is disambiguation context only, not a crypto-baseline claim.
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 – Maryland
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.