Inspiration

Crypto users trade across wallets and exchanges, but tax reporting is still confusing and manual. We were inspired by how hard it is to answer: “What do I owe?”, “Am I compliant?”, and “What should I do next?”

What it does

CryptoAuditX ingests transactions in a wallet, reconstructs portfolio activity, calculates gains using FIFO, flags compliance risks (missing prices, unclassified transactions, transfer ambiguity), and simulates tax-aware sell/hold scenarios with recommendations using AI automation.

How we built it

  • Frontend: Next.js 14 + TypeScript + Tailwind + Recharts
  • Backend: NestJS APIs for ingestion, compliance, and simulation
  • Core engine: Shared TypeScript FIFO tax engine for deterministic gain/loss calculations
  • Flow: Wallet Address → processing → portfolio analytics → compliance checks → scenario simulation/report export

Challenges we ran into

  • Inconsistent metadata and token naming across sources
  • Missing historical price data for some transactions
  • Correctly matching transfers without double-counting taxable events
  • Making complex tax/compliance output easy to understand in UI

Accomplishments that we're proud of

  • Built an end-to-end working pipeline from wallet addresses to actionable insights
  • Implemented deterministic FIFO-based tax calculations
  • Added compliance risk scoring and audit-style flag tracking
  • Delivered scenario simulation so users can plan decisions, not just report history

What we learned

  • Trust comes from deterministic, explainable tax logic
  • Data normalization is the hardest part of crypto tooling
  • Good UX is critical for compliance products
  • Simulation adds major practical value beyond static tax reports

What's next for CryptoAuditX

  • Add more exchange/wallet connectors and on-chain ingestion
  • Improve price oracle coverage and confidence scoring
  • Expand jurisdiction-specific tax rules and reporting templates
  • Introduce automated remediation workflows for compliance flags
  • Generate richer AI-powered recommendations with clearer rationale

Built With

Share this project:

Updates