One change, then what?
Suppose one input in a historical blockchain execution had been different. Finding dependent transactions is a useful start, but it does not tell you whether those transactions would succeed, revert, or become invalid.
RHOOK executes the remaining transactions against the state produced by the changed branch. It records where the two histories first differ and enough evidence to explain the difference.
What the replay keeps fixed
The starting checkpoint, historical context, and transaction order are declared. One intervention changes the branch. Subsequent execution results and states are then regenerated.
The transcript records transaction identity, state commitments, execution status, fees, logs, and semantic values tied to a particular state. A separate verifier checks the relationships inside that record.
The current work
The repository has a small protocol-neutral example and a pinned Robinhood Chain v4 replay over 50 continuous blocks. Recent work has focused on reproducing that example on a clean Linux setup and making the verifier stricter about malformed evidence.
The Robinhood example changes a declared input while keeping the historical envelope for alignment. Its documentation explains that analytical boundary and the limits of the reproduction.
Still a research implementation
The current implementation is single-target and does not authenticate the transcript producer. It is not a production certification or a system for assigning liability. The repository keeps those boundaries explicit.
A separate historical Alchemix study informed this line of work. Its reported results are not presented as a benchmark of the current evidence stack.