Denis Gregor
I find the bugs that pass every test: silent data failures, now in smart contracts.
Public earnings
$0
Public findings
0
Skillset
Self-reported
Admin verified
Blockchain Platforms (L1 + VM)
Programming Languages
Security Services & Methodology
Biography
Backend and systems engineer moving into smart-contract security. My work is about the failures that don't crash: silently wrong data, values that satisfy a check while being meaningless, code that passes its own test suite for the wrong reason.
Twenty-plus merged pull requests into projects I don't maintain, across ten languages (Python, Rust, Go, Java, C++, and more), each with a test that reproduces the defect before the fix. The same method, applied to Solidity: contract-security-notes reproduces six common ways a contract loses money — vault inflation, reentrancy, access control, oracle manipulation, unchecked returns, signature replay — each with a Foundry test that carries out the exploit and shows the fix stops it.
github.com/dngr2
Security portfolio
Title | Description |
|---|---|
| contract-security-notes | Six common smart-contract vulnerabilities, each with a Foundry exploit test and its fix |
| staking-audit | A worked security review of a StakingRewards protocol: 3 findings (High/Medium/Low) with PoC tests and a report |
| invariant-fuzzing | Catching an AMM value-leak with a stateful Foundry invariant instead of a hand-written PoC |
| proxy-security | The two ways upgradeable contracts get taken over: unprotected initializer and storage collision, each with a Foundry PoC and fix |