It's January 2026…
Your inbox is overflowing with “ser pls I need a private audit” from protocol founders you’ve never met.
You remember 6 months ago when you stayed up past midnight chasing that first bug on Immunefi
Now you’ve stacked seven figures in bounties
Life is good
I get up, train, and work in Web3 security. Sleep. Repeat.
That’s it - I’m fully locked in. I don’t even go out with friends in the evenings, only on weekends.
I want to become one of the leading experts in Web3 security.
@0x1engineer@0xGreed_ Consistency is good for being slighty better than average. After that you need intensity, persistence and maybe even a bit of insanity to go over that level
@0x1engineer@0xGreed_ It's really hard to say which one is better and probably depends on the person. But I would say most aha moments happen when you're completely going crazy at something for a lot of hours in one day. That's when you have the most context stored in your brain to connect the dots.
Assume every function can be called with garbage
Even if the doc says "only called by X" — check if that's enforced on-chain.
and
Look for invariants
You ask:
“What must always be true?”
“Where can these invariants break?”
It has happened to me so many times now that it's commical. I think I have something and then try to write a PoC and be proven wrong, brutal haha. Gotta love it tho, makes me fired up
Damn just proved with a PoC that 2 of my findings are actually invalid. This is why its important to write PoCs, you never know if a validation of inputs doesn't happen in some external contract called by the function you think is vulnerable.
@andrewcmonte Banks only care about one thing. Having your money sit queitly at their place. Once you start trying to move the money out, you're gonna have a bad time.