I'm happy to share that Iโve joined @certora as a Security Researcher.
After a year and a half working mostly solo, joining such a talented team feels like the right next step in my journey.
Grateful and proud to reach this point. ๐ซก
Every AI auditor now does the same boring thing.
So I went and fused the 4 security pillars into a singular pipeline:
- Static analysis
- RAG vulnerability search
- Recursive depth analysis
- Fuzzing and testing
Fully autonomous ๐ค
Fully open-source ๐
Going live tomorrow ๐จ
I just saw a โWe warned Balancerโ post from a multifollower legitimate account.
I hope someone finds the private key for the zero address and this circus ends.
I miss the good ol CT with sick write ups, protocol break downs and tips, at the very least it was core protocol devs with near organ failure.
These days itโs a bunch of whiny little cunts crying about their ai auditor had issues rejected, or some guy got sick with the flu.
web3 security Twitter lately:
> Company A, B, C: Our AI tool outperforms all the bad security companies on the market
> Pashov shows up at ETH Bulgaria in a Lamborghini
> Certora onboarded the nation of Bulgaria to do audits for them
crazy time to be alive
Hey chat, weโre hiring Formal Verification Engineers at Certora.
Iโve noticed many security researchers in the space already use formal methods during audits, now itโs time to go deeper.
Weโre looking for solid professionals with backgrounds in math, computer science, or formal methods.
If you want to work with a top-notch team and feel like this is for you, send me your CV, and please repost to help me find some legends.
I watched a movie yesterday, and one quote I've heard stuck with me:
"Don't doubt yourself, son. Doubt kills."
It's a powerful mindset, don't second-guess yourself. Doubting yourself and your abilities is like ignoring your instincts, convincing yourself that the code is perfect.
What you really need is a shift.
Instead of doubting your skills, doubt the code.
Very often, the issues are in front of your eyes, and what you need is a little shift in your mindset and how you look at a certain function. Don't verify it works, find when it doesn't.
Assume there are bugs - believe it.
Because doubting the code is one of the most effective ways to find a helpful idea. And once you find one, you're already a step closer to the solution.
More on that soon.
I watched a movie yesterday, and one quote I've heard stuck with me:
"Don't doubt yourself, son. Doubt kills."
It's a powerful mindset, don't second-guess yourself. Doubting yourself and your abilities is like ignoring your instincts, convincing yourself that the code is perfect.
What you really need is a shift.
Instead of doubting your skills, doubt the code.
Very often, the issues are in front of your eyes, and what you need is a little shift in your mindset and how you look at a certain function. Don't verify it works, find when it doesn't.
Assume there are bugs - believe it.
Because doubting the code is one of the most effective ways to find a helpful idea. And once you find one, you're already a step closer to the solution.
More on that soon.