Cryptoassets Regulatory Intelligence cryptoassets.gi
US-KY v13.3.0
content: ai_generated legal review: never_reviewed (informational) publication gate: 1 failing10 sources retrieved model claude-sonnet-5 · 2026-08-06

Kentucky, USA

US-KY schema crypto-v2.0.0 trajectory: not yet assessedregulatedoverlaps: FIM, WPM

Last updated · 8 categories · 17 sourced findings · 13 sources in the cumulative register

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

Jurisdiction lead brief

Lead Signal

Kentucky's HB 701 (2025) remains the single most consequential development shaping the state's digital-asset posture, but this cycle's most important development is not new legislation -- it is a correction to how the existing law had been characterized. The statute's money-transmitter-licensing exemption, codified at KRS 286.11-007, covers home digital-asset mining, digital-asset mining businesses, and node operation. It does not extend to staking. An earlier characterization treating staking as falling within that same licensing carve-out has been reviewed and corrected: staking-as-a-service is addressed through a separate HB 701 amendment to KRS 292.340, which excludes it from securities classification rather than from money-transmission licensing. The distinction matters operationally -- a mining or node-operation business relying on the licensing exemption is standing on different statutory ground than a staking-service provider relying on the securities-law exclusion, and conflating the two overstates the breadth of Kentucky's money-transmitter carve-out. HB 701 separately guarantees individuals' right to hold and manage crypto assets in self-hosted wallets without money-transmission-licensing interference, reinforcing Kentucky's broader self-custody posture. Confidence across the HB 701-derived claims in this cycle has been normalized to Probable rather than Confirmed: the underlying record rests on a single secondary source (a LegiScan bill summary and The Block reporting) for a binding, high-materiality statutory claim, and primary statutory text has not yet been independently retrieved.

8 of 8 categories
Signal
Density

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

#

Kentucky has no bespoke crypto-exchange or custody licence separate from its general money-transmitter law administered by the Kentucky Department of Financial Institutions (KY DFI). HB 701 (2025) carved out explicit statutory exemptions from money-transmitter regulation for self-hosted wallet custody, blockchain node operation and staking activity, but the underlying general MTL statute's exact KRS citation and scope as applied to exchanges/custodians has not been independently verified against primary statutory text in this pass.

Open gap — crypto-int-1Exact KRS chapter/section citation for Kentucky's general money-transmitter licensing statute as applied to virtual-currency exchanges/custodians has not been independently pulled from primary statutory text; research should fetch the Kentucky Revised Statutes directly (apps.legislature.ky.gov) to confirm scope and any additional crypto-specific carve-outs.no under-indexing note recorded
Open gap — crypto-int-5Underlying enrolled bill texts (HB 701, SB 255, HB 230) and their KRS citations were not independently pulled from the Kentucky Legislature site (apps.legislature.ky.gov); this pass relied on T4 secondary news reporting for statutory content across crypto_licensing, token_classification, on_chain_activity_regime, and tax_treatment.no under-indexing note recorded
Open gap — crypto-int-6Whether Kentucky's dual MTL (KY DFI) plus Division of Securities Blue Sky overlay warrants a sub-JID split for the sub_regime discriminator (analogous to AE-VARA/AE-ADGM/AE-DIFC) has not been assessed by the Architect; flagged for consideration but not resolved this cycle.no under-indexing note recorded
Standing sub-brief425 words · last cycle 2026-08-06

Crypto Licensing

