I run the infrastructure, then I try to break it. DevOps behind AuraNode, HexaNode, TropicalCrypto, SinceDAO, and Rektanalisis DAO by day, smart contract auditor and offensive researcher the rest of the time, and part of Airdropfinder. I trust systems only after I have attacked them myself.
Running node infrastructure taught me where things break under pressure, and that made me a sharper attacker. I audit the smart contracts and protocols behind the networks I operate, then write the exploit before someone with worse intentions does.
I like the messy edges: reentrancy nobody noticed, an oracle that trusts the wrong price, a privileged function guarded by an assumption. If value flows through it, I want to know how it fails.
Review Solidity protocols before and after launch. Combine manual reasoning with fuzzing to surface reentrancy, oracle manipulation, and access control bugs, then verify the fixes hold.
Run and harden validator infrastructure, then red team it. Threat model the deployment, lock down key custody, and keep an attacker's view of everything I ship.
Cut my teeth on capture the flag and public bug bounty, moving from web exploitation into on chain security as the money moved there.
Found a cross function reentrancy that let an attacker drain rewards before balances updated. Reported privately, patched with a reentrancy guard and checks effects interactions.
Showed how a thinly traded pair could be pushed with a flash loan to mint against an inflated price. Recommended a time weighted feed and sanity bounds.
A Foundry based invariant fuzzing harness I reuse across audits to hammer protocol state and catch the bugs manual review misses.
A writeup on sandwich and backrun patterns observed on chain, and what protocol designers can do to make their users a smaller target.
Open to bug bounty engagements, security research, and appsec consulting. Let's talk.