Cryptoassets Regulatory Intelligence cryptoassets.gi
US-CT · run crypto-2026-08-06 v13.3.0
content: ai_generated 15 sources retrieved model claude-sonnet-5 ·

United States – Connecticut

US-CT schema crypto-v2.0.0 trajectory: not recordedregulatedoverlaps: FIM, WPM

Last updated · 8 categories · 25 sourced findings · 15 sources in the cumulative register

8Categoriesbaseline.
25Findings.claims[]
0Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 8 rendered categories; click to filter)
No categories moved this cycle.

Jurisdiction brief

No content recorded at this JID path.

8 of 8 categories
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

Connecticut has no bespoke crypto-asset licensing statute. Virtual-currency exchange, custody and transmission businesses fall under the state's general money-transmitter licensing (MTL) regime, administered via NMLS by the state banking/financial-institutions authority. In 2025 the legislature amended the MTL framework specifically as applied to crypto firms (Public Act 25-66 / H.B. 7082), tightening disclosure and consumer-facing obligations for licensees engaged in virtual-currency money transmission, while a separate provision of the same act bars Connecticut government entities from holding, investing in, or accepting payment in virtual currency. No CT-specific crypto exchange/custody license distinct from the MTL regime has been 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.

Sources and findings (2)
  1. T?source not recordedM5bindingin force
  2. T?source not recordedM3non-binding

#

Connecticut does not operate its own token-taxonomy regime; per the jurisdiction disambiguation, characterisation of crypto assets as securities, commodities, or payment stablecoins is governed by federal SEC/CFTC frameworks, applicable uniformly to Connecticut market participants. The SEC's 2026 interpretive release on the application of federal securities laws to crypto assets distinguishes digital commodities, digital collectibles, digital tools, stablecoins and digital securities, while the GENIUS Act separately confirms that compliant payment stablecoins are not securities.

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 (4)
  1. T?source not recordedM4non-binding
  2. T?source not recordedM4bindingenacted not yet effective
  3. T?source not recordedM3non-binding
  4. T?source not recordedM2non-binding

#

Connecticut has no state-specific regime governing on-chain activities such as staking, DeFi lending, mining, node operation, validation or tokenization. To the extent such activities involve money transmission, the general MTL law may apply; classification of protocol mining and protocol staking activities under federal securities/commodities law is addressed only at the federal level via SEC/CFTC interpretive guidance, not by any Connecticut-specific instrument.

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 (3)
  1. T?source not recordedM3non-binding
  2. T?source not recordedM3non-binding
  3. T?source not recordedM2non-binding

#

Connecticut has no independent stablecoin statute. The federal GENIUS Act (signed July 18, 2025) establishes the first comprehensive U.S. stablecoin framework, covering issuer permitting, 1:1 reserve backing, redemption rights, and disclosure, with implementing rules from the OCC, FDIC, NCUA, Federal Reserve and Treasury still at proposal stage as of mid-2026 and full operative effect no later than January 18, 2027. Treasury's proposed criteria for certifying a state regime as 'substantially similar' to the federal framework (relevant to any future Connecticut state-qualified issuer route) also remain unfinished.

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 (5)
  1. T?source not recordedM5bindingenacted not yet effective
  2. T?source not recordedM5bindingenacted not yet effective
  3. T?source not recordedM5bindingenacted not yet effective
  4. T?source not recordedM4bindingenacted not yet effective
  5. T?source not recordedM3non-binding

#

Connecticut's Public Act 25-66 (2025, H.B. 7082) introduced crypto-specific consumer protections layered on the general MTL regime: mandatory plain-language risk disclosure for crypto money-transmission businesses and a minor-protection requirement mandating legal-guardian verification for users under 18. No Connecticut-specific custody-segregation or complaint-handling rule specific to crypto was identified beyond general MTL bonding/net-worth 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.

Sources and findings (4)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM4bindingin force
  3. T?source not recordedM3non-binding
  4. T?source not recordedM2non-binding

#

Connecticut applies no crypto-specific state tax statute; federal tax treatment (IRS: crypto as property) sets the baseline that flows through to Connecticut's federally conformed income tax base. Capital gains arise on disposals; ordinary income arises on receipt via mining, staking, forks or compensation. A pending federal bill (PARITY Act) would create a de minimis exemption for small stablecoin payment transactions, but it is not yet enacted.

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 (4)
  1. T?source not recordedM4bindingin force
  2. T?source not recordedM4bindingin force
  3. T?source not recordedM2non-binding
  4. T?source not recordedM1non-binding

#

Connecticut has no independent cross-border crypto-transfer regime. Federal sanctions/OFAC screening and FinCEN Travel Rule-style analysis of virtual-currency transmittals apply uniformly nationwide, and the GENIUS Act layers Bank Secrecy Act and U.S. sanctions compliance obligations onto permitted stablecoin issuers, including a FinCEN/OFAC joint proposed rule implementing those 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.

Sources and findings (3)
  1. T?source not recordedM4non-binding
  2. T?source not recordedM3bindingin force
  3. T?source not recordedM2non-binding

#

Per the crypto consumer's module-subscription model, AML/CFT obligations are sourced from the shared FIM aml_ctf module rather than produced natively in this crypto baseline. No aml_cft_regime claims are emitted here; disambiguation context only: Connecticut crypto money-transmission licensees remain subject to federal Bank Secrecy Act obligations administered by FinCEN regardless of state licensing status.

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 – Connecticut
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewernot recorded
trust.content_sourceai_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.

Suppressed by doctrine: derived risk score; per-module RAG traffic light; derived_scores = {}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-08-17. A year-precision row is never promoted into a tighter band.

Orphan deltas: 0 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card.

Envelope: baseline resolved at jurisdiction_json.baseline; 8 module(s), 25 finding(s), 15 source(s) in the cumulative register.