Kentucky's crypto-licensing posture rests on two layers. The first is the state's general money-transmitter-licensing statute, administered by the Department of Financial Institutions, which presumptively applies to virtual-currency exchange and custody businesses operating in the state absent an applicable carve-out. The exact KRS chapter and section governing that general obligation as specifically applied to virtual-currency businesses has not been independently pulled from primary statutory text this cycle; this is a tracked evidentiary gap rather than a resolved finding. The second and more consequential layer is House Bill 701 (2025), which introduced Kentucky's first dedicated digital-asset carve-outs. HB 701's amendment to KRS 286.11-007 exempts home digital-asset mining, digital-asset mining businesses, and node operation from the state's money-transmitter-licensing requirement. This cycle corrected an earlier characterization that had extended this same exemption to staking activity -- staking is not covered by the KRS 286.11-007 licensing carve-out. Staking is instead addressed by a separate HB 701 amendment to KRS 292.340, which excludes staking-as-a-service from securities classification rather than from money-transmission licensing. The two carve-outs run on parallel but distinct statutory tracks, and treating them as a single blanket exemption overstates the breadth of Kentucky's licensing relief. HB 701 also affirmatively guarantees individuals' right to hold and manage crypto assets in self-hosted, non-custodial wallets without interference from money-transmission-licensing requirements, which functions as a self-custody protection layered on top of the narrower business-activity exemptions. Confidence on the HB 701-derived licensing claims has been normalized to Probable: the operative record for both the exemption scope and the self-custody guarantee rests on a single secondary source (a LegiScan bill summary and a single news account) for claims that are binding and materially significant, and primary enrolled-bill or KRS text has not yet been independently retrieved to support a higher confidence tier. Taken together, Kentucky's licensing regime reads as narrower and more precisely scoped than an initial pass suggested, but the underlying evidentiary base for both the narrow exemption and the general MTL baseline remains thinner than the statutory claims' materiality would ideally warrant.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (3)
  1. T4 · The BlockThe Block — Operating blockchain nodes and engaging in staking activities are explicitly exempted from Kentucky's money transmitter regulations under HB 701.retrieved M4bindingin force
  2. T4 · The BlockThe Block — HB 701 guarantees individuals the right to hold and manage crypto in self-hosted wallets, protecting self-custody activity from money-transmission licensing interference.retrieved M4bindingin force
  3. T1 · FinCENFinCEN — Virtual-currency exchange and custody businesses operating in Kentucky are presumptively subject to the state's general money-transmitter licensing regime administered by KY DFI, absent an applicable HB 701 carve-out.retrieved M4bindingin forceour coverage gap, expected to resolve on a re-run

#

Kentucky has no bespoke state token taxonomy. HB 701 (2025) statutorily clarifies that mining and staking services are not classified as securities under Kentucky law. Separately, the Kentucky Division of Securities (within KY DFI) has, through enforcement actions predating HB 701, treated certain yield-bearing crypto lending products (e.g., Celsius, BlockFi) as securities under state Blue Sky law. Federal SEC/CFTC characterisation continues to govern token-as-security/commodity status generally (see US federal JID).

Standing sub-brief383 words · last cycle 2026-08-06

Token Classification

Kentucky's token-classification picture combines a recent statutory clarification with an older line of enforcement precedent that continues to matter. HB 701's amendment to KRS 292.340 clarifies that digital-asset mining and staking-as-a-service are not classified as securities under Kentucky law, giving those two activity categories reasonably clear statutory footing going forward. That clarification is corrected this cycle to properly attribute the staking carve-out to securities law (KRS 292.340) rather than to the money-transmitter-licensing statute, consistent with the correction applied in the licensing and on-chain-activity modules. Confidence on this clarification is Probable, again reflecting reliance on a single secondary source for the underlying statutory text. Sitting alongside that clarification is a distinct and separately sourced body of enforcement history showing that Kentucky regulators have been willing to classify other crypto product structures as securities under the state's Blue Sky law. In 2021, the Kentucky Division of Securities determined that Celsius Network's interest-bearing crypto accounts constituted securities in the form of investment contracts and issued a cease-and-desist order on that basis. In the same year, the Department of Financial Institutions issued an order barring BlockFi from soliciting or offering securities in Kentucky in connection with its own interest-bearing crypto accounts. Both actions rest on single-source news reporting rather than the underlying regulatory order text, so confidence on each is held at Probable pending independent retrieval of the orders themselves. Read together, the statutory clarification and the enforcement history point in the same direction rather than in tension: Kentucky has drawn a reasonably clear line exempting mining and staking-as-a-service from securities treatment while continuing to treat other yield-bearing or interest-bearing crypto product structures on a case-by-case basis under existing securities law. The practical takeaway for anyone assessing a Kentucky-facing crypto product is that the mining/staking carve-out is narrow and activity-specific -- it does not amount to a general exemption for yield-generating crypto financial products.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (3)
  1. T4 · The BlockThe Block — HB 701 clarifies that mining and staking services are not classified as securities under Kentucky law.retrieved M4bindingin force
  2. T4 · CoinDeskCoinDesk — Kentucky's Division of Securities determined that Celsius Network's interest-bearing crypto accounts constituted securities in the form of investment contracts and issued a cease-and-desist order.retrieved M4bindingin force
  3. T4 · The BlockThe Block — The Kentucky Department of Financial Institutions issued BlockFi an order barring it from soliciting or offering securities in the state in connection with its interest-bearing crypto accounts.retrieved M4bindingin force

#

