[{"data":1,"prerenderedAt":863},["ShallowReactive",2],{"navigation":3,"/blog/dac8-compliance-guide":31,"/blog/dac8-compliance-guide-surround":852},[4,22],{"title":5,"path":6,"stem":7,"children":8,"page":21},"Introduction","/docs/introduction","1.docs/2.introduction",[9,13,17],{"title":10,"path":11,"stem":12},"Why","/docs/introduction/why","1.docs/2.introduction/1.why",{"title":14,"path":15,"stem":16},"Blockchain as solution?","/docs/introduction/blockchain-as-solution","1.docs/2.introduction/2.blockchain-as-solution",{"title":18,"path":19,"stem":20},"What's the Solution?","/docs/introduction/wag3s-as-solution","1.docs/2.introduction/3.wag3s-as-solution",false,{"title":23,"path":24,"stem":25,"children":26,"page":21},"Api Documentation","/docs/api-documentation","1.docs/3.api-documentation",[27],{"title":28,"path":29,"stem":30},"getting started","/docs/api-documentation/api","1.docs/3.api-documentation/1.api",{"id":32,"title":33,"authors":34,"badge":41,"body":43,"date":814,"description":815,"disclaimer":816,"extension":817,"faqs":818,"image":837,"meta":838,"navigation":846,"path":847,"reviewedBy":848,"reviewedDate":814,"seo":849,"stem":850,"__hash__":851},"posts/3.blog/49.dac8-compliance-guide.md","DAC8 Compliance Guide 2026: EU Crypto Reporting for CASPs",[35],{"name":36,"to":37,"avatar":38,"description":40},"Wag3s Team","https://x.com/W3Wag3s",{"src":39},"https://pbs.twimg.com/profile_images/1720428793699926016/yofJTeB6_400x400.jpg","Editorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.",{"label":42},"Regulation — EU",{"type":44,"value":45,"toc":791},"minimark",[46,50,54,57,60,65,82,91,114,117,121,124,136,139,182,185,205,212,216,219,322,325,328,332,335,369,376,380,434,437,441,444,506,509,513,516,521,535,539,550,554,571,575,586,590,598,602,605,631,635,638,676,680,688,705,708,712,752,756],[47,48,33],"h1",{"id":49},"dac8-compliance-guide-2026-eu-crypto-reporting-for-casps",[51,52,53],"p",{},"DAC8 is the EU-level implementation of the OECD's Crypto-Asset Reporting Framework (CARF). It became applicable on 1 January 2026 and requires every MiCA-licensed Crypto-Asset Service Provider (CASP) serving EU-resident users to collect transaction-level customer data and report it annually to a home-state tax authority. The first reporting period covers calendar year 2026; the first report is due by 31 January 2027.",[51,55,56],{},"For crypto businesses operating in or selling to the EU, DAC8 is operationally a heavier lift than MiCA itself. MiCA defines who can offer crypto services; DAC8 defines what they must report about every customer who uses those services. A small exchange with 10,000 EU customers ends up filing a structured XML report covering all of them every year, with self-certification and due-diligence trails that must withstand audit.",[51,58,59],{},"This guide covers what DAC8 requires, who's in scope, the data that must be collected, the reporting deadlines, the penalty regime, and how to design an operational workflow that doesn't crater the user-experience or product roadmap. It's written for compliance leads, finance teams, and engineering leads at MiCA-licensed CASPs and adjacent service providers.",[61,62,64],"h2",{"id":63},"what-dac8-actually-is","What DAC8 actually is",[51,66,67,68,75,76,81],{},"DAC8 is the eighth amendment to ",[69,70,74],"a",{"href":71,"rel":72},"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02011L0016-20240101",[73],"nofollow","Council Directive (EU) 2011/16"," on administrative cooperation in the field of taxation. It was adopted as ",[69,77,80],{"href":78,"rel":79},"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023L2226",[73],"Council Directive (EU) 2023/2226"," in October 2023 and required Member States to transpose into national law by 31 December 2025, with rules applying from 1 January 2026.",[51,83,84,85,90],{},"Substantively, DAC8 transposes the ",[69,86,89],{"href":87,"rel":88},"https://www.oecd.org/tax/exchange-of-tax-information/crypto-asset-reporting-framework.htm",[73],"OECD's Crypto-Asset Reporting Framework"," (CARF) into EU law and goes a step further on certain points:",[92,93,94,102,108],"ul",{},[95,96,97,101],"li",{},[98,99,100],"strong",{},"CARF baseline",": Identification + reporting of crypto-asset transactions.",[95,103,104,107],{},[98,105,106],{},"DAC8 additions",": Coverage of certain e-money tokens (EMTs) and asset-referenced tokens (ARTs) under MiCA, and tighter scope on retail-payment transactions above €50,000.",[95,109,110,113],{},[98,111,112],{},"Automatic exchange",": Data flows between EU Member States automatically, and to OECD CARF jurisdictions through the OECD's Multilateral Competent Authority Agreement.",[51,115,116],{},"The net effect: a CASP operating across EU markets reports once to its home Member State, and the data flows to every relevant jurisdiction automatically.",[61,118,120],{"id":119},"who-is-in-scope","Who is in scope",[51,122,123],{},"A \"Reporting CASP\" under DAC8 is any entity that:",[125,126,127,133],"ol",{},[95,128,129,130],{},"Has obtained authorization as a CASP under MiCA, ",[98,131,132],{},"or",[95,134,135],{},"Provides crypto-asset services in or into the EU as a regular business, even if not MiCA-licensed (e.g. via reverse-solicitation in the transition period).",[51,137,138],{},"In-scope services include:",[92,140,141,147,153,159,165,171,176],{},[95,142,143,146],{},[98,144,145],{},"Operating an exchange"," between crypto-assets and fiat or between crypto-assets.",[95,148,149,152],{},[98,150,151],{},"Custody and administration"," of crypto-assets on behalf of clients.",[95,154,155,158],{},[98,156,157],{},"Operating a trading platform"," for crypto-assets.",[95,160,161,164],{},[98,162,163],{},"Brokerage"," — execution of orders on behalf of clients.",[95,166,167,170],{},[98,168,169],{},"Reception and transmission of orders",".",[95,172,173,170],{},[98,174,175],{},"Crypto-asset transfers on behalf of clients",[95,177,178,181],{},[98,179,180],{},"Payment services denominated in EMTs or qualifying crypto-assets",", where transactions exceed €50,000.",[51,183,184],{},"Out of scope:",[92,186,187,193,199],{},[95,188,189,192],{},[98,190,191],{},"Wallet software providers"," that do not hold or transmit crypto on behalf of users (non-custodial wallets).",[95,194,195,198],{},[98,196,197],{},"Pure DeFi protocols"," that do not have a centralized service provider with user relationships.",[95,200,201,204],{},[98,202,203],{},"NFT marketplaces"," for unique, non-fungible items used solely as collectibles. (The line between \"fungible-enough-to-report\" and \"unique\" is fuzzy and contested.)",[51,206,207,208,211],{},"Important nuance: the ",[98,209,210],{},"place of supply"," test means non-EU exchanges that actively serve EU residents are also in scope. A US-incorporated exchange with EU customers must comply with DAC8 either directly (if it has an EU presence) or by registering with a Member State as a non-EU CASP.",[61,213,215],{"id":214},"data-that-must-be-collected-per-user","Data that must be collected per user",[51,217,218],{},"For every reportable user, a CASP must collect and verify:",[220,221,222,238],"table",{},[223,224,225],"thead",{},[226,227,228,232,235],"tr",{},[229,230,231],"th",{},"Field",[229,233,234],{},"Individual",[229,236,237],{},"Entity",[239,240,241,253,263,272,282,292,302,312],"tbody",{},[226,242,243,247,250],{},[244,245,246],"td",{},"Name",[244,248,249],{},"✓",[244,251,252],{},"✓ (legal name)",[226,254,255,258,260],{},[244,256,257],{},"Address",[244,259,249],{},[244,261,262],{},"✓ (registered office)",[226,264,265,268,270],{},[244,266,267],{},"Tax residency jurisdictions",[244,269,249],{},[244,271,249],{},[226,273,274,277,280],{},[244,275,276],{},"Tax Identification Number(s)",[244,278,279],{},"✓ (per residency)",[244,281,249],{},[226,283,284,287,289],{},[244,285,286],{},"Date and place of birth",[244,288,249],{},[244,290,291],{},"—",[226,293,294,297,299],{},[244,295,296],{},"Legal Entity Identifier (LEI)",[244,298,291],{},[244,300,301],{},"✓ (where issued)",[226,303,304,307,309],{},[244,305,306],{},"Self-certification",[244,308,249],{},[244,310,311],{},"✓ (by an authorized person)",[226,313,314,317,320],{},[244,315,316],{},"Documentary evidence of residency",[244,318,319],{},"✓ (where required)",[244,321,319],{},[51,323,324],{},"The self-certification must be obtained at account opening or, for pre-existing customers, before the first reporting deadline. CASPs must apply due diligence sufficient to identify when a self-certification appears unreliable (e.g. mismatched country indicators).",[51,326,327],{},"For pre-existing accounts, the directive provides limited transition relief: pre-existing individual accounts must be reviewed by 31 December 2026; pre-existing entity accounts by 31 December 2027.",[61,329,331],{"id":330},"transactional-data-that-must-be-reported","Transactional data that must be reported",[51,333,334],{},"For each reportable user, the annual report includes:",[125,336,337,357,363],{},[95,338,339,342,343],{},[98,340,341],{},"Aggregate gross amount"," paid and received per crypto-asset, in fiat-equivalent at the time of each transaction:",[92,344,345,348,351,354],{},[95,346,347],{},"Crypto-to-fiat acquisitions and disposals (with the type of counterparty: retail vs CASP vs other).",[95,349,350],{},"Crypto-to-crypto exchanges.",[95,352,353],{},"Retail-payment transactions exceeding €50,000.",[95,355,356],{},"Transfers to/from external wallets (for the parts where counterparty is not another reporting CASP).",[95,358,359,362],{},[98,360,361],{},"Number of units"," acquired or disposed of per crypto-asset.",[95,364,365,368],{},[98,366,367],{},"Counts"," of relevant transactions in each category.",[51,370,371,372,375],{},"The reporting is ",[98,373,374],{},"annual aggregate"," — not per-transaction. But CASPs must retain the underlying transaction data for at least 5 years (national variations apply) in case of audit.",[61,377,379],{"id":378},"reporting-deadlines","Reporting deadlines",[220,381,382,392],{},[223,383,384],{},[226,385,386,389],{},[229,387,388],{},"Date",[229,390,391],{},"Action",[239,393,394,402,410,418,426],{},[226,395,396,399],{},[244,397,398],{},"1 January 2026",[244,400,401],{},"DAC8 begins. CASPs collect data on every transaction.",[226,403,404,407],{},[244,405,406],{},"31 December 2026",[244,408,409],{},"First reporting period closes. Pre-existing individual accounts due-diligence deadline.",[226,411,412,415],{},[244,413,414],{},"31 January 2027",[244,416,417],{},"First annual report due to home Member State competent authority.",[226,419,420,423],{},[244,421,422],{},"30 September 2027",[244,424,425],{},"Member States exchange data among themselves and with OECD jurisdictions.",[226,427,428,431],{},[244,429,430],{},"31 December 2027",[244,432,433],{},"Pre-existing entity accounts due-diligence deadline.",[51,435,436],{},"The home Member State concept: a CASP reports to one tax authority (its primary EU establishment), not to every Member State where it has customers. The home authority then routes the data via automatic exchange.",[61,438,440],{"id":439},"penalty-regime-member-state-variations","Penalty regime — Member State variations",[51,442,443],{},"The Directive requires \"effective, proportionate, and dissuasive\" penalties but leaves the specifics to national transposition. Current state:",[220,445,446,456],{},[223,447,448],{},[226,449,450,453],{},[229,451,452],{},"Member State",[229,454,455],{},"Penalty range (illustrative)",[239,457,458,466,474,482,490,498],{},[226,459,460,463],{},[244,461,462],{},"Germany",[244,464,465],{},"Administrative fines from €5,000 per failure, up to €50,000 per repeated failure; criminal sanctions for wilful non-compliance.",[226,467,468,471],{},[244,469,470],{},"France",[244,472,473],{},"Up to 5% of annual EU turnover for systemic failure; per-record fines for individual omissions.",[226,475,476,479],{},[244,477,478],{},"Spain",[244,480,481],{},"Administrative fines plus operating-licence suspension for repeated non-compliance.",[226,483,484,487],{},[244,485,486],{},"Ireland",[244,488,489],{},"Up to €19,000 per failure plus daily continuing-failure penalties of €2,500.",[226,491,492,495],{},[244,493,494],{},"Netherlands",[244,496,497],{},"Penalties scaled to severity, up to €830,000 per category of failure.",[226,499,500,503],{},[244,501,502],{},"Italy",[244,504,505],{},"Per-transaction fines from €10 to €50, capped at €30,000 per filer-year.",[51,507,508],{},"The MiCA license-revocation risk is the most consequential. Repeated DAC8 failures by a MiCA-licensed CASP can trigger formal proceedings under Article 64 MiCA. A CASP losing its MiCA passport effectively loses access to the EU market.",[61,510,512],{"id":511},"operational-workflow-what-a-compliant-casp-looks-like","Operational workflow — what a compliant CASP looks like",[51,514,515],{},"The minimum viable DAC8 operations function:",[517,518,520],"h3",{"id":519},"_1-onboarding-due-diligence","1. Onboarding due diligence",[92,522,523,526,529,532],{},[95,524,525],{},"Collect tax residency self-certification at account opening.",[95,527,528],{},"Validate the certification against KYC documents.",[95,530,531],{},"Apply enhanced verification for high-risk indicators (e.g. mismatched country signals, residency in a non-cooperative jurisdiction).",[95,533,534],{},"Refresh certifications on material change (annual reminder is the practical floor).",[517,536,538],{"id":537},"_2-transaction-tagging","2. Transaction tagging",[92,540,541,544,547],{},[95,542,543],{},"Tag every transaction with: counterparty type (CASP vs retail vs unknown), jurisdiction(s), in-scope vs out-of-scope status.",[95,545,546],{},"Preserve fiat-equivalent values at the time of transaction using a defensible price source.",[95,548,549],{},"For retail-payment transactions, flag those exceeding €50,000.",[517,551,553],{"id":552},"_3-aggregate-computation-and-reporting","3. Aggregate computation and reporting",[92,555,556,559,568],{},[95,557,558],{},"Annual rollup per user, per crypto-asset, per transaction type.",[95,560,561,562,567],{},"XML-formatted report aligned with the EU's ",[69,563,566],{"href":564,"rel":565},"https://taxation-customs.ec.europa.eu/",[73],"DAC8 schema"," (similar in structure to FATCA/CRS reporting).",[95,569,570],{},"Encryption and submission via the home Member State's portal.",[517,572,574],{"id":573},"_4-retention-and-audit","4. Retention and audit",[92,576,577,580,583],{},[95,578,579],{},"Underlying transactional data retained for at least 5 years (longer in some Member States).",[95,581,582],{},"Documentation of due-diligence steps preserved.",[95,584,585],{},"Audit trail showing changes to user-residency data.",[517,587,589],{"id":588},"_5-user-communications","5. User communications",[92,591,592,595],{},[95,593,594],{},"Notification to users (typically at account opening) that data may be reported under DAC8.",[95,596,597],{},"Privacy-policy alignment with GDPR — DAC8 reporting is a legal-obligation basis under Article 6(1)(c) GDPR, but transparency obligations remain.",[61,599,601],{"id":600},"where-dac8-intersects-with-mica-gdpr-and-amld","Where DAC8 intersects with MiCA, GDPR, and AMLD",[51,603,604],{},"DAC8 sits in a dense regulatory neighborhood. The intersections matter operationally:",[92,606,607,613,619,625],{},[95,608,609,612],{},[98,610,611],{},"MiCA",": Defines who is a CASP and what services are regulated. DAC8 reporting follows MiCA scope.",[95,614,615,618],{},[98,616,617],{},"GDPR",": Provides the data-protection framework. DAC8 reporting is a legal-obligation processing basis but transparency, retention-limit, and data-subject-rights obligations remain.",[95,620,621,624],{},[98,622,623],{},"AMLD6",": AML/KYC obligations. CASPs already collect much of the DAC8 data for AML purposes; the question is whether the AML data is sufficient for DAC8 (often it isn't, because tax residency is not part of standard KYC).",[95,626,627,630],{},[98,628,629],{},"CARF",": The OECD framework. Non-EU CASPs serving EU customers may be reportable under both DAC8 and CARF in their home jurisdiction.",[61,632,634],{"id":633},"gotchas-in-practice","Gotchas in practice",[51,636,637],{},"Things that trip up CASPs implementing DAC8:",[125,639,640,646,652,658,664,670],{},[95,641,642,645],{},[98,643,644],{},"Pre-existing account review"," is more painful than expected. Customers onboarded before 1 January 2026 may not have residency self-certification, and outreach campaigns are slow and expensive.",[95,647,648,651],{},[98,649,650],{},"Retail-payment €50,000 threshold",". This is per-transaction, not annual. Monitoring requires per-transaction logic, not just annual aggregates.",[95,653,654,657],{},[98,655,656],{},"Crypto-to-crypto valuation",". Each leg of a swap must be valued in fiat-equivalent. Choose a defensible price source and stick with it.",[95,659,660,663],{},[98,661,662],{},"NFT scope",". The line between \"fungible enough to report\" and \"unique collectible\" is unclear. Conservative position: report fractional NFTs and series-mint NFTs; treat fully unique 1/1 NFTs as out of scope, with an internal memo documenting the call.",[95,665,666,669],{},[98,667,668],{},"Stablecoin nuance",". EMTs and ARTs under MiCA are reportable. Algorithmic stablecoins not classified as EMTs may be out of scope but the analysis is fact-specific.",[95,671,672,675],{},[98,673,674],{},"Self-custody transfers",". Transfers to user-controlled wallets that aren't another reporting CASP are reportable but harder to characterize. Default practice: report and let the destination jurisdiction's tax authority sort out the implications.",[61,677,679],{"id":678},"how-wag3s-helps-eu-casps-and-crypto-businesses","How Wag3s helps EU CASPs and crypto businesses",[51,681,682,683,687],{},"For DAOs and crypto businesses with an EU footprint, ",[69,684,686],{"href":685},"/ledger","Wag3s Ledger"," provides:",[92,689,690,693,696,699,702],{},[95,691,692],{},"Transaction-level tagging with DAC8 reporting fields built into the schema.",[95,694,695],{},"Per-counterparty classification (CASP vs retail vs other) for transaction reporting.",[95,697,698],{},"Fair-market valuation in EUR using auditable price sources.",[95,700,701],{},"Annual aggregation per user/customer, per crypto-asset, per category.",[95,703,704],{},"Export formats compatible with the EU's DAC8 XML schema.",[51,706,707],{},"For CASPs themselves implementing DAC8 reporting, the key need is integration between transaction history (which lives in the trading platform) and customer master-data (which lives in KYC/CRM systems). Wag3s Ledger interoperates with both layers.",[61,709,711],{"id":710},"useful-eu-resources","Useful EU resources",[92,713,714,721,729,736,744],{},[95,715,716,720],{},[69,717,719],{"href":78,"rel":718},[73],"Council Directive (EU) 2023/2226 (DAC8)"," — the directive itself.",[95,722,723,728],{},[69,724,727],{"href":725,"rel":726},"https://taxation-customs.ec.europa.eu/taxation/tax-co-operation-and-control/cooperation-tax-matters/enhanced-administrative-cooperation-field-direct-taxation_en",[73],"European Commission DAC8 page"," — implementation tracker.",[95,730,731,735],{},[69,732,734],{"href":87,"rel":733},[73],"OECD CARF"," — the underlying OECD framework.",[95,737,738,743],{},[69,739,742],{"href":740,"rel":741},"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023R1114",[73],"MiCA Regulation (EU) 2023/1114"," — the MiCA license framework that DAC8 sits on top of.",[95,745,746,751],{},[69,747,750],{"href":748,"rel":749},"https://www.eba.europa.eu/regulation-and-policy/markets-crypto-assets-mica",[73],"EBA MiCA guidance"," — supervisory expectations.",[61,753,755],{"id":754},"related-guides","Related guides",[92,757,758,770,777,784],{},[95,759,760,764,765,769],{},[69,761,763],{"href":762},"/blog/mica-regulation","MiCA regulation",", ",[69,766,768],{"href":767},"/blog/mica-implementation-checklist","MiCA implementation checklist"," — the licensing layer DAC8 sits on.",[95,771,772,776],{},[69,773,775],{"href":774},"/blog/aml-kyc-crypto-business","AML & KYC for crypto businesses"," — the operational overlap with DAC8 due diligence.",[95,778,779,783],{},[69,780,782],{"href":781},"/blog/crypto-security-finance-teams","Crypto security for finance teams"," — the operational controls that protect DAC8 data.",[95,785,786,790],{},[69,787,789],{"href":788},"/blog/crypto-audit-readiness","Crypto audit readiness"," — preparing for DAC8 audits.",{"title":792,"searchDepth":793,"depth":793,"links":794},"",2,[795,796,797,798,799,800,801,809,810,811,812,813],{"id":63,"depth":793,"text":64},{"id":119,"depth":793,"text":120},{"id":214,"depth":793,"text":215},{"id":330,"depth":793,"text":331},{"id":378,"depth":793,"text":379},{"id":439,"depth":793,"text":440},{"id":511,"depth":793,"text":512,"children":802},[803,805,806,807,808],{"id":519,"depth":804,"text":520},3,{"id":537,"depth":804,"text":538},{"id":552,"depth":804,"text":553},{"id":573,"depth":804,"text":574},{"id":588,"depth":804,"text":589},{"id":600,"depth":793,"text":601},{"id":633,"depth":793,"text":634},{"id":678,"depth":793,"text":679},{"id":710,"depth":793,"text":711},{"id":754,"depth":793,"text":755},"2026-05-09T00:00:00.000Z","How DAC8 changes EU crypto reporting from 1 January 2026. Who is in scope, the data CASPs must collect, the reporting deadlines, and how to operationalize compliance.","This article is informational and does not constitute legal or compliance advice. DAC8 transposition into national law is ongoing across Member States and exact reporting fields may vary by jurisdiction. CASPs should consult an EU-qualified compliance counsel before designing their reporting infrastructure.","md",[819,822,825,828,831,834],{"question":820,"answer":821},"What is DAC8 and who does it apply to?","DAC8 is the eighth amendment to the EU Directive on Administrative Cooperation, transposing the OECD's CARF framework into EU law. It applies to any Crypto-Asset Service Provider (CASP) authorized under MiCA that serves EU-resident users, including exchanges, custodians, brokers, payment providers, and qualifying NFT marketplaces. Rules took effect 1 January 2026.",{"question":823,"answer":824},"What's the difference between DAC8 and CARF?","CARF is the OECD framework. DAC8 is the EU-specific implementation that goes further: it covers all 27 Member States automatically, includes some categories of e-money tokens that CARF excludes, and requires reporting of certain MiCA-regulated services beyond the CARF baseline. CASPs operating only in the EU follow DAC8; CASPs operating globally typically need both.",{"question":826,"answer":827},"When must CASPs first report under DAC8?","First reporting period: calendar year 2026 (1 January – 31 December 2026). First report due: by 31 January 2027 to the CASP's home Member State tax authority. The home authority then exchanges the data with other Member States and OECD jurisdictions by 30 September 2027.",{"question":829,"answer":830},"What user data must a CASP collect under DAC8?","For every reportable user: name, address, jurisdiction(s) of tax residence, taxpayer identification number(s), date and place of birth (individuals), legal entity identifier (entities), and a self-certification confirming the residency status. CASPs must perform due diligence sufficient to verify the certification and refresh it whenever circumstances change.",{"question":832,"answer":833},"What transaction data is reported?","For each reportable user: aggregate fair-market value and number of units of each crypto-asset acquired or disposed of in exchange for fiat or another crypto-asset, broken down between transactions for fiat (with counterparty type) and crypto-to-crypto. Retail-payment transactions above €50,000 are also in scope. Reporting is annual aggregate, not per-transaction.",{"question":835,"answer":836},"What's the penalty regime for DAC8 non-compliance?","Penalties are set by each Member State and vary widely. The Directive requires sanctions to be effective, proportionate, and dissuasive. National transpositions range from administrative fines starting at €5,000 per failure (Germany) to revenue-based penalties capped at 5% of turnover (France) or operating-licence suspension (Spain in repeated-failure cases). MiCA license-revocation risk is the most significant exposure for serial non-compliance.",null,{"keywords":839},[840,841,842,843,844,845],"dac8 compliance 2026","dac8 casp reporting","dac8 vs carf","eu crypto reporting 2026","casp dac8 deadline","crypto-asset reporting eu",true,"/blog/dac8-compliance-guide","Wag3s Editorial Team — verified against Council Directive (EU) 2023/2226 and national transposition status",{"title":33,"description":815},"3.blog/49.dac8-compliance-guide","Z3MUqgkIII6pwxMWKqN4lTzIv1uHNZuCBQwhNVJTR6Y",[853,858],{"title":854,"path":855,"stem":856,"description":857,"children":-1},"EigenLayer Restaking Accounting: AVS Rewards, LRTs & Tax Treatment","/blog/eigenlayer-restaking-accounting","3.blog/48.eigenlayer-restaking-accounting","How to account for EigenLayer restaking and liquid restaking tokens (LRTs). AVS reward classification, double-income recognition, slashing losses, and IFRS/GAAP treatment for 2026.",{"title":859,"path":860,"stem":861,"description":862,"children":-1},"Crypto Accounting NetSuite Integration: Full Setup Guide for 2026","/blog/crypto-accounting-netsuite-integration","3.blog/50.crypto-accounting-netsuite-integration","How to integrate crypto-native accounting with Oracle NetSuite. Subledger architecture, journal-entry automation, multi-currency configuration, and audit-readiness for finance teams.",1778328593424]