saascode
web3 & on-chain infrastructure·run 074 · May 2026

Crisistrace

An incident and investigation workspace that links instrumented agent decisions, approvals, wallet execution, transaction hashes, multi-hop fund-flow hypotheses, and reviewer conclusions without claiming identity or causality from chain data alone.

Genesis score7.46/10
Make Crisistrace real.0/500
500 more votes and Crisistrace is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
150+ chainsCross-chain coverage claimed
0Direct agent-provenance peers
ImpossibleCausality from chain alone
The case

Existing blockchain forensics products trace fund flows, while agent runtimes can record prompts, data, tool calls, approvals, and wallet execution. The unserved join is valuable only when instrumented before the incident: a later model log and an on-chain transaction do not prove one caused the other. Crisistrace should bind a signed decision and authorization identifier into the transaction execution record, preserve both raw chains of evidence, and present multi-hop attribution as reviewable hypotheses rather than evidence-grade fact or confirmed counterparty identity.

Who pays — and why

The compliance, security, investigation, or operations leader at a digital-asset firm running instrumented agents that can prepare or execute on-chain transactions.

What it unlocks
A signed link among agent run, input sources, model and policy version, approval, wallet request, signer, nonce, and transaction hash
Multi-hop fund-flow views with chain source, heuristic, confidence, labels, bridge boundaries, and alternatives
Versioned incident cases that distinguish raw evidence, generated summaries, investigator hypotheses, decisions, reports, and corrections
How Genesis scored it
7.46across seven criteria
tension 7temporal 8blindspot 6buyer 8leverage 8convergence 5why-not 8
8
Temporal window

Current agent trading and regulatory attention make the gap timely.

8
Buyer persona

Compliance, security, and investigations teams have a concrete agent-transaction incident job.

5
Convergence

The input has limited direct graph support.

Why it scored well

A clear digital-asset investigation buyer, enterprise forensics validation, available indexing and cross-chain primitives, and an unserved agent-execution join support the direction.

What's holding it back

The graph support is weak, instrumentation must predate the incident, on-chain attribution is probabilistic, India alignment is not established, and enterprise incumbents can add agent telemetry.

Signals detected5 sources crossed
SignalChainalysis product research

SignalTraceRule product research

SignalThe Graph research supplied to Genesis

SignalLayerZero research supplied to Genesis

Signalcompetitor scan carried in Genesis

Direction briefcrisistrace.md
crisistrace.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.