Kentucky is one of the more permissive US states for on-chain infrastructure activity: HB 701 (2025) statutorily exempts node operation and staking from money-transmitter licensing and bars local governments from discriminatory ordinances against mining operations, while separate 2021 legislation (SB 255, HB 230) grants tax incentives to large-scale crypto miners.

Standing sub-brief346 words · last cycle 2026-08-06

On-Chain Activity Regime

Kentucky's treatment of on-chain activity is shaped primarily by HB 701 (2025) and by two 2021 tax-incentive statutes. HB 701's amendment to KRS 286.11-007 exempts operation of blockchain nodes from the state's money-transmitter-licensing requirements. This cycle corrected an earlier characterization that had extended the same licensing exemption to staking activity: staking is excluded from the KRS 286.11-007 money-transmitter-licensing exemption and is instead addressed through HB 701's separate amendment to KRS 292.340, which clarifies that staking-as-a-service is not a security. The correction narrows the previously stated scope of licensing relief for staking without removing Kentucky's affirmative statutory position on staking generally -- it simply relocates that position from the licensing track to the securities track. HB 701 also prohibits Kentucky local governments from enacting discriminatory ordinances that unfairly target crypto-mining operations, an affirmative protection for mining infrastructure at the municipal level. Layered underneath these 2025 provisions is Senate Bill 255 (2021), which extends clean-energy-focused state tax incentives to cryptocurrency-mining operations that invest at least $1 million in equipment in Kentucky -- a mining-specific benefit that predates HB 701 by roughly four years and that this module tracks from the activity-regime angle (the same underlying fact is tracked from the tax-treatment angle in that module, reflecting the two distinct regulatory lenses the underlying incentive touches). Confidence across this module's claims is Probable throughout, reflecting single-source (predominantly T4 news, with the LegiScan bill summary as the T3 anchor for HB 701 language) sourcing for claims that are binding and materially significant. No countervailing restriction on mining, node operation, or staking activity was identified in Kentucky this cycle; the overall direction across this module is affirmatively permissive relative to most other US states surveyed to date.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (4)
  1. T4 · The BlockThe Block — Engaging in staking activities is explicitly exempted from Kentucky's money transmitter regulations under HB 701.retrieved M4bindingin force
  2. T4 · The BlockThe Block — Operating blockchain nodes is explicitly exempted from Kentucky's money transmitter regulations under HB 701.retrieved M4bindingin force
  3. T4 · The BlockThe Block — HB 701 prohibits local governments in Kentucky from enacting discriminatory laws that unfairly target crypto mining operations.retrieved M3bindingin force
  4. T4 · CoinDeskCoinDesk — Senate Bill 255 (2021) extends Kentucky's clean-energy-focused tax incentives to cryptocurrency miners who invest at least $1 million in equipment.retrieved M3bindingin force

#

Kentucky has no bespoke state stablecoin-issuance statute. Stablecoin issuance is governed at the federal level by the GENIUS Act (2025), which, prior to full implementation, recognizes state-regulated money transmitters and state-regulated trust companies (categories into which a KY-licensed entity could potentially fall) as eligible payment-stablecoin issuers; federal implementing rules remain in progress as of mid-2026.

Open gap — crypto-int-4Federal GENIUS Act implementing rules for payment-stablecoin issuance remain in progress; specific applicability of the state-regulated money-transmitter/trust-company issuer pathway to a named KY-chartered entity has not been confirmed. No forward date was available in evidence to seed a regulatory_horizon item; monitor for a published implementing-rule timeline.no under-indexing note recorded
Standing sub-brief280 words · last cycle 2026-08-06

Stablecoin Regime

Kentucky has no stablecoin-specific statute of its own, so this module's content is entirely a federal overlay. The federal GENIUS Act (Pub. L. 119-27) permits USD-denominated payment stablecoins issued by state-regulated money transmitters or state-regulated trust companies to qualify under the federal payment-stablecoin definition, and that issuer category could, in principle, include Kentucky-licensed money transmitters or trust companies. That said, two important qualifications apply. First, whether any specific Kentucky-licensed or Kentucky-chartered entity has actually availed itself of, or been confirmed eligible for, the state-regulated-issuer pathway has not been established this cycle -- the claim describes a structural possibility under the federal statute, not a confirmed Kentucky-specific outcome. Second, the GENIUS Act's implementing rules remain in progress at the federal level, so the precise contours of eligibility, supervision, and reserve requirements for a state-regulated issuer are not yet finalized. Confidence on this claim is held at Probable to reflect both the structural (rather than confirmed-applied) nature of the finding and the fact that federal implementing detail is still being worked out. No forward date was available in the evidence base to seed a specific regulatory-horizon milestone for rule finalization; this is tracked as an open monitoring item rather than a dated event.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (1)
  1. T1 · U.S. Securities and Exchange CommissionU.S. Securities and Exchange Commission — Prior to the GENIUS Act's full implementation, a USD-denominated payment stablecoin issued by a state-regulated money transmitter or state-regulated trust company (potentially including a KY-licensed entity) can qualify under the federal definition, though Kentucky has no independent stablecoin-specific statute of its own.retrieved M3bindingin force

