Security research / ChainForgePRO
Find the failing sequence.
Make it reproducible.
A contract can behave correctly in individual tests and fail after a sequence of interactions. ChainForgePRO focuses on the rules that must hold as a protocol changes state—and the test cases that expose when they do not.
EVM / Foundry / Anvil
From a security question to a repeatable test.
- 01 / Specify
Define the invariant
Identify the accounting, access-control, or state-transition rule and its assumptions.
- 02 / Exercise
Explore call sequences
Use a scoped test harness to vary inputs, actors, and contract interactions.
- 03 / Reproduce
Isolate the failure
Capture the initial state and failing sequence in a case another engineer can replay.
A passing fuzz campaign describes the tested scope. It does not constitute a formal proof across all possible program states.
Illustrative investigation
Can a withdrawal bypass the balance rule?
Begin with a property the protocol is expected to preserve. Exercise different actors and call orders, then check that the property still holds. If a failure appears, the useful result is a reproducible sequence with explicit preconditions.
The same case can then become a regression test for a proposed fix. A reviewer can see what failed, what changed, and which behavior was retested.
PROPERTY A successful withdrawal cannot exceed the caller's available balance. EXERCISE choose actor + input + call sequence run against the scoped contract state check the property after each action IF THE PROPERTY FAILS capture initial state and call trace isolate a replayable test case rerun the case against the proposed fix
Evaluation scope
Engineering outputs a team can review.
An engagement starts with the authorized targets, repository revision, environment, and properties to investigate. Select the outputs appropriate to the system and the question under review.
| Output | Reviewable contents |
|---|---|
| Invariant test harness | Properties, handler logic, actor model, configuration, and run instructions. |
| Execution record | Tool versions, repository revision, test settings, logs, and the boundaries of the tested scope. |
| Failure reproduction | For an identified failure: prerequisites, a replayable test, expected behavior, and observed behavior. |
| Remediation evaluation | Assessment of a proposed fix against the reproduction case and agreed regression tests. |
Technical engagement
Bring a protocol and a question.
Share the repository or architecture, the behavior you need to evaluate, and the relevant deployment environment. We can define a focused scope for harness development, failure reproduction, or remediation testing.
Technical ownership
Joshua M. Abrams
Founder & Principal Investigator, Abrams Research Systems LLC. Evaluation artifacts and disclosure terms are agreed for the specific engagement.