We work backward. From the exploit transaction, from the tax statement, from the thing that already broke on-chain — and we ship the tool that should have existed before it did.
Verified incident reportBackLight · root cause + asset flow↗
Auditable tax ledgerDaejang · activity + price applied↗BackLight turns exploit transactions into verified reports. It reproduces the behavior, maps how the assets moved, and explains why the hack happened — in a form you can publish to X, Telegram, and readers who weren't in the trace.
Connect your exchanges and self-custody wallets, and Daejang estimates what you owe. Every line is auditable: what kind of activity the transaction was, and which price was applied to it.
We work at the level most teams skip: execution traces, internal calls, storage diffs, raw log topics, state replayed at a specific block. A forensic report and a tax ledger are two renderings of the same pipeline — decode the chain honestly, then say what it means.
Web3 has no shortage of dashboards. What it lacks is a defensible answer to “what actually happened, and how do you know?” That question is the spec for everything we build.
Not from a roadmap. Every product we own began as a transaction we had to take apart for someone else.
If it can't be replayed at a block height, it isn't a finding. Reproducibility is the interface between research and product.
When the manual work repeats, it becomes a product. Reports become BackLight; reconciliation becomes Daejang.
BackwardLabs is a product studio, not an agency. We are researchers and engineers who got tired of one-off analyses living in group chats, so we turned the work into software people can run themselves.
Trace decoding, state replay, root-cause analysis of live incidents.
Turning research pipelines into interfaces non-researchers can trust.
Multi-venue ingestion, transaction classification, price-source lineage.