#

Kentucky consumer protection in crypto has to date been enforced primarily through securities law actions by the Division of Securities (part of KY DFI) against yield-bearing crypto lending products (Celsius, BlockFi), rather than through a dedicated crypto consumer-protection statute. A pending 2026 bill, HB 380, would establish licensing, transaction limits and consumer-protection requirements for virtual-currency kiosk (crypto ATM) operators; a contested floor amendment (Section 33) would additionally require hardware-wallet providers to offer credential-reset mechanisms, which critics argue undermines self-custody protections established by HB 701. As of the dispatch date, HB 380's final enactment status was not confirmed in this pass.

Open gap — crypto-int-2House Bill 380 (2026), including the contested hardware-wallet credential-reset provision (Section 33), has not been confirmed as enacted, further amended, or failed in the 2026 legislative session; research should check the Kentucky General Assembly's current bill-status page.no under-indexing note recorded
Standing sub-brief326 words · last cycle 2026-08-06

Consumer Protection

Kentucky's crypto consumer-protection posture is built primarily on securities-enforcement precedent rather than a dedicated consumer-protection statute for digital assets. In 2021, the Kentucky Division of Securities found that Celsius Network's interest-bearing crypto accounts exposed consumers to what it characterized as unprecedented risks and that the company had failed to adequately disclose how customer deposits were treated, leading to a cease-and-desist order. In the same year, the Department of Financial Institutions ordered BlockFi to stop opening new interest-account customers in Kentucky, alleging that the product constituted an unregistered security sold without adequate investor protections. Both actions function as the state's operative consumer-protection precedent for yield-bearing crypto products, covering risk-disclosure adequacy and product suitability respectively, even though neither rests on a crypto-specific consumer-protection statute. Both are sourced to single secondary news accounts rather than the underlying regulatory order text, so confidence on each sits at Probable. Layered on top of this enforcement-derived baseline is a live and unresolved legislative item: a floor amendment (Section 33) to House Bill 380 (2026), a bill primarily concerned with crypto-ATM/kiosk regulation, would require hardware-wallet providers to offer a mechanism to assist any person in resetting wallet-access credentials. Critics argue this provision is in direct tension with the non-custodial self-custody design protections that HB 701 established elsewhere in Kentucky's digital-asset framework -- a credential-reset mandate sits uneasily alongside a legal guarantee of self-hosted wallet control. HB 380's enactment status as of the current legislative session has not been confirmed, and confidence on this claim is accordingly held at Uncertain rather than Probable.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (3)
  1. T4 · CoinDeskCoinDesk — Kentucky's Division of Securities found that Celsius Network's crypto interest accounts exposed consumers to 'unprecedented risks' and failed to adequately disclose the treatment of customer deposits, leading to a cease-and-desist order.retrieved M4bindingin force
  2. T4 · The BlockThe Block — Kentucky ordered BlockFi to stop opening new interest-account customers in the state, alleging the product constituted an unregistered security sold without adequate investor protections.retrieved M4bindingin force
  3. T4 · The BlockThe Block — A floor amendment to pending Kentucky House Bill 380 would require hardware-wallet providers to provide a mechanism to assist any person in resetting wallet-access credentials, a provision critics argue is incompatible with non-custodial self-custody design.retrieved M3non-binding

#

Kentucky has enacted targeted tax incentives for large-scale crypto mining operations (SB 255 and HB 230, both 2021) but has no confirmed bespoke individual-level crypto capital-gains or income-tax treatment distinct from federal conformity; this latter point was not independently verified against Kentucky Department of Revenue guidance in this pass and is flagged as a research gap.

Open gap — crypto-int-3Kentucky Department of Revenue guidance on individual-level state income/capital-gains tax treatment of crypto transactions distinct from federal conformity has not been located or confirmed.tax_treatment is a structurally thin-coverage module across the crypto estate per BIAS CORRECTIONS; this gap reflects that pattern.
Standing sub-brief298 words · last cycle 2026-08-06

Tax Treatment

