I break and fix smart contracts.
Focused on EVM security, Solidity analysis, and precision math in DeFi systems.
Actively auditing, while developing PoCs and independent case studies.
- π§© 2 High-Severity Valid Findings (Rewarded) β Code4rena (Forte Float128)
- π§± 1 Valid Finding β Sherlock (Crestal Network, duplicate)
- β 1 Invalid / Intended Behavior Report β documented for learning transparency
- π§ͺ Foundry-based test + PoC workflow
- π§° Tools: Foundry Β· Slither Β· Aderyn Β· Anvil Β· Echidna Β· Remix Β· Etherscan
| Finding | Platform | Severity | Status | Link |
|---|---|---|---|---|
Float128::toPackedFloat Fails to Promote to L Size When Exponent Is Critically Low |
Code4rena β Forte | High | β Valid (Rewarded) | View Report |
Ln::ln() Fails to Validate Negative Inputs, Causing Division-by-Zero Panics |
Code4rena β Forte | High | β Valid (Rewarded) | View Report |
| Unauthorized Token Transfer via Insufficient Access Control | Sherlock β Crestal Network | Medium | View Report | |
| Reward Manipulation in Referral Logic | Code4rena β Nudge | β | β Invalid (Intended Behavior) | View Report |
π See full portfolio: z0L-audits
- Recon & Architecture Mapping: Identify trust boundaries and actor roles
- Static Review: Analyze state transitions and access modifiers
- Dynamic Testing: Foundry fuzz + invariant testing, mainnet forks
- Exploit Simulation: Model realistic attack paths
- Impact Analysis: Evaluate severity, risk exposure, and cascading effects
- Reporting: Clear PoC, rationale, mitigation, and lessons learned
| Domain | Tools / Frameworks |
|---|---|
| Security & Auditing | Foundry Β· Slither Β· Aderyn Β· Anvil Β· Echidna |
| Languages | Solidity Β· TypeScript |
| Analysis | Etherscan Β· Tenderly Β· Remix |
| Documentation | Markdown Β· Obsidian |
- π΅π½ Expand audit catalog
- βπ½ Publish monthly write-ups on logic & math vulnerabilities
- π§π½βπ» Land a Web3 Security Auditor / Smart Contract Engineer role
- π¬ Contribute to open-source audit tooling
βPrecision is security.β
β z0L
I believe secure code is the byproduct of clarity, not just caution.
Every function should explain why itβs safe, not just assume it.
- GitHub: z0Ld3v
- Twitter/X: @z0Ld3v
- Email: Proton
- Portfolio: z0L-audits
π‘οΈ Always learning. Always breaking (ethically). Always improving.