British Columbia has no bespoke provincial crypto-VASP license. Crypto trading platforms (CTPs) serving BC residents register federally/provincially through the Canadian Securities Administrators (CSA) passport system, with the British Columbia Securities Commission (BCSC) acting as principal or non-principal regulator alongside the Ontario Securities Commission (OSC) and other provincial members. The dominant registration category is the interim 'restricted dealer'/'restricted marketplace' form, with unregistered platforms required to file a Pre-Registration Undertaking (PRU) while pursuing full registration.
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.
The CSA does not classify most cryptocurrencies (e.g. bitcoin) as securities themselves, but deems the contractual claim a client holds against a custodial trading platform (a 'crypto contract') to be a security, bringing platforms under securities law regardless of the underlying asset's status. Tokenized traditional financial instruments are generally regulated under the same laws as their non-tokenized equivalents. Stablecoins have historically fallen into a classification gap, at times treated as securities or derivatives absent bespoke legislation, a gap the federal Stablecoin Act is intended to close.
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.
British Columbia has moved to restrict one on-chain activity directly — proof-of-work mining — by banning new grid connections for crypto mining, framed as electricity-supply protection rather than crypto-market regulation. Staking is permitted within regulated custodial products (e.g. staking-enabled ETFs), while DeFi and more advanced on-chain products remain largely unavailable to Canadian retail users pending regulatory clarity.
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.
Canada is establishing a federal stablecoin framework under Bank of Canada oversight. Budget 2025 committed to a Stablecoins Act requiring issuer registration, 1:1 reserves, redemption policies and risk-management frameworks, alongside amendments to the Retail Payment Activities Act; the government's budget package (including the stablecoin policy) narrowly passed Parliament. Implementation remains ongoing: the Bank of Canada has flagged stablecoin regulation and consumer-driven banking as new responsibilities to begin the following year, and provincial securities regulators (e.g. Alberta Treasury Board and Finance, Ontario Securities Commission) have separately approved individual CAD-pegged stablecoin issuers ahead of the federal regime taking full effect. CAUTION: federal Stablecoins Act implementation timeline and final in-force status should be treated as pre-final pending primary-source confirmation.
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)
T?source not recordedM5bindingproposed
T?source not recordedM5bindingenacted not yet effective
Consumer protection for crypto in BC operates through the national CSA/CIRO registrant framework: registered dealers/marketplaces must segregate client and proprietary assets, use acceptable custodians, avoid margin/leverage for retail crypto clients, and comply with CIRO's newly introduced tiered Digital Asset Custody Framework developed in response to the QuadrigaCX collapse.
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.
The CRA (Canada's federal tax authority, applicable in BC) applies existing Income Tax Act concepts to crypto rather than crypto-specific statutory rules: barter-transaction rules apply when crypto is used to pay for goods/services, and commodity/capital-versus-business-income rules apply to trading gains. The CRA has acknowledged significant enforcement limitations, estimating around 40% of crypto-platform users are non-compliant or at high risk, and has pursued court-ordered data disclosures from Canadian platforms (Coinsquare, Dapper Labs) to improve detection.
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.
Canada imposes no crypto-specific outbound capital control, but foreign crypto platforms serving Canadian residents (including BC) must meet the same registration/custody requirements as domestic platforms or block Canadian users, and federally-regulated reporting entities are subject to FINTRAC cross-border electronic funds transfer (EFT) reporting rules that extend to crypto-related transfers. Cross-border product access (e.g. U.S. CFTC-regulated crypto futures) has in some cases been enabled only through narrow, case-by-case Canadian regulatory exemptions rather than blanket permission.
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 (FINTRAC registration as a money services business, KYC/CDD, STR/SAR reporting) are out of scope for this baseline because crypto subscribes to the shared Financial Integrity Module (FIM) aml_ctf regime rather than duplicating it here. This module is emitted structurally per the module list but intentionally carries no aml_cft-specific claims in the crypto DR baseline; FINTRAC-related material found during research is captured only as disambiguation context in cross_border_transfer.
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 Canada – British Columbia
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.