Bulgaria applies the EU Markets in Crypto-Assets Regulation (MiCA, Regulation (EU) 2023/1114) directly, supplemented by a national implementing Law on Markets in Crypto-Assets (ZPKA, published Darzhaven Vestnik No. 67/2025) that entered into force 8 July 2025. Crypto-asset service providers (CASPs) require Article 63 MiCA authorisation from the Financial Supervision Commission (FSC), except for credit institutions providing crypto-asset services under Title V/Article 60(3), which the Bulgarian National Bank (BNB) supervises. A national grandfathering window allowed VASPs already on Bulgaria's national register to continue operating under prior national law provided they filed a MiCA Article 63 application by 8 October 2025; the EU-wide transitional regime for all Member States ended 1 July 2026, after which unauthorised crypto-asset service provision is a breach of EU law.
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.
Bulgaria transposes MiCA's tripartite crypto-asset taxonomy (asset-referenced tokens, e-money tokens, and other crypto-assets) without a distinct national classification scheme. The FSC applies ESMA's Guidelines on the qualification of crypto-assets as financial instruments to delineate MiCA-scope tokens from MiFID II-scope securities, implementing them through the national MiCA-transposing legislation rather than separate guidance.
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.
Neither MiCA nor Bulgaria's national implementing legislation establishes a dedicated licensing or prudential regime for on-chain activities such as staking, DeFi lending, mining, node operation, or validator services as distinct categories. These activities are only indirectly captured where they fall within MiCA's existing CASP service categories (e.g., custody and administration, or portfolio management of crypto-assets); genuinely decentralised, non-intermediated activity generally falls outside MiCA's scope by recital exclusion. This is a jurisdiction-wide (EU-level) gap rather than a Bulgaria-specific omission.
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.
MiCA Titles III and IV impose a comprehensive stablecoin regime directly applicable in Bulgaria. Asset-referenced token (ART) issuers require FSC authorisation; e-money token (EMT) issuance is restricted to credit institutions or authorised e-money institutions supervised by the Bulgarian National Bank. Both token types carry reserve-of-assets, redemption-right, and disclosure obligations.
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.
Consumer protection for crypto-asset holders and CASP clients in Bulgaria runs through directly-applicable MiCA obligations: mandatory white paper disclosure (now in machine-readable iXBRL format since 23 December 2025), restrictions on marketing communications, custody segregation duties for CASPs, and mandatory complaint-handling procedures. ESMA and NCAs, including the FSC, also issue public verification guidance directing consumers to the Interim MiCA Register.
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.
Bulgaria has no crypto-specific tax code; digital-asset gains are absorbed into the general flat-rate personal/corporate income tax system based on 2014 National Revenue Agency (NRA) administrative guidance that has not been publicly superseded. Layered on top from 1 January 2026 is the EU-wide DAC8 crypto-asset reporting regime, which is directly binding regardless of any gap in Bulgaria-specific guidance updates.
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.
Bulgaria's cross-border crypto-asset framework combines MiCA's single-market passporting regime for authorised CASPs, the crypto-asset 'travel rule' under Regulation (EU) 2023/1113, and DAC8's cross-border tax-data exchange. No Bulgaria-specific outbound capital restriction on crypto-assets was 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.
Crypto AML/CFT obligations are out of scope for this baseline: the crypto consumer subscribes to the FIM aml_ctf module and AML-specific claims are not produced here. For disambiguation context only: Bulgaria's AML framework for virtual-asset service providers runs through the Law on Measures against Money Laundering (LMML), with the Financial Intelligence Directorate (FID-SANS) and, per MONEYVAL's follow-up assessment, some technical deficiencies remain around VASP-specific supervision, new-technology risk assessment, and fit-and-proper checks.
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 Bulgaria
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.