Cybersecurity & forensics
Chain-Trace
Normalize blockchain activity into investigator-ready evidence.
- Status
- Working product
- My role
- Full-stack forensics platform engineering
- Timeframe
- 2026
- Core technology
- FastAPI · Next.js · PostgreSQL · SQLAlchemy
01 / Context
The problem
Raw blockchain APIs expose chain-specific structures that slow investigation and make it hard to build one coherent transaction narrative.
02 / Product
The implemented solution
Chain-Trace detects the relevant chain, normalizes transfers, enriches counterparties, organizes addresses into cases, and presents a unified investigation timeline.
03 / System
Architecture, in plain language
Modular FastAPI services adapt provider data into shared event models. SQLAlchemy persistence and caching reduce repeated external calls; the Next.js interface manages traces, labels, profiles, and sessions.
04 / Judgment
Important decisions
- Normalized chain-specific events so investigation tools can operate on one model.
- Layered built-in, local, and provider labels to preserve control when external enrichment is unavailable.
- Cached expensive provider lookups while keeping provenance visible.
05 / Boundaries
Limitations and next work
Address labels and traceability heuristics are investigative signals, not proof of identity or wrongdoing. Provider coverage and chain data can be incomplete.
06 / Implementation
Focused technology
FastAPI · Next.js · PostgreSQL · SQLAlchemy · Etherscan · Moralis