Incident workspace
Observation Window Skew In A Fictional Oracle
A fictional market reads a short observation window during a volatile synthetic price sequence, producing a probable oracle-manipulation lesson without executable replay.
Phase 1 · Fictional Content
Fictional data used to validate the TraceFi interface. This is not a real security incident.
Architecture Context
- Project model
- A fictional lending market used only to test oracle-manipulation learning surfaces.
- Chains
- EVM Prototype Chain
- Categories
- Oracle Manipulation, Observation Window, Market Design
Normal Intended Flow
The intended path keeps the decision state and execution state aligned before sensitive state changes occur.
For this dossier, compare that expected behavior against the invariant panel and state changes below.
Exploit Flow
The exploit path models a mismatch between the state used for calculation and the state that exists when the action is applied.
This phase keeps the diagram static so it can later be replaced by the canonical animated diagram system.
Attack Flow Diagram
Static prototype visualization of normal flow, exploit flow, and invariant break. No real transaction data is represented.
Accessible summary: A collateral decision should not depend on an observation window that can be dominated by one synthetic price movement.
Invariant-break Explanation
The prototype trace shows the modeled decision reading a narrow window during synthetic volatility.
Asset And State Changes
| State | Before | After | Delta | Note |
|---|---|---|---|---|
| Synthetic oracle reading | 1.00 reference units | 1.28 reference units | +0.28 reference units | Prototype-only value used to test visualization and table layout. |