Kentucky's crypto-adjacent tax treatment is evidenced almost entirely at the mining-operator level rather than the individual-taxpayer level. House Bill 230 (2021) grants a series of sales and excise tax breaks to cryptocurrency-mining operations in Kentucky. Senate Bill 255, enacted the same year, extends clean-energy-focused tax incentives to crypto-mining operations that invest at least $1 million in equipment in the state; the exact tax type underlying that incentive mechanism -- whether it operates through income tax, property tax, or franchise tax channels -- has not been confirmed against primary Department of Revenue or enrolled-bill text this cycle. Both claims rest on a single secondary news source (the same underlying CoinDesk report covers both bills' signing), and confidence on each is held at Probable, consistent with the AUTO-DOWNGRADE discipline applied to single-source statutory claims generally and with tax_treatment's structurally thinner sourcing bar across the broader crypto-jurisdiction estate. What remains entirely unconfirmed is the individual-level side of the picture: whether Kentucky publishes any guidance on state income or capital-gains tax treatment of crypto transactions that departs from, or simply conforms to, federal treatment. No such guidance was located in this cycle's evidence base, and this is tracked as an open gap rather than a negative finding -- an absence of confirmed guidance is not the same as confirmation that no distinct state treatment exists.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (2)
  1. T4 · CoinDeskCoinDesk — House Bill 230 (2021) offers cryptocurrency miners a series of sales and excise tax breaks in Kentucky.retrieved M3bindingin force
  2. T4 · CoinDeskCoinDesk — Senate Bill 255 (2021) extends clean-energy-focused tax incentives to crypto-mining operations investing at least $1 million in equipment in Kentucky.retrieved M3bindingin forceour coverage gap, expected to resolve on a re-run

#

Kentucky imposes no identified state-specific restriction on outbound or cross-border crypto transfers beyond the federal Bank Secrecy Act framework, including FinCEN's money-transmitter/travel-rule obligations and OFAC sanctions screening, which apply uniformly nationwide to any Kentucky-licensed or Kentucky-based virtual-asset business acting as an exchanger or administrator.

Standing sub-brief245 words · last cycle 2026-08-06

Cross-Border Transfer

Kentucky has no state-specific cross-border transfer restriction for crypto activity; the operative framework here is entirely federal. FinCEN's Bank Secrecy Act framework classifies administrators and exchangers of convertible virtual currency who accept and transmit value, or who buy or sell virtual currency for currency or other value, as money transmitters subject to travel-rule and reporting obligations. That federal baseline applies uniformly to Kentucky-based virtual-currency businesses absent any state-specific carve-out, and none was identified this cycle. Confidence on this claim is held at Probable rather than Confirmed: the claim rests on a single T1 anchor (FinCEN's 2019 convertible-virtual-currency guidance), and this monitor's confidence discipline requires at least two independent T1-T2 anchors before a well-established federal baseline claim can be rated Confirmed, notwithstanding that FinCEN guidance itself is a primary regulatory source. This is a sourcing-discipline distinction rather than a substantive doubt about the underlying federal rule, which is long-standing and not itself contested.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (1)
  1. T1 · FinCENFinCEN — An administrator or exchanger of convertible virtual currency that accepts and transmits value, or buys/sells virtual currency for currency or other value, is a money transmitter subject to FinCEN's BSA travel-rule and reporting obligations, a federal baseline applicable to Kentucky-based virtual-currency businesses absent a state-specific carve-out.retrieved M3bindingin force

#

AML/CFT obligations applicable to Kentucky-based virtual-asset businesses (KYC/CDD, SAR/STR reporting, sanctions screening, recordkeeping, risk assessment) are governed at the federal level under the Bank Secrecy Act/FinCEN MSB framework and are covered under the crypto consumer's subscription to the FIM aml_ctf module rather than produced natively in this baseline. No Kentucky-specific AML overlay beyond the federal BSA framework was identified in this pass.

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 on record for this sub-brief

No categories match.

Filters combine as OR inside a group and AND across groups.

Publication gate

Blocking. 1 failing check(s).

schema_validFAIL
min_quoted_text_presentwaived — floor 0%
egress_verifiedpass
every_practical_object_has_source_idn/a — no subject in this jurisdiction
source_tier_integrity_okpass
jurisdiction_source_floor_metpass
tier_a_b_national_primary_pct40.0
aggregator_only_jurisdiction_count0
manual_override

Editorial metadata

Provenance only. Nothing below gates publication or affects the render.

Editorial metadata for Kentucky, USA
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewerno reviewer on record
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-09-27. 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), 17 finding(s), 13 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.