Blockchain Security Research
Ongoing research into smart contract vulnerability classes, MEV, and protocol attack surfaces, with reproductions written as Foundry tests.
Overview
A standing body of work rather than a shipped product: reading contracts, reproducing known exploit classes in tests, and building a personal catalogue of the patterns that keep recurring.
Problem
Vulnerability write-ups explain what went wrong after the fact, but reading a post-mortem is not the same as understanding the bug well enough to spot it in unfamiliar code. The gap closes only by reproducing the failure yourself.
Solution
Each pattern studied gets a minimal Foundry reproduction — a contract exhibiting the flaw and a test that exploits it. Static analysis with Slither runs first to see what tooling catches, which makes the residue that tooling misses the interesting part.
Architecture
A Foundry workspace of isolated case directories, one per vulnerability class, each with the vulnerable contract, an exploit test, and notes on the root cause and its fix. Python scripts drive batch analysis across the set.
Key features
- Reproductions of reentrancy, access-control, and oracle-manipulation classes
- Notes tracing each bug to its root cause and remediation
- Slither baselines showing what static analysis does and does not catch
- Comparison of the same flaw across Solidity versions
Technology stack
Current status
Ongoing private research. No findings are published and no public repository exists, so nothing here should be read as a disclosed vulnerability or a completed audit.
Links
No public repository or deployment for this project yet, so there is nothing to link here. I would rather leave this empty than point at something that does not exist — happy to talk through the work directly. Get in touch.