Pennsylvania has no bespoke crypto-asset licensing statute. Crypto exchange, custody and transmission activity is assessed under the state's general Money Transmission Business Licensing Law, administered by the Department of Banking and Securities (DoBS). In 2019 DoBS issued guidance holding that crypto exchanges which never directly handle fiat currency (transacting instead through bank-account transfers) are not 'money transmitters' and therefore fall outside the licensing requirement, since virtual currency is not 'money' under the statute. Businesses that do directly accept and transmit fiat currency for a fee in connection with crypto activity remain within the general MTL regime, licensed via NMLS. No update to this 2019 position has been identified as of the current run 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.
Pennsylvania has not codified its own token taxonomy. Per the disambiguation seed, characterisation of a given token as a security, commodity, stablecoin or other instrument is governed by federal SEC/CFTC frameworks rather than state law, and applies uniformly within Pennsylvania absent any state override.
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.
Pennsylvania has no bespoke licensing or permitting regime specific to staking, DeFi/DEX activity, node operation, validation, or tokenization. The only on-chain activity to draw dedicated legislative attention has been bitcoin mining: a 2023 proposal to ban crypto mining, folded into an energy-conservation bill, was scrapped by its sponsor before the bill advanced, leaving mining without a state-level prohibition (subject only to general environmental/energy permitting for power-generation facilities).
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.
Pennsylvania has no state-specific stablecoin-issuance, reserve, redemption, disclosure, or systemic-designation regime. Stablecoin issuance authorisation and reserve/redemption standards are governed federally under the GENIUS Act, which applies within Pennsylvania in the absence of any state override.
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.
General Pennsylvania consumer-protection law applies to crypto activity in the absence of crypto-specific rules. House Bill 2481 ('Bitcoin Rights'), which would clarify residents' rights to self-custody digital assets alongside bitcoin-payment and taxation guidance, passed the Pennsylvania House in October 2024 by a 176-26 vote but had not been confirmed as enacted into law by the Senate as of the current run date, leaving self-custody protections in a proposed, non-binding state.
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.
Pennsylvania has not enacted crypto-specific tax legislation; digital assets are taxed under general state personal income tax rules layered on top of the federal property-based tax treatment (IRS treats crypto as property, giving rise to capital gains/loss on disposition and ordinary income treatment for staking/mining rewards). House Bill 2481 included proposed guidelines for taxing bitcoin transactions, but this provision had not been confirmed enacted as of the current run 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.
Pennsylvania imposes no state-specific outbound restriction, reporting threshold, or cross-border travel-rule regime on crypto transfers. Cross-border crypto transfers originating from or destined to Pennsylvania are governed exclusively by federal sanctions (OFAC) and BSA/FinCEN cross-border reporting frameworks, with no Pennsylvania overlay 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.
AML/CFT obligations for crypto businesses in Pennsylvania (KYC/CDD, travel rule, SAR/STR reporting, sanctions screening, record-keeping, risk assessment) are addressed at the fleet level under the crypto consumer's subscription to the Financial Integrity Module (FIM) aml_ctf baseline (federal BSA/FinCEN regime). Per station doctrine, this baseline does not independently produce aml_ctf/aml_cft claims; any AML-relevant material surfaced during Pennsylvania research is disambiguation context only and is not 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 – Pennsylvania
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.