Notes from the workbench.
Posts about web3.forensia.ai: how the product works, what we are building next, and how to read on-chain evidence without overclaiming.
A simpler investigation interface, built around one search
One search field, a plain summary first, and four deeper views on demand. It shows the records a lookup retrieved, not a full history, an owner or a safety verdict.
Read the post →- Transactions · 7 min→
Reading a transaction as a tree of contract calls
See which contract call happened inside which, then jump from any step to its activity record and source response. It is the structure a provider reported, not an independent replay.
- Transactions · 7 min→
Who actually executed each step of a transaction
Each call now separates the transaction sender, the immediate caller, the requested code and the account whose storage is in play. These are interpreted roles, not owners or verified code.
- Transactions · 7 min→
Telling failed actions apart from completed movements
Forensia separates calls that failed, calls undone by a failing parent, and calls not reported as failed. A call not reported as failed is still not a verified balance change.
- Transactions · 7 min→
Reading a direct ETH to WETH wrap or unwrap
Forensia explains one narrow kind of transaction in plain words: a direct wrap or unwrap at the Ethereum WETH contract. It is not a swap interpreter, and it does not replay execution.
- Permissions · Evidence · 7 min→
Connecting a token approval to the transfer that followed
Forensia sets a recorded approval beside a later transfer and, where one exact transferFrom call matches, links to it. It never states that the approval caused the transfer.
- Transactions · Evidence · 7 min→
What code was at an address when the transaction ran
For up to four addresses a transaction called, Forensia records the code a provider reported at three moments around it. It does not prove which bytes any single call executed.
- Transactions · Evidence · 7 min→
Before and after: what one transaction changed
When a provider supplies it, Forensia shows balances, nonces, code and storage before and after an Ethereum transaction. It is one source’s report, not a replay, and it omits intermediate steps.
- Transactions · Evidence · 7 min→
Comparing contract code before, after and at block end
Forensia lines up the code a source reported for a call target at up to three moments around a transaction. It does not establish which bytes any individual call actually ran.
- Timelines · Permissions · 7 min→
A timeline that groups by transaction and keeps its gaps
The activity timeline orders one result’s transfers and permission events by transaction and block. Where order or time is missing or contradictory, it says so and does not guess.
- Timelines · Saved work · 7 min→
One timeline across two saved captures
A saved investigation with two results gets a combined timeline that keeps each capture’s observations separate and never confuses event time with collection time. It holds two captures, no more.
- Saved work · Evidence · 6 min→
When two captures disagree, Forensia keeps both versions
Saved captures are compared occurrence by occurrence. Differing amounts, recipients or status are shown side by side with both values. Forensia does not decide which one is correct.
- Saved work · Evidence · 10 min→
Notes that point at the exact records they rely on
A note in a saved investigation can now cite up to 16 exact records across both saved results, and a correction keeps every one of them. A link is your reasoning. It is not proof of a connection.
- Evidence · Saved work · 7 min→
Checking what the screen says against the responses that were kept
Forensia rebuilds its supported readings from the provider responses retained in your browser and blocks saving and export on a contradiction. It checks consistency with those bytes. It does not re-execute the chain.
- Transactions · Evidence · 7 min→
Making the transaction, its receipt and its block agree first
Forensia now refuses to interpret an Ethereum-style transaction unless three captured records agree on what it is and where it sits. This area is still being extended, and it is not a proof of inclusion or finality.
- Bitcoin · Tracing · 6 min→
One Bitcoin transaction, three allocation assumptions, side by side
Forensia shows how proportional, input-order and reverse-order allocation each split one input across a transaction’s outputs. These are accounting assumptions. None is an observed path or evidence of ownership.
- Bitcoin · Tracing · 7 min→
Following spent Bitcoin outputs, one checked step at a time
Forensia can follow a Bitcoin transaction’s spent outputs into the transactions that spent them. It is limited to four checks and two hops, and it never says who owns anything.
- Tracing · Evidence · 6 min→
Following transfers Forensia has already captured
Follow captured transfers links same-asset movements inside one existing result, with no new requests. It shows up to 16 records and two hops, and it names gaps as gaps.
- Tracing · Evidence · 7 min→
Checking what an ETH recipient sent next, within fixed bounds
An optional check looks for a recipient’s next native transfers and confirms them against receipts. It inspects one candidate block per check, with four checks and two hops at most.
- Tracing · Evidence · 7 min→
Checking what a token recipient did next with the same token
An optional check finds a recipient’s later Transfer events for the same token contract and confirms each against its receipt. One 2,000-block window, four checks, two hops.
- Bridges · Evidence · 6 min→
Checking one Across bridge journey between Ethereum and Base
How Forensia matches an Across deposit on one network to its fill on the other, using the full bridge identifier. It covers one protocol and two networks. It is not general cross-chain tracing.
- Saved work · Tracing · 6 min→
Saving trace progress and bridge checks apart from the original result
Follow-up checks on a result can be saved, reopened without new requests, backed up and imported. They are stored in this browser only, unencrypted and unsigned, and never rewrite the original capture.
- Tracing · Saved work · 8 min→
What happens to a saved trace when a check is interrupted
A saved trace now records each check before it runs, keeps the attempt counted if the page closes, and never retries on its own. Broader browser lifecycle checks remain open.
- Tracing · Evidence · 6 min→
An experiment: locating one older wallet transaction by its nonce
Notes on a non-public demonstration capability, not available on the public site. It searches for at most one earlier nonce change when ordinary history is missing. It is not wallet indexing.
- Product · 3 min→
What Forensia is for
A read-only way to look up a public address or transaction and see what the records show, who says so, and where the proof ends.